openjms

Hello everybody,

I encounter the following problem using JMS.
When I make huge publications, and I start one subscriber that subscribe =
to=20
several topics evrything is fine.=20
However if I start one or more subscribers sometimes the JMS server stop =
to send=20
update to all subscribers.=20
When I truss JMS Server I can see that it continues to receive update but=
 it=20
does not dispatch this update to subscribers. Just after I kill the subsc=
riber=20
which hang the JMS server other subscribers restart to receive update.

I also have the same problem when I start several subscribers and one of =
it try=20
to make unsubscribe.

It looks like a mutex lock, but I do not how it could happen. Sometimes b=
ut not=20
always the JMS server log an exception ConccurentModificationException.

Any idea will be greatly appreciate.

Thanks

Arnau ROCHE

Hi everybody,

OpenJms Server send the following exception and hang.
If someone could help me to understand what is happening.

I also have this message when I truss the OpenJms Server :
getsockname(25, 0xEE380EE0, 0xEE380EDC, 1)      =3D 0
connect(25, 0xEE380D30, 16, 1)                  Err#146 ECONNREFUSED=20

Thanks a lot for any help.

Arnaud ROCHE

14:14:50.383 ERROR [RMI TCP Connection(4)-10.10.210.25] - Exception in=20
DestinationManager.messageAdded
java.util.ConcurrentModificationException
        at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
        at java.util.HashMap$ValueIterator.next(HashMap.java:812)
        at java.util.AbstractCollection.toArray(AbstractCollection.java:1=
25)
        at org.exolab.jms.messagemgr.ConsumerManager.
hasActiveConsumers(ConsumerManager.java:621)
        at org.exolab.jms.messagemgr.DestinationManager.
messageAdded(DestinationManager.java:622)
        at org.exolab.jms.messagemgr.MessageMgr.notifyOnAddMessage(Messag=
eMgr.
java:661)
        at org.exolab.jms.messagemgr.MessageMgr.
addNonPersistentMessage(MessageMgr.java:332)
        at org.exolab.jms.messagemgr.MessageMgr.add(MessageMgr.java:283)
        at org.exolab.jms.server.JmsServerSession.sendMessage(JmsServerSe=
ssion.
java:350)
        at org.exolab.jms.server.rmi.RmiJmsServerSession.
sendMessage(RmiJmsServerSession.java:174)
        at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.
invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java=
:261)
        at sun.rmi.transport.Transport$1.run(Transport.java:148)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport=
.java:
460)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.
run(TCPTransport.java:701)
        at java.lang.Thread.run(Thread.java:534)

Bugs item #1058427, was opened at 2004-11-01 16:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1058427&group_id=54559

Category: server
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Dmitri Afanassiev (dmitria)
Assigned to: Nobody/Anonymous (nobody)
Summary: QueueDestinationCache throws IndexOutOfBoundsException

Initial Comment:
03:14:47.605 ERROR [RMI TCP Connection(1027)-
192.168.254.17] - Failed to make message persistent
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
        at java.util.LinkedList.entry(LinkedList.java:343)
        at java.util.LinkedList.get(LinkedList.java:286)
        at java.util.Collections$SynchronizedList.get
(Collections.java:1323)
        at 
org.exolab.jms.messagemgr.QueueDestinationCache.getE
ndpointForMessage(QueueDestinationCache.java:459)
        at 
org.exolab.jms.messagemgr.QueueDestinationCache.persi
stentMessageAdded(QueueDestinationCache.java:384)
        at 
org.exolab.jms.messagemgr.MessageMgr.notifyOnAddPersi
stentMessage(MessageMgr.java:717)
        at 
org.exolab.jms.messagemgr.MessageMgr.addPersistentMe
ssage(MessageMgr.java:386)
        at org.exolab.jms.messagemgr.MessageMgr.add
(MessageMgr.java:281)
        at 
org.exolab.jms.server.JmsServerSession.sendMessage
(JmsServerSession.java:350)
        at 
org.exolab.jms.server.rmi.RmiJmsServerSession.sendMess
age(RmiJmsServerSession.java:174)
        at java.lang.reflect.Method.invoke(Native Method)
        at sun.rmi.server.UnicastServerRef.dispatch
(UnicastServerRef.java:236)
        at sun.rmi.transport.Transport$1.run
(Transport.java:147)
        at java.security.AccessController.doPrivileged
(Native Method)
        at sun.rmi.transport.Transport.serviceCall
(Transport.java:143)
        at 
sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:460)
        at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.ru
n(TCPTransport.java:701)
        at java.lang.Thread.run(Thread.java:479)

I have system with one QueueSender submitting 
thousands of persistent messages to one queue and 
several QueueReceiver's retrieving messages from this 
queue. Number of receiver's changes time to time (some 
connecting and some disconnecting) and sometimes (in 
my test it happens between 300k..1M messages) I'm 
catching this exception and QueueSender.send() fails. It 
looks like problem is in "incomplete" synchronization of  
_consumers object. However, additional synchronization 
may cause performance degradation and I preferred just 
to add special exception handling in 
QueueDestinationCache class (reset index to 0 after 
such exception, verify size of the list and try again).


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1058427&group_id=54559