ColdFusion 9 server going down frequently

New Here ,
Dec 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

We are facing CF server going down frequently from last 2 months without any major changes done in code or settings. Please help us to find the root cause of this issue. Current server settings and errors occurring in the logs are as below

CF server version : 9.0.0.251028

Edition: Enterprise

OS : Unix

OS version: 5.9

Adobe Driver version: 4.0 (Build 0005)

Java Version :1.6.0_12

Web server : Apache

Min JVM Heap size (MB) : 1524     Max JVM Heap size (MB) : 4096

JVM Arguments:

-server -Dsun.io.useCanonCaches=false -XX:MaxPermSize=1524m -XX:+UseConcMarkSweepGC -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib

Errors from cfserver.log:

error Error while reading header S_ERROR_TITLE

java.net.SocketException: Broken pipe

error Error in getRealPathFromConn

java.net.SocketException: Broken pipe

error Error while reading header Acrobat-Version

java.net.SocketException: Connection reset

error ROOT CAUSE:

java.lang.OutOfMemoryError: Java heap space

error Error while reading header S_DEBUGGING_MESSAGE

java.net.SocketException: Broken pipe

These kind of errors are displayed in the log file and we have to restart the server frequently because of this. Please let me know if any other info is needed.

Views

453

Likes

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 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

You're probably not going to get a whole lot of support, as CF9 is well past End Of Life (EOL).  However, you might consider updating to the latest supported JVM (which per this Adobe Blog article appears to be JDK 7).  You may also need some Java tuning.


Ultimately, you'd be well served to consider updating to the latest fully-supported version of ColdFusion (ColdFusion 2016, or at a minimum, ColdFusion 11).

-Carl V.

Likes

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
Adobe Community Professional ,
Dec 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

Carl Von Stetten wrote:

However, you might consider updating to the latest supported JVM (which per this Adobe Blog article appears to be JDK 7).

Just to add that Java 7 support started with ColdFusion 9.0.2.

Likes

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
LEGEND ,
Dec 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

While I completely agree with Carl Von Stetten​, I would add one caveat regarding the latest CF9 supported JDK.  If you do upgrade to JDK7, and if you use Solr or Verity collections, JDK7 update 31 has been known to cause issues with collections.  I have not been able to find any workarounds for this issue.  We wound up having to upgrade to CF10 before this problem disappeared.

JDK7 update 25 works just fine with collections.  But it isn't as secure as update 31.

Just a heads up.

HTH,

^_^

Likes

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 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

Yes we are using verity collection in the application and also upgrading to 10 will not be possible now. Will CF 9 work fine with JDK7 update 25?

Likes

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
Adobe Community Professional ,
Dec 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

asish4u22 wrote:

-XX:MaxPermSize=1524m

It may or may not be the cause, but that value is too large. Try 256m.

Likes

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 14, 2016 Dec 14, 2016

Copy link to clipboard

Copied

LATEST

BKBK wrote:

asish4u22 wrote:

-XX:MaxPermSize=1524m

It may or may not be the cause, but that value is too large. Try 256m.

we had increased this value earlier as we were getting out of memory error. Can this be the issue??

Likes

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