[jboss-user] [JBoss Messaging] - MBean Servic cannot open jms session
chip_schoch
do-not-reply at jboss.com
Sun Jun 3 11:17:10 EDT 2007
I upgraded to JBossAS 4.2.0.GA and JBM1.3.0.GA and when I deploy my message handling MBean I get the following when it tries to create a jms session. I am not quite sure what this is even saying to me. Any insight as to what I need to do to fix this would be sincerely appreciated.
2007-06-03 11:04:37,988 INFO [com.eLynx.Messaging.MessageReceiver] EMail ServiceService MessageReceiver thread started...
| 2007-06-03 11:04:37,988 INFO [com.eLynx.Messaging.MessageReceiver] EMail Service Service started.
| 2007-06-03 11:04:37,988 DEBUG [com.eLynx.Service.EMail.EMailService] Started eLynx.EMail:service=EMailService
| 2007-06-03 11:04:45,315 ERROR [com.eLynx.Messaging.MessageReceiver] Exception running MessageReceiver [thread id=115].
| java.lang.NullPointerException
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:86)
| 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.eLynx.Messaging.MessageReceiver.run(MessageReceiver.java:552)
| 2007-06-03 11:04:46,424 ERROR [com.eLynx.Messaging.MessageReceiver] Exception closing JMS Session objects.
| java.lang.NullPointerException
| at org.jboss.jms.client.container.ClosedInterceptor.maintainRelatives(ClosedInterceptor.java:288)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:165)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java)
| at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131)
| at com.eLynx.Messaging.MessageReceiver.run(MessageReceiver.java:629)
Here is the code snippet where it occurs:
// Lookup our JMS connection factory
| InitialContext context = getInitialContext ();
| QueueConnectionFactory connFactory = (QueueConnectionFactory) context
| .lookup (getProperty (MessageReceiverProperties
| .PropJMSConnectoryFactory));
|
| // Get our jms connection
| m_jmsConnection = connFactory.createQueueConnection ();
|
| // Get our jms session
| m_jmssession = m_jmsConnection.createSession (false, Session.AUTO_ACKNOWLEDGE);
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050748#4050748
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050748
More information about the jboss-user
mailing list