I have a strange problem with an EAR containing EJBs from a shared lib placed in the /lib folder inside the ear.
The EAR deploys on Glassfish 2 with out errors.
But on Glassfish 3 deployment fails.
When I setup a simple EAR application with the following structure everything works well:
/
+- lib/
+- META-INF/
| +- application.xml
| +- sun-application.xml
+- my_ejb_module.jar (containing one stateless session ejb - BeanA)
+- my_web_module.war
Now I try to add a shared library with an additional EJB in the /lib folder
/
+- lib/
| +- sharedejbs.jar (containing one stateless session ejb - BeanB)
+- META-INF/
| +- application.xml
| +- sun-application.xml
+- my_ejb_module.jar (containing one stateless session ejb - BeanA)
+- my_web_module.war
Now when I try to deploy I got the following error message:
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Portable JNDI names for EJB EntityServiceBean : [java:global/imixs-workflow-testclient-ear-0.0.2-SNAPSHOT/imixs-workflow-testclient-ejb-0.0.2-SNAPSHOT/EntityServiceBean!org.imixs.workflow.jee.ejb.EntityService, java:global/imixs-workflow-testclient-ear-0.0.2-SNAPSHOT/imixs-workflow-testclient-ejb-0.0.2-SNAPSHOT/EntityServiceBean]
INFO: Portable JNDI names for EJB TestFacadeBean : [java:global/imixs-workflow-testclient-ear-0.0.2-SNAPSHOT/imixs-workflow-testclient-ejb-0.0.2-SNAPSHOT/TestFacadeBean, java:global/imixs-workflow-testclient-ear-0.0.2-SNAPSHOT/imixs-workflow-testclient-ejb-0.0.2-SNAPSHOT/TestFacadeBean!org.imixs.jee.testclient.TestFacade]
SCHWERWIEGEND: Exception while loading the app
org.glassfish.deployment.common.DeploymentException: Error in linking security policy for imixs-workflow-testclient-ear-0.0.2-SNAPSHOT -- Inconsistent Module State
at com.sun.enterprise.security.SecurityUtil.linkPolicyFile(SecurityUtil.java:329)
at com.sun.enterprise.security.SecurityDeployer.linkPolicies(SecurityDeployer.java:259)
at com.sun.enterprise.security.SecurityDeployer.access$100(SecurityDeployer.java:63)
.....
.........
I found a similar issue in the forum:
http://forums.java.net/jive/thread.jspa?messageID=371638
but this did not help me. I placed empty beans.xml files - with no effect.
Can anybody give me a hint what's going wrong here.
thanks for help
ralph
[Message sent by forum member 'rsoika' ]
http://forums.java.net/jive/thread.jspa?messageID=376028