java:/comp/env JNDI Namespace not found within ActionHandler Implementations ---------------------------------------------------------------------------- Key: JBPM-1903 URL: https://jira.jboss.org/jira/browse/JBPM-1903 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 GA Environment: JBoss 4.2.3 GA with MySQL5 Database jBPM Enterprise Deployment Reporter: Robert Schmelzer When you try to lookup the JNDI Namespace java:comp/env in an enterprise deployment wihtin an ActionHandler implementation it will throw an NameNotFoundException. So it is not possible to lookup ejb or other component local stuff within ActionHandler implementations. In special this also affects you, when you signal a token within an ActionHandler and any of the following Node is async using the JMSMessgeService because the JMS implementation will also make a lookup on the connection factory using the comp/env Namespace. The reason for this is the change in the classloader when executing ActionHandlers. The contex class loader is by default changed to the ProcessClassLoader using the UCL as parent. But JBoss uses the ContextClassLoader ot scope the comp/env Namespace. When using the original context class loader as the parent for the ProcessClassLoader it works again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira