Re: [JBoss-user] Problems deploying an EAR on JBoss 3.2

[Christian Neuroth]

Title: Message

Hi!   Was my mistake.... I figured it out...   The jboss.xml of one of the ejbs contained a jndi name, that was already used by another one....   Thanks    christian   ----- Original Message ----- From: James Higginbotham To: [EMAIL PROTECTED] Sent: Monday, February 03, 2003 5:22 PM Subject: RE: [JBoss-user] Problems deploying an EAR on JBoss 3.2 Wow! I've been seeing this on 3.0.6 as well but thought it was our complex build system.. I end up having to delete the tmp, db, and log directories (just be be sane and clear the logs for my sake) and things deploy fine.. This didn't happen on 3.0.4, so something has changed in the deployer - its getting confused and picking up both old deployments and new or something.. Only way I can explain this oddity.. Anyone from Jboss-dev have any ideas about this? Its really slowing down my development.   Thanks, James -----Original Message----- From: Christian Neuroth [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:17 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Problems deploying an EAR on JBoss 3.2 Hi!   Deploying the single ejb-jar works... But when I pack them into an ear archive I receive the following message:   javax.management.InstanceAlreadyExistsException: jboss.management.local:EJBModule=Foo-ejb.jar,J2EEApplication= ,J2EEServer=example.ear,j2eeT ype=StatelessSessionBean,name=BarHomeRemote already registered.   I deleted everything from the deploy folder and tried again - without success....     The application.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'> <application> <display-name>ExampleEAR</display-name> <description>blub</description> <module> <ejb>Foo-ejb.jar</ejb> </module> <module> <ejb>Bar-ejb.jar</ejb> </module> </application>   Thanks!     Christian