2 Replies Latest reply on May 20, 2004 11:18 AM by Simone

    MDB not unbound after undeploy

    Simone Newbie

      Hi,

      In Jboss 3.2.3 I have a sar file that contains an ear. Inside the ear I have two jars. One with a session bean one with an MDB that depends on the session bean. The sar deploys fine but when I do the undeploy my MDB stays bound so the next deployment fails with an javax.management.InstanceAlreadyExistsException:jboss.j2ee:jndiName=local/JobsCollector,service=EJB already registered.
      My jboss.xml for MDB follows

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">
      
      <jboss>
      
       <enterprise-beans>
      
       <!--
       To add beans that you have deployment descriptor info for, add
       a file to your XDoclet merge directory called jboss-beans.xml that contains
       the <session></session>, <entity></entity> and <message-driven></message-driven>
       markup for those beans.
       -->
      
       <message-driven>
       <ejb-name>JobsCollector</ejb-name>
       <destination-jndi-name>queue/webGuru/pricer/ResponseQueue</destination-jndi-name>
       <configuration-name>Standard Message Driven Bean</configuration-name>
       <depends>jboss.mq.destination:name=webGuru/pricer/ResponseQueue,service=Queue </depends>
       <depends>jboss.j2ee:jndiName=EJB/Session/JobFacade,service=EJB</depends>
       </message-driven>
      
       </enterprise-beans>
      
       <resource-managers>
       </resource-managers>
      
       <container-configurations>
       <container-configuration extends="Standard Message Driven Bean">
       <container-name>Standard Message Driven Bean with Security</container-name>
       <security-domain>java:/jaas/test</security-domain>
       </container-configuration>
       </container-configurations>
      
      </jboss>
      

      Anyone any idea?
      Many thanks!!!
      Simone