[ https://jira.jboss.org/jira/browse/JBAS-6135?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-6135: ----------------------------------- Attachment: failed-start-server.log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6135?page=com.atlassian.jira.plug... ] Brian Stansberry commented on JBAS-6135: ---------------------------------------- In attached failed-start-server.log, relevant logging starts at line 5734. In testrun-1018-server.log it's at line 5733. In both cases, the code executing is from org.jboss.ha.framework.server.ClusterPartition.startService(): // Do the channel connect in another thread while this // thread starts the cache and does that channel connect ChannelConnectTask task = new ChannelConnectTask(connectLatch); this.threadPool.run(task); } this.cacheHandler.startCache(); try { // This will block waiting for any async channel connect above connectLatch.await(); if (this.connectException != null) { throw this.connectException; } this.log.debug("Get current members"); this.waitForView(); // get current JG group properties this.log.debug("get nodeName"); The thread executing this code is named "main"; it's visible in both logs. The ChannelConnectTask is run in a thread pool thread; it's logging is only shown in failed-start-server.log; in testrun-1018-server.log it doesn't log. The ChannelConnectTask is as follows: public void run() { try { ClusterPartition.this.channel.connect(ClusterPartition.this.getPartitionName()); } catch (Exception e) { synchronized (ClusterPartition.this.channelLock) { ClusterPartition.this.connectException = e; } } finally { this.latch.countDown(); } } I checked whether the failure to proceed could be due to the synchronized block in the catch block. But the other code that might contend for ClusterPartition.this.channelLock does not execute until after the this.log.debug("Get current members"); logging shown above; as you can see in the logs that logging never occurs. In the testrun-1018-server.log, the "main" thread shows the expected logging for JBC channel connect and state transfer. So in that case, that connect seemed to succeed, while logging was emitted by the thread running the ChannelConnectTask. In the failed-start-server.log, the connect run by the ChannelConnectTask logs as expected, but no logging from the "main" thread for the JBC channel connect appears. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6135?page=com.atlassian.jira.plug... ] Brian Stansberry closed JBAS-6135. ---------------------------------- Resolution: Done JGRP-849 fix in JGroups 2.6.6.GA seems to have eliminated this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira