9 Replies Latest reply on May 16, 2008 12:55 PM by Marcelo Alcantara

    MDB login for topic subscriber

    alanc_yang Newbie

      I ran into a situation when the MDB is deployed, it encountered the following exception:

      20:56:33,698 INFO [EjbModule] Deploying AlarmMDB
      20:56:33,768 WARN [OILServerILService] Client request resulted in a server exception:
      javax.jms.JMSSecurityException: The login id has an assigned client id. That client id is
      already connected to the server!
      at org.jboss.mq.sm.AbstractStateManager.checkUser(AbstractStateManager.java:213)
      at org.jboss.mq.server.JMSDestinationManager.checkUser(JMSDestinationManager.java:
      748)
      at org.jboss.mq.server.JMSServerInterceptorSupport.checkUser(JMSServerInterceptorS
      upport.java:274)
      at org.jboss.mq.server.TracingInterceptor.checkUser(TracingInterceptor.java:741)
      at org.jboss.mq.server.JMSServerInvoker.checkUser(JMSServerInvoker.java:274)
      at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:321)
      at java.lang.Thread.run(Thread.java:534)

      Is it complaining the parameter used in createTopicConnection("user", "password") from within MDB is conflicting with other user/password used somewhere else? I do have other MBean subscribes to the same topic but with different user/password.

      Wonder how this is happened.
      Thanks for your help.

      Alan

        • 1. Re: MDB login for topic subscriber
          Adrian Brock Master

          But the same clientid? Show your jbossmq-state.xml - feel free to obfuscate the
          passwords.

          Regards,
          Adrian

          • 2. Re: MDB login for topic subscriber
            alanc_yang Newbie

            Here is the jbossmq-state.xml file:

            <?xml version="1.0" encoding="UTF-8"?>
            <StateManager>
             <Users>
             <User>
             <Name>john</Name>
             <Password>needle</Password>
             <Id>DurableSubscriberExample</Id>
             </User>
             <User>
             <Name>guest</Name>
             <Password>guest</Password>
             </User>
             <User>
             <Name>nobody</Name>
             <Password>nobody</Password>
             </User>
             <User>
             <Name>dynsub</Name>
             <Password>dynsub</Password>
             </User>
             <User>
             <Name>MACCAlarm</Name>
             <Password>*****</Password>
             <Id>MACCAlarm</Id>
             </User>
             <User>
             <Name>MACCAlarmMDB</Name>
             <Password>*****</Password>
             <Id>MACCAlarmMDB</Id>
             </User>
             </Users>
             <Roles>
             <Role name="guest">
             <UserName>guest</UserName>
             <UserName>john</UserName>
             <UserName>MACCAlarm</UserName>
             <UserName>MACCAlarmMDB</UserName>
             </Role>
             <Role name="subscriber">
             <UserName>john</UserName>
             <UserName>MACCAlarm</UserName>
             <UserName>MACCAlarmMDB</UserName>
             </Role>
             <Role name="publisher">
             <UserName>john</UserName>
             <UserName>dynsub</UserName>
             <UserName>MACCAlarm</UserName>
             <UserName>MACCAlarmMDB</UserName>
             </Role>
             <Role name="durpublisher">
             <UserName>john</UserName>
             <UserName>dynsub</UserName>
             <UserName>MACCAlarm</UserName>
             <UserName>MACCAlarmMDB</UserName>
             </Role>
             <Role name="noacc">
             <UserName>nobody</UserName>
             </Role>
             </Roles>
             <DurableSubscriptions>
             <DurableSubscription>
             <ClientID>DurableSubscriberExample</ClientID>
             <Name>chap6-ex1dtps</Name>
             <TopicName>testTopic</TopicName>
             </DurableSubscription>
             <DurableSubscription>
             <ClientID>MACCAlarm</ClientID>
             <Name>macc-alarm-manager</Name>
             <TopicName>testTopic</TopicName>
             </DurableSubscription>
             <DurableSubscription>
             <ClientID>MACCAlarmMDB</ClientID>
             <Name>macc-alarm-manager</Name>
             <TopicName>testTopic</TopicName>
             </DurableSubscription>
             </DurableSubscriptions>
            </StateManager>
            


            • 3. Re: MDB login for topic subscriber
              Adrian Brock Master

              I don't see any duplicates so it is not a configuration issue.

              According to the message you have two people logged in with same clientID,
              or at least trying to.

              Regards,
              Adrian

              • 4. Re: MDB login for topic subscriber
                alanc_yang Newbie

                Two clientID:
                - MACCAlarmMDB
                - MACCAlarm
                have the same name
                - macc-alarm-manager
                would that cause problem? The 'name' attribute seems to have been generated automatically. Is that the case and I wonder how?

                • 5. Re: MDB login for topic subscriber
                  P T Newbie

                  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)

                  • 6. Re: MDB login for topic subscriber
                    Arvind Aggarwal Newbie

                    Hi,

                    Is there any way to fix this issue. I am uing 4.2.2 GA version and am facing the same problem. Please help

                    • 7. Re: MDB login for topic subscriber
                      Marcelo Alcantara Newbie

                      I have the some problem.

                      Adrian, can you give us a hand? :-)

                      Thanks in advance.

                      Marcelo

                      • 8. Re: MDB login for topic subscriber
                        Adrian Brock Master

                        You're tryin to create a pool of connections all with the same client id.
                        This isn't allowed. Only one connection can use a client id at once.

                        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)
                        


                        You can use the jms resource adapter with a client id,
                        but only if you set the max-pool-size to 1

                        • 9. Re: MDB login for topic subscriber
                          Marcelo Alcantara Newbie

                          hi Adrian,

                          Thanks for your respose.

                          Our problem is that we are running a cluster - this problem just happens with the second node of the cluster - the mdb/pool from the first loaded server connects fine, but the second loaded server gives that client id message.

                          We could solve the issue with a hand from Brian Stanberry, giving a login/client id on the jboss command line. But although it fixes the problem, it seems a horrible solution.

                          Analysing your answer, as the mdb is not a ha-singleton, it is loaded on both servers. Then, either if we put the pool size to one, we will have one connection on each server which will bring the same issue.

                          I understood that if we remove the client-id it will work fine. The client-id configuration is not necessary?

                          Thank in advance.

                          Regards,

                          Marcelo