JBoss EAP 5.x throws javax.naming.NameAlreadyBoundException: classPathEntries

1). Deploy the Attached two SAR files in the same JBoss profile.
2). Both the SAR files contains a Comman JAR file which has META-INF/MANIFEST.MF file with the attribute "Main-Class: test.TestClass"
3). As soon as we start the JBoss instance we will be able to see the following Exception:

09:46:54,656 ERROR [Ejb3ClientDeployer] Could not deploy vfszip:/home/someuser/jboss-eap-5.0.0/jboss-as/server/default_profile/deploy/SimpleSarTwo.sar/commonUtil.jar/
javax.naming.NameAlreadyBoundException: classPathEntries
at org.jnp.server.NamingServer.bind(NamingServer.java:209)
at org.jnp.server.NamingServer.bind(NamingServer.java:167)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:650)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:611)
at org.jboss.ejb3.deployers.Ejb3ClientDeployer.deploy(Ejb3ClientDeployer.java:150)
at org.jboss.ejb3.deployers.Ejb3ClientDeployer.deploy(Ejb3ClientDeployer.java:61)
at org.jboss.deployers.vfs.spi.deployer.AbstractSimpleVFSRealDeployer.deploy(AbstractSimpleVFSRealDeployer.java:56)

Option-1). Either we can remove the "Main-Class" attribute from your JAR file "CommonUtil.jar" and then deploy your SAR files.

Option-2). If we don't want to edit the Jar file "CommonUtil.jar" to remove the Main-Class attribute from it's MANIFEST.MF file then we need to make sure that only one copy of the JAR is available to the JBoss Deployer, as a Library. It means you can place the JAR file inside "$PROFILE/lib" directory rather than putting it inside two different SAR files. So if we put JAR file inside "$PROFILE/lib" then it will be available for both the SAR files, without duplication.