[ https://issues.apache.org/activemq/browse/AMQ-768?page=all ] Hiram Chirino resolved AMQ-768: -------------------------------
Fix Version: (was: 4.0.2) Resolution: Fixed > Client and Broker hang trying to start a connection > --------------------------------------------------- > > Key: AMQ-768 > URL: https://issues.apache.org/activemq/browse/AMQ-768 > Project: ActiveMQ > Type: Bug > Versions: 4.0 > Environment: JDK 1.5.0_06, Windows XP SP2 > Reporter: Jamie McCrindle > Assignee: Hiram Chirino > Fix For: 4.1 > > > Every now and again a client hangs connecting to the broker. The broker is > configured with the default activemq.xml. The stack dumps are as follows: > ACTIVEMQ_HOME: C:\Java\incubator-activemq-4.0\bin\.. > Loading message broker from: xbean:activemq.xml > INFO BrokerService - ActiveMQ 4.0 JMS Message Broker > (localhos > t) is starting > INFO BrokerService - For help or more information please > see: > http://incubator.apache.org/activemq/ > INFO ManagementContext - JMX consoles can connect to > service:jmx:r > mi:///jndi/rmi://localhost:1099/jmxrmi > INFO JDBCPersistenceAdapter - Database driver recognized: > [apache_derby > _embedded_jdbc_driver] > INFO JournalPersistenceAdapter - Journal Recovery Started from: Active > Jou > rnal: using 5 x 20.0 Megs at: > C:\Java\incubator-activemq-4.0\activemq-data\journ > al > INFO JournalPersistenceAdapter - Journal Recovered: 1 message(s) in > transa > ctions recovered. > INFO TransportServerThreadSupport - Listening for connections at: > tcp://SIM-J > amesM:61616 > WARN MulticastDiscoveryAgent - brokerName not set > INFO TransportConnector - Connector default Started > INFO TransportServerThreadSupport - Listening for connections at: > tcp://SIM-J > amesM:61613?wireFormat=stomp > INFO TransportConnector - Connector stomp Started > INFO NetworkConnector - Network Connector default Started > INFO BrokerService - ActiveMQ JMS Message Broker > (localhost, I > D:SIM-JamesM-2205-1149180591980-1:0) started > WARN ManagedTransportConnection - Failed to unregister mbean: > org.apache.ac > tivemq:BrokerName=localhost,Type=Connection,ConnectorName=default,Connection=9 > the stack dump is: > "main" prio=6 tid=0x000379d0 nid=0x93d0 in Object.wait() > [0x0007e000..0x0007fc40 > ] > at java.lang.Object.wait(Native Method) > - waiting on <0x02b66278> (a > edu.emory.mathcs.backport.java.util.concurr > ent.CountDownLatch) > at java.lang.Object.wait(Object.java:474) > at > edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(C > ountDownLatch.java:179) > - locked <0x02b66278> (a > edu.emory.mathcs.backport.java.util.concurrent. > CountDownLatch) > at > org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatN > egotiator.java:73) > at > org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.ja > va:44) > - locked <0x02b64098> (a java.lang.Object) > at > org.apache.activemq.transport.ResponseCorrelator.asyncRequest(Respons > eCorrelator.java:68) > at > org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorr > elator.java:73) > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect > ion.java:1131) > at > org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(Activ > eMQConnection.java:1219) > - locked <0x02b602c0> (a org.apache.activemq.ActiveMQConnection) > at > org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java: > 435) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira