Urgent!!!: Usage of connectionfactory with pre-configured... additional info

Question

          In addition to my previous mail the exception seems to occur when:
          the message driven bean in the weblogic deployment desriptor uses:
          - Only <connection-factory-jndi-name> which points to a topic connection factory
          that has the client id field set. (So without the jms-client-id)
          - Both <connection-factory-jndi-name> which points to a topic connection factory
          that has the client id field set and <jms-client-id> which contains the same client
          id as the connection factory
          - Both <connection-factory-jndi-name> which points to a topic connection factory
          that DOES NOT have the client id field set and <jms-client-id> which DOES contain
          a client id.
          I don't know if this has something to do with it, but previously a different MDB
          had subscribed durably to the same topic by setting the client id in the deployment
          descriptor. The durable subscription was manually removed via the console and
          the server has been restarted afterwards, but the exception still occurs.
          --- example of non working dd ---
          --- connection factory has NOT been conigured with a client id ---
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>EJBMDBComponent</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>topic/MyTopic</destination-jndi-name>
          <connection-factory-jndi-name>jms.MyTopicConnectionFactory</connection-factory-jndi-name>
          <jms-client-id>blabla</jms-client-id>
          </message-driven-descriptor>
          <jndi-name>EJBMDBComponent</jndi-name>
          </weblogic-enterprise-bean>
          

Answer 1

Urgent issues should go through customer support, this is an
          informal forum.
          The thing to understand is that only one
          active connection may use a given client-id at a time. Check
          JMS statistics to make sure there truly is no other
          connection using the client-id - you can get a list of
          active connections via the console.
          See my answer to your other recent post for more info.
          Tom, BEA
          Raymond Brandon wrote:
          > In addition to my previous mail the exception seems to occur when:
          >
          > the message driven bean in the weblogic deployment desriptor uses:
          > - Only <connection-factory-jndi-name> which points to a topic connection factory
          > that has the client id field set. (So without the jms-client-id)
          > - Both <connection-factory-jndi-name> which points to a topic connection factory
          > that has the client id field set and <jms-client-id> which contains the same client
          > id as the connection factory
          > - Both <connection-factory-jndi-name> which points to a topic connection factory
          > that DOES NOT have the client id field set and <jms-client-id> which DOES contain
          > a client id.
          >
          > I don't know if this has something to do with it, but previously a different MDB
          > had subscribed durably to the same topic by setting the client id in the deployment
          > descriptor. The durable subscription was manually removed via the console and
          > the server has been restarted afterwards, but the exception still occurs.
          >
          > --- example of non working dd ---
          > --- connection factory has NOT been conigured with a client id ---
          >
          > <weblogic-ejb-jar>
          > <weblogic-enterprise-bean>
          > <ejb-name>EJBMDBComponent</ejb-name>
          > <message-driven-descriptor>
          > <destination-jndi-name>topic/MyTopic</destination-jndi-name>
          > <connection-factory-jndi-name>jms.MyTopicConnectionFactory</connection-factory-jndi-name>
          > <jms-client-id>blabla</jms-client-id>
          > </message-driven-descriptor>
          > <jndi-name>EJBMDBComponent</jndi-name>
          > </weblogic-enterprise-bean>
          >