[JBoss Messaging] - Re: JMS Server Locks Up
by clebert.suconicï¼ jboss.com
rtm333,
It would help if you could attach a complete stack trace here:
http://jira.jboss.org/jira/browse/JBMESSAGING-836
In particular... I want to know what is holding this thread to finish, ont the future task:
| "WorkerThread#11[11.222.111.222:3824]" prio=10 tid=0x00335e48 nid=0x1d01 in Object.wait() [0xa30fe000..0xa30ffb70]
| at java.lang.Object.wait(Native Method)
| - waiting on <0xbb5662a0> (a org.jboss.messaging.util.Future)
| at java.lang.Object.wait(Object.java:474)
| at org.jboss.messaging.util.Future.getResult(Future.java:51)
| - locked <0xbb5662a0> (a org.jboss.messaging.util.Future)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.stop(ServerConsumerEndpoint.java:677)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.setStarted(ServerSessionEndpoint.java:822)
| - locked <0xbb51f210> (a java.util.HashMap)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.setStarted(ServerConnectionEndpoint.java:753)
| - locked <0xbb51f358> (a EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.stop(ServerConnectionEndpoint.java:280)
| - locked <0xbb51f1b8> (a org.jboss.jms.server.endpoint.ServerConnectionEndpoint)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$stop$aop(ConnectionAdvised.java:99)
| at sun.reflect.GeneratedMethodAccessor136.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aop.Advisor.dynamicInvoke(Advisor.java:723)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:101)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:127)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:715)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:552)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016615#4016615
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4016615
19Â years, 2Â months
[EJB 3.0] - Re: MDB deployment problem
by weston.priceï¼ jboss.com
Hmmm...it appears that the resource adapter name is not being set correctly. Can you tell me what version of EJB3 you are using? Also, I am not sure why are using annotations and a ejb-jar.xml file. Typically you would only use the XML configuration if there was something you needed to override.
The reason I ask is that you have different transaction attributes in your annotation and your XML file. In the former you specify you want BMT and in the latter CMT.
To explicitly set the resource adapter name you can (depending on your EJB3 version)
1) Use the @ResourceAdapter annotation
2) Use the <resource-adapter> element in a jboss.xml file.
For JMS, this should be set automatically to the jms-ra.rar. However, I don't believe older version of EJB3 did this by default.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016614#4016614
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4016614
19Â years, 2Â months