geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevan Miller <kevan.mil...@gmail.com>
Subject Re: Maybe a ActiveMQ Bug?
Date Wed, 04 Jun 2008 12:17:45 GMT

On Jun 4, 2008, at 3:06 AM, Jochen Zink wrote:

> Hello,
>
> We are running Geronimo 2.0.1. We are using a JMS-Queue with one  
> Receiver (MDB). Sometimes we get this Exception on Geronimo’s stdout:
> Exception in thread "ActiveMQ Transport: tcp://localhost/ 
> 127.0.0.1:61616" java.lang.IndexOutOfBoundsException: Index: 0,  
> Size: 0
> 	at  
> edu 
> .emory 
> .mathcs 
> .backport 
> .java 
> .util 
> .concurrent.CopyOnWriteArrayList.remove(CopyOnWriteArrayList.java:346)
> 	at  
> org 
> .apache 
> .activemq 
> .ra 
> .ServerSessionPoolImpl 
> .getExistingServerSession(ServerSessionPoolImpl.java:159)
> 	at  
> org 
> .apache 
> .activemq 
> .ra 
> .ServerSessionPoolImpl.getServerSession(ServerSessionPoolImpl.java: 
> 114)
> 	at  
> org 
> .apache 
> .activemq 
> .ActiveMQConnectionConsumer.dispatch(ActiveMQConnectionConsumer.java: 
> 136)
> 	at  
> org 
> .apache 
> .activemq.ActiveMQConnection.onCommand(ActiveMQConnection.java:1479)
> 	at  
> org 
> .apache 
> .activemq 
> .transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:95)
> 	at  
> org 
> .apache 
> .activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> 	at  
> org 
> .apache 
> .activemq 
> .transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java: 
> 133)
> 	at  
> org 
> .apache 
> .activemq 
> .transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> 	at  
> org 
> .apache 
> .activemq.transport.TransportSupport.doConsume(TransportSupport.java: 
> 84)
> 	at  
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: 
> 137)
> 	at java.lang.Thread.run(Thread.java:619)
>
> After this, the ActiveMQ System seems to hang. Only a restart helps.  
> Is this a Bug? I found this:
> http://issues.apache.org/activemq/browse/AMQ-1246
>
> It sounds a little bit similar.
>
> Is there any workaround known?

Hi Jochen,
Yes, it's an ActiveMQ bug. I believe it was fixed by http://issues.apache.org/activemq/browse/AMQ-1215

Geronimo 2.1.1 includes the fixed version of ActiveMQ (4.1.2). Is G  
2.1.1 an option for you? We haven't tested AMQ 4.1.2 with G 2.0.x,  
although it should be doable...

--kevan


Mime
View raw message