SourceForge.net
2004-07-04 12:33:57 UTC
Bugs item #984891, was opened at 2004-07-04 22:33
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=984891&group_id=54559
Category: transport
Group: v0.7.6.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: ConcurrentModificationException on server shutdown
Initial Comment:
(Originally from
http://article.gmane.org/gmane.comp.java.openjms.devel
/616)
Hello,
I sporadically get a
java.util.ConcurrentModificationException on the
client side when i shut down the openjms server. This is
annoying
because my ExceptionListener won't get called and this
in turn prevents
my failover to be triggered. I'm using openjms-0.7.6.1.
2004-05-19 12:12:53,473 [MultiplexConnection-
XXX.XXX.XXX.XXX:36342]
DEBUG org.exolab.core.mipc.Demultiplexer -
Demultiplexer terminating on exception
java.io.EOFException
at java.io.DataInputStream.readInt
(DataInputStream.java:397)
at
org.exolab.core.mipc.MessageInputStream.receive
(MessageInputStream.java:95)
at org.exolab.core.mipc.Demultiplexer.run
(Demultiplexer.java:153)
at
org.exolab.core.mipc.MultiplexConnection.run
(MultiplexConnection.java:240)
2004-05-19 12:12:53,478 [MultiplexConnection-
XXX.XXX.XXX.XXX:36342]
DEBUG org.exolab.core.mipc.MultiplexConnection -
MultiplexConnection
terminating on exception
java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next
(Hashtable.java:976)
at org.exolab.core.mipc.Demultiplexer.run
(Demultiplexer.java:172)
at
org.exolab.core.mipc.MultiplexConnection.run
(MultiplexConnection.java:240)
I had a look at org.exolab.core.mipc.Demultiplexer and
after adding a
bit of synchronisation it worked fine.
Regards
Andre Gebers
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=984891&group_id=54559
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=984891&group_id=54559
Category: transport
Group: v0.7.6.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: ConcurrentModificationException on server shutdown
Initial Comment:
(Originally from
http://article.gmane.org/gmane.comp.java.openjms.devel
/616)
Hello,
I sporadically get a
java.util.ConcurrentModificationException on the
client side when i shut down the openjms server. This is
annoying
because my ExceptionListener won't get called and this
in turn prevents
my failover to be triggered. I'm using openjms-0.7.6.1.
2004-05-19 12:12:53,473 [MultiplexConnection-
XXX.XXX.XXX.XXX:36342]
DEBUG org.exolab.core.mipc.Demultiplexer -
Demultiplexer terminating on exception
java.io.EOFException
at java.io.DataInputStream.readInt
(DataInputStream.java:397)
at
org.exolab.core.mipc.MessageInputStream.receive
(MessageInputStream.java:95)
at org.exolab.core.mipc.Demultiplexer.run
(Demultiplexer.java:153)
at
org.exolab.core.mipc.MultiplexConnection.run
(MultiplexConnection.java:240)
2004-05-19 12:12:53,478 [MultiplexConnection-
XXX.XXX.XXX.XXX:36342]
DEBUG org.exolab.core.mipc.MultiplexConnection -
MultiplexConnection
terminating on exception
java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next
(Hashtable.java:976)
at org.exolab.core.mipc.Demultiplexer.run
(Demultiplexer.java:172)
at
org.exolab.core.mipc.MultiplexConnection.run
(MultiplexConnection.java:240)
I had a look at org.exolab.core.mipc.Demultiplexer and
after adding a
bit of synchronisation it worked fine.
Regards
Andre Gebers
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=984891&group_id=54559