2 Replies Latest reply on Aug 26, 2011 8:34 AM by jewellgm

    JBoss 6 NameAlreadyBoundException




      I am attempting to deploy 3 separate ear files in JBoss AS 6.  These ears contain a common jar that has a Main-Class attribute in the manifest.  This is causing a NameAlreadyBoundException as discussed here:




      As a temporary solution, I have removed this jar and placed it into the <server config>/lib directory.  However, this isn't a viable solution since we provide our ear files to somebody else.  Additionally, the offending jar is not ours, so modifying the jar would potentially have licensing issues. 

      Is there some configuration that I can provide inside the ear files that would prevent this error from occurring?




      Greg Jewell

        • 1. Re: JBoss 6 NameAlreadyBoundException

          You could disable (comment out) the Ejb3ClientDeployer from JBOSS_HOME/server/<servername>/deployers/ejb3.deployer/META-INF/ejb3-as-deployers-jboss-beans.xml if you are sure that the applications will not required "Java EE Application Client" support.

          1 of 1 people found this helpful
          • 2. Re: JBoss 6 NameAlreadyBoundException

            Thank you for the response.  This does appear to work for me, but I am reluctant to make a global configuration change like that.  Is there something similar that I can do with a metafile inside the ears themselves?