This week's book giveaway is in the OCMJEA forum.
We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes jboss jms UnsupportedOperationException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "jboss jms UnsupportedOperationException" Watch "jboss jms UnsupportedOperationException" New topic
Author

jboss jms UnsupportedOperationException

ruchi Agrawal
Greenhorn

Joined: Nov 17, 2009
Posts: 1
Hello ,

We have a server and client set up in java , where server code is deployed on jboss. It sends some events to client on periodic basis.
I have started seeing the following exception in my log quite frequently :
java.lang.UnsupportedOperationException
at EDU.oswego.cs.dl.util.concurrent.SyncCollection.add(SyncCollection.java:355)
at org.jboss.jms.client.state.HierarchicalStateSupport.<init>(HierarchicalStateSupport.java:63)
at org.jboss.jms.client.state.SessionState.<init>(SessionState.java:135)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateSessionDelegate(StateCreationAspect.java:125)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect2.invoke(StateCreationAspect2.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ConnectionAspect.handleCreateSessionDelegate(ConnectionAspect.java:164)
at sun.reflect.GeneratedMethodAccessor146.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.createSessionDelegate(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.createSessionInternal(JBossConnection.java:269)
at org.jboss.jms.client.JBossConnection.createSession(JBossConnection.java:91)
at com.ipaccess.omcr.server.session.AsyncMessageProducerBean.postMessageToQueue(AsyncMessageProducerBean.java:94)
at com.ipaccess.omcr.server.session.AsyncMessageProducerBean.pushMessageOnFMQueue(AsyncMessageProducerBean.java:70)
at sun.reflect.GeneratedMethodAccessor238.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy362.pushMessageOnFMQueue(Unknown Source)
at com.ipaccess.omcr.server.session.AlarmUpdateHandlerBean.sendEventsToClient(AlarmUpdateHandlerBean.java:1784)
at com.ipaccess.omcr.server.session.AlarmUpdateHandlerBean.replaceAlarmListNew(AlarmUpdateHandlerBean.java:835)
at com.ipaccess.omcr.server.session.AlarmUpdateHandlerBean.updateClient(AlarmUpdateHandlerBean.java:1759)
at sun.reflect.GeneratedMethodAccessor241.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237)

Please let me know if somebody else has seen this or has some clue as why this is happening .

Greg Charles
Sheriff

Joined: Oct 01, 2001
Posts: 2849
    
  11

Interesting. You must be using a particularly old version of JBoss, right? The Oswego.edu concurrency package was created by Doug Lea, but pretty much superseded by the java.util.concurrency package some years back. I had no idea JBoss was still using them. In any case, I looked up the source code, and it looks like that exception gets thrown if the thread gets interrupted while trying to acquire the mutex, which is what makes the collection synchronized. I'm not sure if there's anything you can do about that though, other than upgrading to a newer version of JBoss.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jboss jms UnsupportedOperationException