[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE booting Embedded JBoss from trunk

[clebert.suconic@jboss.com]

This will require more time debugging this...

I have taken the action of looking into this, and there is something going on with aop.


Our aspects are being deployed, but for some reason the PerVM aspect we use is not being applied here.


I have added a trace to our code, and I could see where the connection is created:


   [testng] 2008-01-09 14:45:02,131 13889 INFO  [org.jboss.jms.delegate.ConnectionFactoryDelegate] @WorkManager(1)-2 connectionDelegate created = ConnectionDelegate[31261706, ID=g-iasbc8bf-1-aqkbc8bf-ssqw43-110j3, SID=0] state = null
  |    [testng] java.lang.Exception: trace
  |    [testng]     at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:197)
  |    [testng]     at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
  |    [testng]     at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
  |    [testng]     at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
  |    [testng]     at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
  |    [testng]     at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137)
  |    [testng]     at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
  |    [testng]     at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
  |    [testng]     at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:401)
  |    [testng]     at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:339)
  |    [testng]     at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:692)
  |    [testng]     at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
  |    [testng]     at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
  |    [testng]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  |    [testng]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  |    [testng]     at java.lang.Thread.run(Thread.java:595)
  |    [testng] 2008-01-09 14:45:02,151 13909 WARN  [org.jboss.resource.adapter.jms.inflow.JmsActivation] @WorkManager(1)-2 Failure in jms activation org.jboss.resour

And we should have StateCreationAspect on the stack trace,  before the ConnectionFactoryDelegate. So.. there is something going on with AOP.
(which is an InVM aspect),

So... someone should debug this from the AOP point of view.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118434#4118434

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118434