tracker issue : CF-4159697

select a category, or use search below
(searches all categories and all time range)
Title:

ColdFusion 2016 Enterprise Clustering Problems

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): Mike Brunt / Mike Brunt (Mike Brunt)

Created: 05/31/2016

Components: Web Container (Tomcat), Instance/Cluster Manager

Versions: 2016

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF2016_Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Linux All

Vote Count: 0

Problem Description: Currently we are trying to set up a simple cluster with one remote and one local instance on, they will 
use sticky sessions and session replication. All instances stop and start fine prior to setting up the
cluster, however after setting up the cluster and restarting the instances some appear to be in some
sort of hanging pre-startstate and we can no longer get into Instance Manager in ColdFusion Admin.  


Steps to Reproduce:  Go to Enterprise Manager > Clustering > create cluster, add instances then try to start all instances in the cluster.

Actual Result: At least two of the instances fail to start and it is no longer possible to browse Instance Manager in ColdFusion Administrator.

Expected Result:  The cluster is created stably and all instances restart.

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4159697

External Customer Info:
External Company:  
External Customer Name: Mike Brunt
External Customer Email:  
External Test Config: My Hardware and Environment details:  ColdFusion Enterprise 2016 both before and after hotfix 1, running on CentOS 7.x

Attachments:

Comments:

When we try to stop the instances in trouble we get this message... [root@ar-dev03 bin]# ./coldfusion start Starting ColdFusion 2016 server ... The ColdFusion 2016 server is starting up and will be available shortly. ====================================================================== ColdFusion 2016 server has been started. ColdFusion 2016 will write logs to /opt/coldfusion2016/web01-01/bin/../logs/coldfusion-out.log ====================================================================== [root@ar-dev03 bin]# ./coldfusion stop Stopping ColdFusion 2016 server, please wait May 22, 2016 8:10:27 PM com.adobe.coldfusion.launcher.Launcher stopServer SEVERE: Shutdown Port 8007is not active. Stop the server only after it is started. ColdFusion 2016 server has been stopped Also, the newser entry in the out.log is this... May 22, 2016 19:45:16 PM Information [localhost-startStop-2] - Stopping Event Gateways. May 22, 2016 19:45:21 PM Information [localhost-startStop-2] - Stopping Monitoring Server. May 22, 2016 19:45:21 PM Information [localhost-startStop-2] - ColdFusion stopped 19:45 is 30 minutes ago our local time, before we put this instance into the cluster. This entry is in the error.log May 22, 2016 8:07:59 PM org.apache.catalina.ha.tcp.SimpleTcpCluster startInternal SEVERE: Unable to start cluster. org.apache.catalina.tribes.ChannelException: java.net.BindException: Cannot assign requested address; No faulty members identified. at org.apache.catalina.tribes.group.ChannelCoordinator.internalStart(ChannelCoordinator.java:187) at org.apache.catalina.tribes.group.ChannelCoordinator.start(ChannelCoordinator.java:105) at org.apache.catalina.tribes.group.ChannelInterceptorBase.start(ChannelInterceptorBase.java:155)
Comment by External U.
2569 | May 31, 2016 02:45:38 PM GMT
Hi Mike, We would want you to send the following files to us , so that we can figure out the issue: 1. Please zip your logs directory and send the zip. 2. Send <cfinstance>/runtime/conf/server.xml file Also can you add the following flag to the jvm.config of all the instances in cluster: -Djava.net.preferIPv4Stack=true Please add this flag and restart all your instances. Tell us if this works and please send us the above files! Thanks, Suchika
Comment by Suchika S.
2570 | June 01, 2016 07:05:12 AM GMT
Hi Mike, Did our workaround fix your issue? If not then please send us the files mentioned in the comments below.If yes do let us know so that we can close the bug. Thanks, Suchika.
Comment by Suchika S.
2571 | July 28, 2016 12:02:49 AM GMT
Mike, any update for us?
Comment by Vamseekrishna N.
2572 | August 18, 2016 01:46:08 AM GMT
Closing this bug. We can reopen it if we have the required information to proceed or have other users reporting the same issue.
Comment by Vamseekrishna N.
2573 | August 24, 2016 12:04:58 AM GMT
To bad this was close with no resolution we appear to be experiencing the identical problem: create cluster then clones no longer work. We received the same message when stopping the server and nothing at startup. Also on CentOS.
Comment by External U.
2574 | September 29, 2016 04:11:55 PM GMT