JBossAS 5.1.0: ConcurrentModificationException in org.jboss.jms.client.container.ClosedInterceptor

[kevin.lohmann]

Hi *,

we are using JBossAS 5.1.0.

From time to time our client receives following ConcurrentModificationException when we call Connection.close():

java.util.ConcurrentModificationException
    at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
    at java.util.HashMap$KeyIterator.next(Unknown Source)
    at EDU.oswego.cs.dl.util.concurrent.SyncCollection$SyncCollectionIterator.next(SyncCollection.java:483)
    at java.util.AbstractCollection.addAll(Unknown Source)
    at java.util.HashSet.<init>(Unknown Source)
    at org.jboss.jms.client.container.ClosedInterceptor.maintainRelatives(ClosedInterceptor.java:295)
    at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:165)
    at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
    at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
    at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java)
    at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131)

I couldn't find anything here or in www, is it a known bug? Can we (the client) do anything except catch the ConcurrentModificationException?

Thanks in advance,

Kevin

[kevin.lohmann]

So, nobody can give me a hint?

I just can't surround every jms-api-call with a try-catch (catch everything), because there is chance for a ConcurrentModificationException, or a NPe, or ...!

Any advices would be nice!

Thx & cheers,

Kevin

[jaikiran]

I'll move this to JBoss Messaging forum. Let's see if someone there knows whether this is a known issue.

[kevin.lohmann]

Here, too, anyone has a clue about whether this is a known bug or not?