• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Coldfusion 11: Troubleshooting - No error to indicate the cause of issue in Coldfusion log files

New Here ,
Dec 07, 2015 Dec 07, 2015

Copy link to clipboard

Copied

OS: RHEL 6.7 (64-bit)

ColdFusion processes are dying or stop running for no reason that we can find in the ColdFusion log files or in the OS log files. Does anyone any suggestion what I can do to troubleshoot this issue.

Views

281

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Dec 07, 2015 Dec 07, 2015

Copy link to clipboard

Copied

Maybe try Fusion Reactor or something similar?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guide ,
Dec 07, 2015 Dec 07, 2015

Copy link to clipboard

Copied

If you have CF Enterprise sometimes CF Monitor can be assistance to notice what is happening.

It is fair to say on 64 bit the initial and maximum memory setting plus MaxMetaspace of 256m, 512m and 192m respectively can be small. While some kind of Java logging or monitoring can assist to check how well those are performing perhaps you can be better served to increase one or more of those values.

HTH, Carl.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 08, 2015 Dec 08, 2015

Copy link to clipboard

Copied

We have CF Enterprise and I have enabled alerts with CF Monitor for memory, slow response etc. But nothing was triggered prior to our external website monitor detect the website has stopped responding.

We have increased the Java Heap Size to 4086MB. Is the Metaspace different to this?

Thanks,

Tim

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guide ,
Dec 08, 2015 Dec 08, 2015

Copy link to clipboard

Copied

LATEST

Hi Tim,

Yes Metaspace is different being non heap. If you have available memory perhaps adjust it EG:

-XX:MetaspaceSize=312m -XX:MaxMetaspaceSize=512m

CF Monitor memory only shows you heap usage. So if non heap memory was having an issue it will not be noticed. There are other non heap memory spaces than Metaspace like Code Cache and Compressed Classes (this one enabled Windows Java 8 64 bit I am not sure on Unix) however those filling therefore causing a crash are less likely but should not be overlooked.

HTH again, Carl.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation