Hi all,
 
I'm trying to deploy a Message Driven Bean which subscribes durable to a Topic. (I'm using JBoss 3.0.4 with a Solid database).
 
In the generic dd I set the following:
 
        <message-driven>
            <ejb-name>EJBMessageDrivenComponent</ejb-name>
            <ejb-class>crm.application.ejb.EJBMessageDrivenComponent</ejb-class>
            <transaction-type>Container</transaction-type>
            <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
            <message-driven-destination>
                <destination-type>javax.jms.Topic</destination-type>
                <subscription-durability>Durable</subscription-durability>
            </message-driven-destination>
        </message-driven>
 
In the JBoss dd I set:
 
      <message-driven>
          <ejb-name>EJBMessageDrivenComponent</ejb-name>
          <destination-jndi-name>topic/MyTopic</destination-jndi-name>
          <mdb-client-id>test</mdb-client-id>
          <mdb-subscription-id>test</mdb-subscription-id>
          <configuration-name>Standard Message Driven Bean</configuration-name>
      </message-driven>
So I want to subscribe durable and specify a clientID/subscription name but I don't want to set a username/password. If I don't specify mdb-user/mdb-passwd I get a javax.jms.JMSSecurityException during deployment saying
 
"Connection not authorized to do durable subscription on topic: MyTopic".
 
If I do set a username/passwd :
 
          <mdb-user>john</mdb-user>
          <mdb-passwd>needle</mdb-passwd>
It says:
    javax.jms.IllegalStateException: The connection has already a clientID
What does the clientID/SubscriptionName have to do with the authorized connection?
 
Regards,
 
Raymond Brandon
 


--

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.


Reply via email to