You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Jamie McCrindle <ja...@gmail.com> on 2006/06/01 16:16:57 UTC
hung connecting to broker
hi,
every now and again my client hangs while connecting to the broker.
I'm using the incubating-activemq 4.0 release on windows XP,
connecting via tcp://localhost:61616. Stacktrace is as follows:
"main" prio=6 tid=0x00037b38 nid=0x875c in Object.wait() [0x0007f000..0x0007fc40
]
at java.lang.Object.wait(Native Method)
- waiting on <0x03274110> (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 <0x03274110> (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 <0x03276a30> (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 <0x02b60208> (a org.apache.activemq.ActiveMQConnection)
at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:
435)
at com.vnocore.empower.jms.JmsTemplate.afterPropertiesSet(JmsTemplate.ja
va:217)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1059)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:363)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:226)
- locked <0x030ebdf0> (a java.util.HashMap)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:147)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
preInstantiateSingletons(DefaultListableBeanFactory.java:275)
at org.springframework.context.support.AbstractApplicationContext.refres
h(AbstractApplicationContext.java:320)
regards,
jamie.
Re: hung connecting to broker
Posted by Sanjiv Jivan <sa...@gmail.com>.
I'm occasionally seeing a similar behaviour with ActiveMQ 4.0. Will add
comments to the issue once I have more concrete info
On 6/21/06, Hiram Chirino <hi...@hiramchirino.com> wrote:
>
> That's very odd. You wouldn't have an old version of the activemq
> jar's somewhere in the classpath would you?
The package names have changed to this shouldn't really be an issue, right?
But it could be related to http://issues.apache.org/activemq/browse/AMQ-768
> You may want vote for or add your comments to that issue.
Regards,
> Hiram
>
> On 6/21/06, christyc <ca...@avaya.com> wrote:
> >
> > We're seeing a similiar problem, and wanted to see if this is the same
> issue.
> >
> > We have two web apps in Tomcat 2.2.9 that use JMS connections. We were
> > using ActiveMQ3.0, things were fine, and now we're testing with ActiveMQ
> 4.0
> > (and I tried 4.0.1) and the results are:
> >
> > the first web app starting a JMS connection works fine. When the second
> web
> > app tries to start a JMS connection (after successfully getting a
> > ConnectionFactory as the first web app did also), it hangs. We shut
> down
> > Tomcat, leave the broker running, and turn on Tomcat and the first web
> app
> > hangs when it tries to start a JMS connection and same with the second
> web
> > app. Here's the error log (at the end I have the successful
> connection):
> >
> > 2006-06-21 15:25:30,864 [Thread-2] 58 JNDIReferenceFactory.java
> > DEBUG Getting instance of org.apache.activemq.ActiveMQConnectionFactory
> > 2006-06-21 15:25:30,943 [Thread-2] 101 JMSUtil.java
> > DEBUG successfully obtained connection factory
> > 2006-06-21 15:25:31,312 [Thread-2] 62 WireFormatNegotiator.java
> > DEBUG Sending: WireFormatInfo { version=1,
> > properties={TightEncodingEnabled=true, TcpNoDelayEnabled=true,
> > SizePrefixDisabled=false, StackTraceEnabled=true,
> > MaxInactivityDuration=30000, CacheEnabled=true},
> magic=[A,c,t,i,v,e,M,Q]}
> > 2006-06-21 15:25:31,318 [Thread-2] 167 JMSUtil.java
> > DEBUG returning connection: ActiveMQConnection
> > {id=ID:machinename.com-33231-1150925131041-1
> :0,clientId=null,started=false}
> > 2006-06-21 15:25:31,312 [ActiveMQ Transport:
> > tcp://localhost/xxx.x.x.x:61616] 139 TcpTransport.java
> > DEBUG TCP consumer thread starting
> >
> >
> >
> > Here is the successful log of this:
> > 2006-06-21 15:14:22,754 [Thread-36] 62 WireFormatNegotiator.java
> > DEBUG Sending: WireFormatInfo { version=1,
> > properties={TightEncodingEnabled=true, TcpNoDelayEnabled=true,
> > SizePrefixDisabled=false, StackTraceEnabled=true,
> > MaxInactivityDuration=30000, CacheEnabled=true},
> magic=[A,c,t,i,v,e,M,Q]}
> > 2006-06-21 15:14:22,796 [ActiveMQ Transport:
> > tcp://localhost/xxx.x.x.x:61616] 139 TcpTransport.java
> > DEBUG TCP consumer thread starting
> > 2006-06-21 15:14:22,816 [Thread-36] 167 JMSUtil.java
> > DEBUG returning connection: ActiveMQConnection
> > {id=ID:machinename.com-32883-1150924462273-1
> :0,clientId=null,started=false}
> > 2006-06-21 15:14:22,862 [ActiveMQ Transport:
> > tcp://localhost/xxx.x.x.x:61616] 85 WireFormatNegotiator.java
> > DEBUG Received WireFormat: WireFormatInfo { version=1,
> > properties={StackTraceEnabled=true, TightEncodingEnabled=true,
> > TcpNoDelayEnabled=true, SizePrefixDisabled=false,
> > MaxInactivityDuration=30000, CacheEnabled=true},
> magic=[A,c,t,i,v,e,M,Q]}
> > 2006-06-21 15:14:22,862 [ActiveMQ Transport:
> > tcp://localhost/xxx.x.x.x:61616] 92 WireFormatNegotiator.java
> > DEBUG tcp://localhost/xxx.x.x.x:61616 before negotiation:
> > OpenWireFormat{version=1, cacheEnabled=false, stackTraceEnabled=false,
> > tightEncodingEnabled=false, sizePrefixDisabled=false}
> >
> > --
> > View this message in context:
> http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4983639
> > Sent from the ActiveMQ - User forum at Nabble.com.
> >
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
Re: hung connecting to broker
Posted by James Strachan <ja...@gmail.com>.
This looks like the system is waiting for a connection to complete
(its hung waiting for the content negotiation to complete)..
On 6/22/06, christyc <ca...@avaya.com> wrote:
>
> Here's the stack trace, it does look similiar to the problem you noted.
>
> Thread [Thread-2] (Suspended)
>
> Object.wait(long) line: not available [native method]
>
> CountDownLatch(Object).wait() line: not available
>
> CountDownLatch.await() line: 179
>
> WireFormatNegotiator.oneway(Command) line: 73
>
> MutexTransport.oneway(Command) line: 44
>
> ResponseCorrelator.asyncRequest(Command, ResponseCallback) line:
> 68
>
> ResponseCorrelator.request(Command) line: 73
>
> ActiveMQConnection.syncSendPacket(Command) line: 1112
>
> ActiveMQConnection.ensureConnectionInfoSent() line: 1200
>
> ActiveMQConnection.start() line: 434
>
> JMSUtil.getConnection(String) line: 170
>
> JMSUtil.getSession(boolean, String) line: 225
>
> JMSUtil.getSession(boolean) line: 193
>
> SourceListener.registerForSourceTopic() line: 46
>
> SourceManager.initialize() line: 69
>
> GroupMgmtModel.<init>() line: 62
>
> NativeConstructorAccessorImpl.newInstance0(Constructor,
> Object[]) line: not available [native method]
>
> NativeConstructorAccessorImpl.newInstance(Object[]) line: not
> available
>
> DelegatingConstructorAccessorImpl.newInstance(Object[]) line:
> not available
>
> Constructor<T>.newInstance(Object...) line: not available
>
> Class<T>.newInstance0() line: not available
>
> Class<T>.newInstance() line: not available
>
> MgmtFactory.createClass(MgmtFactory$MgmtModelInfo) line: 595
>
> MgmtFactory.loadAllAdminModels() line: 567
>
> MgmtFactory.<clinit>() line: 122
>
> StartupLoader.loadMgmtModels() line: 123
>
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line:
> not available [native method]
>
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: not
> available
>
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not
> available
>
> Method.invoke(Object, Object...) line: not available
>
> LoadMethodInvoker.invokeLoadMethod(Object) line: 41
>
> StartupLoader.start(Properties) line: 68
>
> PEGenericServlet$PEServletStarter.run() line: 121
>
> Thread.run() line: not available
>
>
>
> --
> View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4995330
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: hung connecting to broker
Posted by christyc <ca...@avaya.com>.
Here's the stack trace, it does look similiar to the problem you noted.
Thread [Thread-2] (Suspended)
Object.wait(long) line: not available [native method]
CountDownLatch(Object).wait() line: not available
CountDownLatch.await() line: 179
WireFormatNegotiator.oneway(Command) line: 73
MutexTransport.oneway(Command) line: 44
ResponseCorrelator.asyncRequest(Command, ResponseCallback) line:
68
ResponseCorrelator.request(Command) line: 73
ActiveMQConnection.syncSendPacket(Command) line: 1112
ActiveMQConnection.ensureConnectionInfoSent() line: 1200
ActiveMQConnection.start() line: 434
JMSUtil.getConnection(String) line: 170
JMSUtil.getSession(boolean, String) line: 225
JMSUtil.getSession(boolean) line: 193
SourceListener.registerForSourceTopic() line: 46
SourceManager.initialize() line: 69
GroupMgmtModel.<init>() line: 62
NativeConstructorAccessorImpl.newInstance0(Constructor,
Object[]) line: not available [native method]
NativeConstructorAccessorImpl.newInstance(Object[]) line: not
available
DelegatingConstructorAccessorImpl.newInstance(Object[]) line:
not available
Constructor<T>.newInstance(Object...) line: not available
Class<T>.newInstance0() line: not available
Class<T>.newInstance() line: not available
MgmtFactory.createClass(MgmtFactory$MgmtModelInfo) line: 595
MgmtFactory.loadAllAdminModels() line: 567
MgmtFactory.<clinit>() line: 122
StartupLoader.loadMgmtModels() line: 123
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line:
not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: not
available
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not
available
Method.invoke(Object, Object...) line: not available
LoadMethodInvoker.invokeLoadMethod(Object) line: 41
StartupLoader.start(Properties) line: 68
PEGenericServlet$PEServletStarter.run() line: 121
Thread.run() line: not available
--
View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4995330
Sent from the ActiveMQ - User forum at Nabble.com.
Re: hung connecting to broker
Posted by Hiram Chirino <hi...@hiramchirino.com>.
That's very odd. You wouldn't have an old version of the activemq
jar's somewhere in the classpath would you?
But it could be related to http://issues.apache.org/activemq/browse/AMQ-768
You may want vote for or add your comments to that issue.
Regards,
Hiram
On 6/21/06, christyc <ca...@avaya.com> wrote:
>
> We're seeing a similiar problem, and wanted to see if this is the same issue.
>
> We have two web apps in Tomcat 2.2.9 that use JMS connections. We were
> using ActiveMQ3.0, things were fine, and now we're testing with ActiveMQ 4.0
> (and I tried 4.0.1) and the results are:
>
> the first web app starting a JMS connection works fine. When the second web
> app tries to start a JMS connection (after successfully getting a
> ConnectionFactory as the first web app did also), it hangs. We shut down
> Tomcat, leave the broker running, and turn on Tomcat and the first web app
> hangs when it tries to start a JMS connection and same with the second web
> app. Here's the error log (at the end I have the successful connection):
>
> 2006-06-21 15:25:30,864 [Thread-2] 58 JNDIReferenceFactory.java
> DEBUG Getting instance of org.apache.activemq.ActiveMQConnectionFactory
> 2006-06-21 15:25:30,943 [Thread-2] 101 JMSUtil.java
> DEBUG successfully obtained connection factory
> 2006-06-21 15:25:31,312 [Thread-2] 62 WireFormatNegotiator.java
> DEBUG Sending: WireFormatInfo { version=1,
> properties={TightEncodingEnabled=true, TcpNoDelayEnabled=true,
> SizePrefixDisabled=false, StackTraceEnabled=true,
> MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
> 2006-06-21 15:25:31,318 [Thread-2] 167 JMSUtil.java
> DEBUG returning connection: ActiveMQConnection
> {id=ID:machinename.com-33231-1150925131041-1:0,clientId=null,started=false}
> 2006-06-21 15:25:31,312 [ActiveMQ Transport:
> tcp://localhost/xxx.x.x.x:61616] 139 TcpTransport.java
> DEBUG TCP consumer thread starting
>
>
>
> Here is the successful log of this:
> 2006-06-21 15:14:22,754 [Thread-36] 62 WireFormatNegotiator.java
> DEBUG Sending: WireFormatInfo { version=1,
> properties={TightEncodingEnabled=true, TcpNoDelayEnabled=true,
> SizePrefixDisabled=false, StackTraceEnabled=true,
> MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
> 2006-06-21 15:14:22,796 [ActiveMQ Transport:
> tcp://localhost/xxx.x.x.x:61616] 139 TcpTransport.java
> DEBUG TCP consumer thread starting
> 2006-06-21 15:14:22,816 [Thread-36] 167 JMSUtil.java
> DEBUG returning connection: ActiveMQConnection
> {id=ID:machinename.com-32883-1150924462273-1:0,clientId=null,started=false}
> 2006-06-21 15:14:22,862 [ActiveMQ Transport:
> tcp://localhost/xxx.x.x.x:61616] 85 WireFormatNegotiator.java
> DEBUG Received WireFormat: WireFormatInfo { version=1,
> properties={StackTraceEnabled=true, TightEncodingEnabled=true,
> TcpNoDelayEnabled=true, SizePrefixDisabled=false,
> MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
> 2006-06-21 15:14:22,862 [ActiveMQ Transport:
> tcp://localhost/xxx.x.x.x:61616] 92 WireFormatNegotiator.java
> DEBUG tcp://localhost/xxx.x.x.x:61616 before negotiation:
> OpenWireFormat{version=1, cacheEnabled=false, stackTraceEnabled=false,
> tightEncodingEnabled=false, sizePrefixDisabled=false}
>
> --
> View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4983639
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: hung connecting to broker
Posted by christyc <ca...@avaya.com>.
We're seeing a similiar problem, and wanted to see if this is the same issue.
We have two web apps in Tomcat 2.2.9 that use JMS connections. We were
using ActiveMQ3.0, things were fine, and now we're testing with ActiveMQ 4.0
(and I tried 4.0.1) and the results are:
the first web app starting a JMS connection works fine. When the second web
app tries to start a JMS connection (after successfully getting a
ConnectionFactory as the first web app did also), it hangs. We shut down
Tomcat, leave the broker running, and turn on Tomcat and the first web app
hangs when it tries to start a JMS connection and same with the second web
app. Here's the error log (at the end I have the successful connection):
2006-06-21 15:25:30,864 [Thread-2] 58 JNDIReferenceFactory.java
DEBUG Getting instance of org.apache.activemq.ActiveMQConnectionFactory
2006-06-21 15:25:30,943 [Thread-2] 101 JMSUtil.java
DEBUG successfully obtained connection factory
2006-06-21 15:25:31,312 [Thread-2] 62 WireFormatNegotiator.java
DEBUG Sending: WireFormatInfo { version=1,
properties={TightEncodingEnabled=true, TcpNoDelayEnabled=true,
SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
2006-06-21 15:25:31,318 [Thread-2] 167 JMSUtil.java
DEBUG returning connection: ActiveMQConnection
{id=ID:machinename.com-33231-1150925131041-1:0,clientId=null,started=false}
2006-06-21 15:25:31,312 [ActiveMQ Transport:
tcp://localhost/xxx.x.x.x:61616] 139 TcpTransport.java
DEBUG TCP consumer thread starting
Here is the successful log of this:
2006-06-21 15:14:22,754 [Thread-36] 62 WireFormatNegotiator.java
DEBUG Sending: WireFormatInfo { version=1,
properties={TightEncodingEnabled=true, TcpNoDelayEnabled=true,
SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
2006-06-21 15:14:22,796 [ActiveMQ Transport:
tcp://localhost/xxx.x.x.x:61616] 139 TcpTransport.java
DEBUG TCP consumer thread starting
2006-06-21 15:14:22,816 [Thread-36] 167 JMSUtil.java
DEBUG returning connection: ActiveMQConnection
{id=ID:machinename.com-32883-1150924462273-1:0,clientId=null,started=false}
2006-06-21 15:14:22,862 [ActiveMQ Transport:
tcp://localhost/xxx.x.x.x:61616] 85 WireFormatNegotiator.java
DEBUG Received WireFormat: WireFormatInfo { version=1,
properties={StackTraceEnabled=true, TightEncodingEnabled=true,
TcpNoDelayEnabled=true, SizePrefixDisabled=false,
MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
2006-06-21 15:14:22,862 [ActiveMQ Transport:
tcp://localhost/xxx.x.x.x:61616] 92 WireFormatNegotiator.java
DEBUG tcp://localhost/xxx.x.x.x:61616 before negotiation:
OpenWireFormat{version=1, cacheEnabled=false, stackTraceEnabled=false,
tightEncodingEnabled=false, sizePrefixDisabled=false}
--
View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4983639
Sent from the ActiveMQ - User forum at Nabble.com.
Re: hung connecting to broker
Posted by Hiram Chirino <hi...@hiramchirino.com>.
thanks for opening the issue!
On 6/21/06, Jamie McCrindle <ja...@gmail.com> wrote:
> Hiya,
>
> Raised the JIRA here:
>
> http://issues.apache.org/activemq/browse/AMQ-768
>
> regards,
> jamie.
>
> On 6/21/06, sram <sh...@gmail.com> wrote:
> >
> > did we enter JIRA for this if so which one, I am trying to see if this issue
> > fixed, we are getting similar error on our windows platform
> > --
> > View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4966383
> > Sent from the ActiveMQ - User forum at Nabble.com.
> >
> >
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: hung connecting to broker
Posted by Jamie McCrindle <ja...@gmail.com>.
Hiya,
Raised the JIRA here:
http://issues.apache.org/activemq/browse/AMQ-768
regards,
jamie.
On 6/21/06, sram <sh...@gmail.com> wrote:
>
> did we enter JIRA for this if so which one, I am trying to see if this issue
> fixed, we are getting similar error on our windows platform
> --
> View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4966383
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
Re: hung connecting to broker
Posted by sram <sh...@gmail.com>.
did we enter JIRA for this if so which one, I am trying to see if this issue
fixed, we are getting similar error on our windows platform
--
View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4966383
Sent from the ActiveMQ - User forum at Nabble.com.
Re: hung connecting to broker
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Our transports wait for the wire format to be negotiated. Before
allowing messages to be sent.
Perhaps we need to set a timeout out on that wait so that if a
connection is established but then then gets hung before the
WireFormatInfo is sent, that it can be cleaned up.
Could ya open a new JIRA for this so that we don't forget about your problem?
On 6/2/06, Jamie McCrindle <ja...@gmail.com> wrote:
> hiya,
>
> It's happened and here's a little more info:
>
> > I wonder if you've hit this issue?
> > http://issues.apache.org/activemq/browse/AMQ-732
>
> not sure. or at least, those aren't the symptoms I'm seeing. The
> output from the broker is:
>
> 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)
>
> I'm not setting a clientId but I'm not using a durable topic either (I
> am using an Exclusive consumer, though).
>
> Apologies if this isn't much to go on but I'm at a loss as to what is
> happening. Will get source and start debugging soon, though, which
> might give me a few more clues.
>
> cheers,
> j.
>
> On 6/1/06, James Strachan <ja...@gmail.com> wrote:
> > On 6/1/06, Jamie McCrindle <ja...@gmail.com> wrote:
> > > Hi James,
> > >
> > > Thanks for the quick reply. To complicate things a little, I've
> > > rewritten JmsTemplate to behave a little more like how I believe
> > > ActiveMQ would prefer a JmsTemplate to behave, along with a whole
> > > bunch of utility methods that JmsTemplate is missing. This could be
> > > what's causing the issue and I wouldn't expect you guys to solve it.
> >
> > Cool.
> >
> >
> > > I didn't see any broker errors but I'll keep a look out for next time
> > > it happens. It seems to go away if I get rid of my activemq-data
> > > directory.
> > >
> > > Once it's stuck, it always freezes trying to make an initial
> > > connection to the broker, i.e. it hasn't had time to do anything too
> > > smart (but it could be some kind of unclean shutdown that causes the
> > > issue).
> >
> > I wonder if you've hit this issue?
> > http://issues.apache.org/activemq/browse/AMQ-732
> >
> > --
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> >
>
--
Regards,
Hiram
Re: hung connecting to broker
Posted by Jamie McCrindle <ja...@gmail.com>.
hiya,
It's happened and here's a little more info:
> I wonder if you've hit this issue?
> http://issues.apache.org/activemq/browse/AMQ-732
not sure. or at least, those aren't the symptoms I'm seeing. The
output from the broker is:
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)
I'm not setting a clientId but I'm not using a durable topic either (I
am using an Exclusive consumer, though).
Apologies if this isn't much to go on but I'm at a loss as to what is
happening. Will get source and start debugging soon, though, which
might give me a few more clues.
cheers,
j.
On 6/1/06, James Strachan <ja...@gmail.com> wrote:
> On 6/1/06, Jamie McCrindle <ja...@gmail.com> wrote:
> > Hi James,
> >
> > Thanks for the quick reply. To complicate things a little, I've
> > rewritten JmsTemplate to behave a little more like how I believe
> > ActiveMQ would prefer a JmsTemplate to behave, along with a whole
> > bunch of utility methods that JmsTemplate is missing. This could be
> > what's causing the issue and I wouldn't expect you guys to solve it.
>
> Cool.
>
>
> > I didn't see any broker errors but I'll keep a look out for next time
> > it happens. It seems to go away if I get rid of my activemq-data
> > directory.
> >
> > Once it's stuck, it always freezes trying to make an initial
> > connection to the broker, i.e. it hasn't had time to do anything too
> > smart (but it could be some kind of unclean shutdown that causes the
> > issue).
>
> I wonder if you've hit this issue?
> http://issues.apache.org/activemq/browse/AMQ-732
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
Re: hung connecting to broker
Posted by James Strachan <ja...@gmail.com>.
On 6/1/06, Jamie McCrindle <ja...@gmail.com> wrote:
> Hi James,
>
> Thanks for the quick reply. To complicate things a little, I've
> rewritten JmsTemplate to behave a little more like how I believe
> ActiveMQ would prefer a JmsTemplate to behave, along with a whole
> bunch of utility methods that JmsTemplate is missing. This could be
> what's causing the issue and I wouldn't expect you guys to solve it.
Cool.
> I didn't see any broker errors but I'll keep a look out for next time
> it happens. It seems to go away if I get rid of my activemq-data
> directory.
>
> Once it's stuck, it always freezes trying to make an initial
> connection to the broker, i.e. it hasn't had time to do anything too
> smart (but it could be some kind of unclean shutdown that causes the
> issue).
I wonder if you've hit this issue?
http://issues.apache.org/activemq/browse/AMQ-732
--
James
-------
http://radio.weblogs.com/0112098/
Re: hung connecting to broker
Posted by Jamie McCrindle <ja...@gmail.com>.
Hi James,
Thanks for the quick reply. To complicate things a little, I've
rewritten JmsTemplate to behave a little more like how I believe
ActiveMQ would prefer a JmsTemplate to behave, along with a whole
bunch of utility methods that JmsTemplate is missing. This could be
what's causing the issue and I wouldn't expect you guys to solve it.
I didn't see any broker errors but I'll keep a look out for next time
it happens. It seems to go away if I get rid of my activemq-data
directory.
Once it's stuck, it always freezes trying to make an initial
connection to the broker, i.e. it hasn't had time to do anything too
smart (but it could be some kind of unclean shutdown that causes the
issue).
cheers,
j.
On 6/1/06, James Strachan <ja...@gmail.com> wrote:
> Is there any errors occurring on the broker?
>
> BTW please read this page...
> http://incubator.apache.org/activemq/spring-support.html
>
> in particular you should always use the PooledConnectionFactory if you
> want to use Spring's JmsTemplate - unless you are using JCA
>
> On 6/1/06, Jamie McCrindle <ja...@gmail.com> wrote:
> > hi,
> >
> > every now and again my client hangs while connecting to the broker.
> > I'm using the incubating-activemq 4.0 release on windows XP,
> > connecting via tcp://localhost:61616. Stacktrace is as follows:
> >
> > "main" prio=6 tid=0x00037b38 nid=0x875c in Object.wait() [0x0007f000..0x0007fc40
> > ]
> > at java.lang.Object.wait(Native Method)
> > - waiting on <0x03274110> (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 <0x03274110> (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 <0x03276a30> (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 <0x02b60208> (a org.apache.activemq.ActiveMQConnection)
> > at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:
> > 435)
> > at com.vnocore.empower.jms.JmsTemplate.afterPropertiesSet(JmsTemplate.ja
> > va:217)
> > at org.springframework.beans.factory.support.AbstractAutowireCapableBean
> > Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1059)
> > at org.springframework.beans.factory.support.AbstractAutowireCapableBean
> > Factory.createBean(AbstractAutowireCapableBeanFactory.java:363)
> > at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
> > (AbstractBeanFactory.java:226)
> > - locked <0x030ebdf0> (a java.util.HashMap)
> > at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
> > (AbstractBeanFactory.java:147)
> > at org.springframework.beans.factory.support.DefaultListableBeanFactory.
> > preInstantiateSingletons(DefaultListableBeanFactory.java:275)
> > at org.springframework.context.support.AbstractApplicationContext.refres
> > h(AbstractApplicationContext.java:320)
> >
> > regards,
> > jamie.
> >
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
Re: hung connecting to broker
Posted by James Strachan <ja...@gmail.com>.
Is there any errors occurring on the broker?
BTW please read this page...
http://incubator.apache.org/activemq/spring-support.html
in particular you should always use the PooledConnectionFactory if you
want to use Spring's JmsTemplate - unless you are using JCA
On 6/1/06, Jamie McCrindle <ja...@gmail.com> wrote:
> hi,
>
> every now and again my client hangs while connecting to the broker.
> I'm using the incubating-activemq 4.0 release on windows XP,
> connecting via tcp://localhost:61616. Stacktrace is as follows:
>
> "main" prio=6 tid=0x00037b38 nid=0x875c in Object.wait() [0x0007f000..0x0007fc40
> ]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x03274110> (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 <0x03274110> (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 <0x03276a30> (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 <0x02b60208> (a org.apache.activemq.ActiveMQConnection)
> at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:
> 435)
> at com.vnocore.empower.jms.JmsTemplate.afterPropertiesSet(JmsTemplate.ja
> va:217)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBean
> Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1059)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBean
> Factory.createBean(AbstractAutowireCapableBeanFactory.java:363)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
> (AbstractBeanFactory.java:226)
> - locked <0x030ebdf0> (a java.util.HashMap)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
> (AbstractBeanFactory.java:147)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.
> preInstantiateSingletons(DefaultListableBeanFactory.java:275)
> at org.springframework.context.support.AbstractApplicationContext.refres
> h(AbstractApplicationContext.java:320)
>
> regards,
> jamie.
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: hung connecting to broker
Posted by sram <sh...@gmail.com>.
Is this problem fixed if so in which version, we seems to be having ame issue
on windows env only
--
View this message in context: http://www.nabble.com/hung-connecting-to-broker-t1717047.html#a4966032
Sent from the ActiveMQ - User forum at Nabble.com.