Re: NullPointerException in AMQMessageStore.addMessage in AMQ 5.2

Not sure what you mean by "raise an issue". You mean if I had submitted a bug? No, I haven't yet since I didn't have a readily reproducible test cases. Here is the full stack that wraps the root cause that I posted before. org.springframework.jms.UncategorizedJmsException: Uncategorized except

Re: NullPointerException in AMQMessageStore.addMessage in AMQ 5.2

Hi I posted this a while back and we are still having this issue. It seems happen only when there is "large" load, meaning maybe 1500-2500 messages in the queue. So my guess is we might be hitting some resource limit and hitting this issue. Any idea? Thanks -- View this message in context:

NullPointerException in AMQMessageStore.addMessage in AMQ 5.2

Hi, Intermittently, we get a NullPointerException while sending a message out and not sure what's causing it. Caused by: java.lang.NullPointerException at org.apache.activemq.store.amq.AMQMessageStore.addMessage(AMQMessageStore.java:129) at org.apache.activemq.broker.region.Queue

Re: connection failover using ActiveMQ 5.2

Looks like timeout parameter has been replaced by maxReconnectAttempts. -- View this message in context: http://www.nabble.com/connection-failover-using-ActiveMQ-5.2-tp23374917p23377412.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: connection failover using ActiveMQ 5.2

Reading FailoverTransportFactory.java, I see the code that causes the exception to occur, but I don't understand the logic. It seems like this check is added later. I don't see the same check in 4.1.2 public Transport createTransport(CompositeData compositData) throws IOException {

connection failover using ActiveMQ 5.2

Hello, I am trying to set up auto-reconnect per http://activemq.apache.org/failover-transport-reference.html instruction failover:(tcp://primary:61616)?timeout=3000 But for some reason, I am getting IllegalArgumentException when timeout attribute is set. Caused by: javax.jms.JMSException: C

Messages get stuck temporarily

Hi, We have messages that get submitted to the queue daily. Every so often, these messages get stuck in the queue until another message arrives the next day. It almost seems like the second message "pushes" out the first... Any idea why? Is there some configuration property that's causing t

Re: ClassCastException with VirtualTopic on 5.1

org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:196) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183) at java.lang.Thread.run(Thread.java:619) jydev

Re: ClassCastException with VirtualTopic on 5.1

eling it might be related to that... Thanks! jydev wrote: > > Hi Aaron, > > Thanks for your reply. I tried running our configuration at home (not > using your test class), but unable to reproduce. Only thing I can think > that's different is the OS. We use CentOS at w

Re: ClassCastException with VirtualTopic on 5.1

> Thanks, >Aaron > > On Fri, May 16, 2008 at 6:17 PM, jydev <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> Getting the following error with VirtualTopic on 5.1, when there are more >> than one topic subscribers. >> >>

ClassCastException with VirtualTopic on 5.1

listeners ok even though broker is spitting out the errors above. But I want to make sure that there would be no weird side-effects due to the error. Thanks you in advance jydev -- View this message in context: http://www.nabble.com/ClassCastException-with-VirtualTopic-on-5.1