geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-688) ActiveMQActivationSpec default maxSessions value reset to 0 by Geronimo
Date Sat, 27 Aug 2005 03:25:05 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-688?page=all ]

Aaron Mulder updated GERONIMO-688:
----------------------------------

    Fix Version: 1.0-M5

Can we confirm that this is fixed for M5?

> ActiveMQActivationSpec default maxSessions value reset to 0 by Geronimo
> -----------------------------------------------------------------------
>
>          Key: GERONIMO-688
>          URL: http://issues.apache.org/jira/browse/GERONIMO-688
>      Project: Geronimo
>         Type: Bug
>     Versions: 1.0-M4
>     Reporter: Ivan Dubrov
>      Fix For: 1.0-M5

>
> The org.activemq.ra.ActiveMQActivationSpec  sets its maxSessions property to the 10 by
default, but during application deployment if maxSessions is not set manually, Geronimo GBeans
runtime resets this value to the 0, making MDB beans not working.
> Here is the exception thrown during sending message to the topic:
> 13:24:04,749 WARN  [TransportChannelSupport] No Packet found to match Receipt correlationId:
9
> java.util.NoSuchElementException
>         at java.util.LinkedList.remove(LinkedList.java:579)
>         at java.util.LinkedList.removeFirst(LinkedList.java:131)
>         at org.activemq.ra.ServerSessionPoolImpl.getExistingServerSession(ServerSessionPoolImpl.java
> :116)
>         at org.activemq.ra.ServerSessionPoolImpl.getServerSession(ServerSessionPoolImpl.java:98)
>         at org.activemq.ActiveMQConnectionConsumer.dispatchToSession(ActiveMQConnectionConsumer.java
> :154)
>         at org.activemq.ActiveMQConnectionConsumer.dispatch(ActiveMQConnectionConsumer.java:116)
>         at org.activemq.ActiveMQConnection.consume(ActiveMQConnection.java:937)
>         at org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.ja
> va:374)
>         at org.activemq.transport.TransportChannelSupport.doConsumePacket(TransportChannelSupport.ja
> va:368)
>         at org.activemq.transport.tcp.TcpTransportChannel.run(TcpTransportChannel.java:310)
>         at java.lang.Thread.run(Thread.java:534)
> The reason is that maxSessions = 0, and sessions list size = 0 too, so it tries to get
existent session (as maximum size is reached) from the empty list.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message