Status/Resolution/Reason: Closed/Fixed/Fixed
Reporter/Name(from Bugbase): A S / A S (A S)
Created: 11/25/2014
Components: Web Container (Tomcat)
Versions: 10.0
Failure Type: Non Functioning
Found In Build/Fixed In Build: Final / Update 23
Priority/Frequency: Major / Some users will encounter
Locale/System: English / Linux RH Enterprise 6
Vote Count: 1
Problem Description:We have had a small cluster of two instances working until updating to CF10 update 14. Now we receive communication errors
Steps to Reproduce: Create CF cluster. Update to update 14. Restart instances. View coldfusion-error.log of instances.
Actual Result: One or both instances are hung/dead
Expected Result:Both instances restart
Any Workarounds: Downgrade to update 13.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3857664
Reason: PRNeedInfo
External Customer Info:
External Company:
External Customer Name: GuitsBoy
External Customer Email:
External Test Config: My Hardware and Environment details:
CentOS 6.6 64 bit, 16GB ram.
On a reboot, or with both instances off, usually both instances will come up. Once they are up, and you try to restart one instance, you get replication communication errors. If I remove the secondary IP address to remove traffic, restarting an instance will occasionally work. But with any traffic at all, restarting the instance results in the instance never fully coming up.
Downgrading to update 13 results in normal operation.Attachments:
- November 26, 2014 00:00:00: 1_cf-error-logs.txt
- December 11, 2014 00:00:00: 2_cfusion1-coldfusion-error.log.txt
- December 11, 2014 00:00:00: 3_cfusion1-coldfusion-out.log.txt
- December 11, 2014 00:00:00: 4_cfusion1-server.xml.txt
- December 11, 2014 00:00:00: 5_cfusion2-coldfusion-error.log.txt
- December 11, 2014 00:00:00: 6_cfusion2-coldfusion-out.log.txt
- December 11, 2014 00:00:00: 7_cfusion2-server.xml.txt
Comments: