We've migrated from ColdFusion MX 6.1 to 8 recently and we're
seeing an alarming number of error messages like these:
Server Error
The server encountered an internal error and was unable to complete your request.
JRun Connector Protocol Error.
We're running:
Cold Fusion 8,0,1,195765 64-Bit
Solaris 10
Apache 2.2.10
JRun Connector mod_jrun22.so
JDK 1.5.0_16 (we downgraded the JVM as a potential fix)
Oracle JDBC drivers 11.1.0.6.0 for JDK 5 (we need Oracle 11g database support)
We've spent several days investigating this now. The only patterns seem to be that:
-happens a little bit more after a server restart
-can return the error very quickly on random pages
-but can also return the error on pages that are running big queries and take a long time to run
-very inconsistent, we can call the same page multiple times at once - some requests fail, others succeed
-we are also seeing a lot of java.io.EOFException errors in our cfserver.log with stack traces of some kind
-the logs don't point in any parcticular direction, nor do the JRun Connector errors seem to coincide with any logs entries
What we've tried to do to fix this:
-Tried the built-in Adobe Oracle database drivers
-Tried the JDK 5 version of the Oracle 11.1.0.6.0 database drivers
-Downgraded the JVM used by Cold Fusion 8 to JDK 5.
-Adjusted the data source connection pools timeouts; turned off Maintain Connections altogether just to see if it made a difference
-Adjusted template caching settings
-Tweaked the 3 or 4 JRun Connector timeout settings in Apache. Also turned on verbose mode on the JRun Connector to see if that revealed anything. Saw a few suspicious entries, such as:
jrApache[init] 127.0.0.1:51800 destroying/closing socket [35] error 0
jrApache[init] jrCloseSocket [35]
But these did not parallel all of the JRun connector errors we've been seeing.
-Tried connecting to only one database node at a time (we have an Oracle cluster)
-Verified our JDBC connection string
-Tried reproducing this error under previous Cold Fusion 6.1 production servers and in development environment, but didn't have any luck
-Even tried cleaning up the linebreak characters in some of our code after vi complained about "premature end of file" or "premature end of line" - no luck.
We're pulling our hair out at this point. The only other thing we've suspected is a firewall or loadbalancer issue causing us to lose connections. HELP!!!!
Server Error
The server encountered an internal error and was unable to complete your request.
JRun Connector Protocol Error.
We're running:
Cold Fusion 8,0,1,195765 64-Bit
Solaris 10
Apache 2.2.10
JRun Connector mod_jrun22.so
JDK 1.5.0_16 (we downgraded the JVM as a potential fix)
Oracle JDBC drivers 11.1.0.6.0 for JDK 5 (we need Oracle 11g database support)
We've spent several days investigating this now. The only patterns seem to be that:
-happens a little bit more after a server restart
-can return the error very quickly on random pages
-but can also return the error on pages that are running big queries and take a long time to run
-very inconsistent, we can call the same page multiple times at once - some requests fail, others succeed
-we are also seeing a lot of java.io.EOFException errors in our cfserver.log with stack traces of some kind
-the logs don't point in any parcticular direction, nor do the JRun Connector errors seem to coincide with any logs entries
What we've tried to do to fix this:
-Tried the built-in Adobe Oracle database drivers
-Tried the JDK 5 version of the Oracle 11.1.0.6.0 database drivers
-Downgraded the JVM used by Cold Fusion 8 to JDK 5.
-Adjusted the data source connection pools timeouts; turned off Maintain Connections altogether just to see if it made a difference
-Adjusted template caching settings
-Tweaked the 3 or 4 JRun Connector timeout settings in Apache. Also turned on verbose mode on the JRun Connector to see if that revealed anything. Saw a few suspicious entries, such as:
jrApache[init] 127.0.0.1:51800 destroying/closing socket [35] error 0
jrApache[init] jrCloseSocket [35]
But these did not parallel all of the JRun connector errors we've been seeing.
-Tried connecting to only one database node at a time (we have an Oracle cluster)
-Verified our JDBC connection string
-Tried reproducing this error under previous Cold Fusion 6.1 production servers and in development environment, but didn't have any luck
-Even tried cleaning up the linebreak characters in some of our code after vi complained about "premature end of file" or "premature end of line" - no luck.
We're pulling our hair out at this point. The only other thing we've suspected is a firewall or loadbalancer issue causing us to lose connections. HELP!!!!