[jboss-user] [Messaging, JMS & JBossMQ] - Re: MDB login for topic subscriber
pacwest
do-not-reply at jboss.com
Thu Feb 22 13:48:00 EST 2007
I also have similar issues. The application was working without any issues with HSQL. But when I ported the JMS tables to Sybase, I started getting the following error:-
2007-02-22 10:41:48,683 WARN {Timer-3} [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:756)
at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:172)
at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:95)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:519)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:208)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:378)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:168)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:741)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorSupport.java:274)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:694)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:188)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2007-02-22 10:41:48,687 ERROR {Timer-3} [org.jboss.resource.adapter.jms.JmsSessionFactoryImpl] could not create session
javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:756)
at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:172)
at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:95)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:519)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:208)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:378)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:168)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:741)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorSupport.java:274)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:694)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:188)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2007-02-22 10:41:48,688 ERROR {Timer-3} [com.pacwest.commons.jms.Sender] [sendObject] Failure closing producer:
java.lang.NullPointerException
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:77)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2007-02-22 10:41:48,690 ERROR {Timer-3} [com.pacwest.commons.jms.Sender] [sendObject] Failure closing session:
java.lang.NullPointerException
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:87)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2007-02-22 10:41:48,691 ERROR {Timer-3} [com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener] An Exception was received.
javax.jms.JMSException: Could not create a session: javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:392)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.notifyOrderScheduling(ActivationSchedulerTimerListener.java:69)
at com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener.handleNotification2(ActivationSchedulerTimerListener.java:50)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2007-02-22 10:41:48,692 ERROR {Timer-3} [com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener] An error occurred during the call to notify that Order Scheduling should proceed
2007-02-22 10:41:52,612 INFO {Timer-4} [com.pacwest.schedulable.service_activation.BlocksActivationTimerListener] Got notification (#5): javax.management.timer.TimerNotification[source=pacwest.com:name=BlocksActivationTimer,type=Timer][type=jboss.monitor.heartbeat][message=50], handback: null
2007-02-22 10:41:52,613 INFO {Timer-4} [com.pacwest.schedulable.activationorder.ActivationSchedulerTimerListener] The Timer has sent a notification !!! Must wake up the Blocks Order Scheduler!!
2007-02-22 10:41:52,614 DEBUG {Timer-4} [com.pacwest.commons.jms.Sender] [sendObject] preparing jms {queue/BlocksActivationSchedulingQueue}...
2007-02-22 10:41:52,614 DEBUG {Timer-4} [com.pacwest.commons.service_locator.ServiceLocator] Inside ServiceLocator identifying cluster
2007-02-22 10:41:52,614 DEBUG {Timer-4} [com.pacwest.commons.service_locator.ServiceLocator] Setting ServiceLocator in Cluster Mode
2007-02-22 10:41:52,657 WARN {Timer-4} [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
javax.resource.spi.CommException: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:756)
at org.jboss.resource.adapter.jms.JmsManagedConnection.(JmsManagedConnection.java:172)
at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:95)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:519)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:208)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:378)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:133)
at com.pacwest.commons.jms.Sender.sendObject(Sender.java:62)
at com.pacwest.schedulable.service_activation.BlocksActivationTimerListener.notifyOrderScheduling(BlocksActivationTimerListener.java:70)
at com.pacwest.schedulable.service_activation.BlocksActivationTimerListener.handleNotification2(BlocksActivationTimerListener.java:51)
at org.jboss.system.ListenerServiceMBeanSupport.handleNotification(ListenerServiceMBeanSupport.java:391)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
at $Proxy57.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jms.JMSSecurityException: The login id has an assigned client id 'guest', that is already connected to the server!
at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:168)
at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:741)
at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorSupport.java:274)
at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:694)
at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:188)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020749#4020749
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020749
More information about the jboss-user
mailing list