JmsActivation exception

[vachacz]

i'm reciving strange when jboss is running. it appears about with 10 seconds delay

12:18:43,982 INFO [JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1641c0(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@e07e6b destination=topic/testTopic isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
12:18:43,988 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1641c0(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@e07e6b destination=topic/testTopic isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
java.lang.IllegalAccessError: tried to access method org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.<init>(Lorg/jboss/ejb3/mdb/MessagingContainer;)V from class org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory
 at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createProxy(JBossMessageEndpointFactory.java:148)
 at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:131)
 at org.jboss.resource.adapter.jms.inflow.JmsServerSession.setup(JmsServerSession.java:115)
 at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.setupSessions(JmsServerSessionPool.java:191)
 at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.start(JmsServerSessionPool.java:87)
 at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:515)
 at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:288)
 at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:232)
 at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:568)
 at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
 at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
 at java.lang.Thread.run(Thread.java:595)

can anyone give me a hint how to solve this problem

thanks in advance
Luc

[clebert.suconic]

I looks like you have a classIsolation problem.

Take a look on documentation about how to scope your application

[weston.price]

It actually looks more like an EJB3 version problem. What version of EJB3 are you using, and how did you deploy/install it?

[pankajgrover]

I am actually getting the same error while deploying EJB 3.0 trail application that JBOSS provides. Did someone get the same exception trying to deploy the EJB 3.0 trail application ? If yes, please let me know what do I need to do to get rid of this error

It seems the stateful session bean, Stateless session bean and entity beans deployed just fine. It is the MDB that caused this error possibly because the JMS server could not be created.

I had downloaded the jboss-EJB-3.0_RC9-FD and used the install.xml (ant script) for making my JBOSS (4.0.5) ejb 3.0 compliant.

Thanks
Pankaj Grover

[seidler2547]

A bit late, but I found this thread and just wanted to say: we had the problem too, and the reason was, that there was a jboss-ejb3-client.jar in the server/default/lib directory, after deleting that, there were no duplicate classes anymore and it worked.

Stefan

[jessiezam]

Try activating the JMS message inflow from jmsra.rar.
Follow this steps:

1. goto {JBOSS_HOME}/server/{YOURCONFIG}/conf
2. open the standardjboss.xml file
3. scroll down and locate this comment "<!-- Uncomment to use JMS message inflow from jmsra.rar "
4. uncomment the "<invoker-proxy-binding>" under it.
5. restart your jboss.

Jessie

[jessiezam]

BTW, what i meant in step 4 is to uncomment the whole "<invoker-proxy-binding>" node.

Jessie