This content has been marked as final.
Show 22 replies
-
15. Re: MBean Servic cannot open jms session
clebert.suconic Jun 4, 2007 4:44 PM (in response to chipschoch)Also.. .should we debug AOP and identify why this happened.. .or should we just fix the issue?
BTW: I will be moving this thread to Development forum, since it became a development thread now. -
16. Re: MBean Servic cannot open jms session
timfox Jun 4, 2007 4:56 PM (in response to chipschoch)Nice catch Clebert.
We should probably get Kabir's opinion on this. -
17. Re: MBean Servic cannot open jms session
timfox Jun 4, 2007 5:05 PM (in response to chipschoch)We should add a smoke test (example) for this too.
-
18. Re: MBean Servic cannot open jms session
clebert.suconic Jun 4, 2007 5:29 PM (in response to chipschoch)"timfox" wrote:
We should add a smoke test (example) for this too.
I have already talked to Tim personally.. but just as a reference to everybody:Clebert wrote:
I have changed the MDBExample to be a scoped EAR. -
19. Re: MBean Servic cannot open jms session
ankurkkapadia Jun 11, 2007 10:26 PM (in response to chipschoch)I had the same issue and it was because I deployed the ear in a scoped manner. Once I removed the scoping everything worked fine
-
20. Re: MBean Servic cannot open jms session
adrian.brock Jan 10, 2008 10:11 AM (in response to chipschoch)The JIRA issues says this is fixed.
But I still see it running in JBoss Head with the new claasloader:2008-01-10 15:48:33,126 ERROR [org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager] Failed to start connection info java.lang.NullPointerException at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:87) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106) at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106) at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java) at org.jboss.jms.client.delegate.ClientConnectionDelegate.start(ClientConnectionDelegate.java) at org.jboss.jms.client.JBossConnection.start(JBossConnection.java:121) at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.start(ClusterConnectionManager.java:664) at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.ensureAllConnectionsCreated(ClusterConnectionManager.java:426) at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.notify(ClusterConnectionManager.java:247) at org.jboss.messaging.core.impl.DefaultClusterNotifier.sendNotification(DefaultClusterNotifier.java:72) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.putReplicantLocally(MessagingPostOffice.java:1167) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.put(MessagingPostOffice.java:1420) at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.registerConnectionFactory(ConnectionFactoryJNDIMapper.java:240) at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:201) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
What is the issue with scoping why does it make a difference?
Seems like you (or aop) have a bad assumption related to classloading? -
21. Re: MBean Servic cannot open jms session
qylin Dec 23, 2008 9:22 AM (in response to chipschoch)"chip_schoch" wrote:
Well Tim, here is what I have determined. I have three MBean Services that handle jms messages. They are essentially the same codebase. If any one of them has a scoped loader I get the exception I sent initially.
But only on the ones that load and initialize AFTER the one with the scoped loader. If a service without it loads and initializes before another one that has its loader scoped, then the first one works fine.
Not scoping the loader is not really an issue for me except that without it I don't seem to be able to separate my log4j log files on a per service basis using the TCLFilter. Is there any known work around for this?
Thanks
Hi, It seems I have the same issue. I'm a newer of jboss. First of all, will you please explain the word scoped?
The second is I have the same NPE when creating a connection.
The following is my codes.ConnectionFactory factory = (ConnectionFactory) ctx .lookup("java:/JmsXA"); Destination dest = (Destination) ctx.lookup("topic/testTopic"); Connection conn = factory.createConnection();
Is this a bug of jboss?
Thank you very much. -
22. Re: MBean Servic cannot open jms session
gaohoward Dec 23, 2008 9:49 AM (in response to chipschoch)Hi Qylin, i suggest you post your question to the user forum :
http://www.jboss.com/index.html?module=bb&op=viewforum&f=238
and give more details of your issue, like jboss version, jbm version, the use case etc.