[
https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1448:
-----------------------------------
i can reproduce locally, but not yet in my eclipse IDE. i have added some debugging that
logs the class loaders.
log.info("context classloader:
"+Thread.currentThread().getContextClassLoader());
log.info("parent of context classloader:
"+Thread.currentThread().getContextClassLoader().getParent());
log.info("class classloader: "+getClass().getClassLoader());
log.info("parent of class classloader:
"+getClass().getClassLoader().getParent());
when it succeeds, this is the logging
18:17:37,031 INFO [ResourceAction] context classloader:
org.jbpm.instantiation.ProcessClassLoader@1015a9e
18:17:37,031 INFO [ResourceAction] parent of context classloader:
sun.misc.Launcher$AppClassLoader@11b86e7
18:17:37,031 INFO [ResourceAction] class classloader:
org.jbpm.instantiation.ProcessClassLoader@1015a9e
18:17:37,031 INFO [ResourceAction] parent of class classloader:
sun.misc.Launcher$AppClassLoader@11b86e7
and when it fails, this is logged
2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] context classloader:
org.jbpm.instantiation.ProcessClassLoader@cbc0bc
2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] parent of context
classloader: sun.misc.Launcher$AppClassLoader@11b86e7
2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] class classloader:
sun.misc.Launcher$AppClassLoader@11b86e7
2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] parent of class
classloader: sun.misc.Launcher$ExtClassLoader@35ce36
So somehow if MVN picks up jdk 6 from the JAVA_HOME, then the classloaders change..
tomorrow i investigate further
jBPM does not initialise thread context classloader
---------------------------------------------------
Key: JBPM-1448
URL:
https://jira.jboss.org/jira/browse/JBPM-1448
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Kevin Conner
Assignee: Bernd Ruecker
Priority: Critical
Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA
jBPM does not initialise the thread context classloader when executing actions within the
process.
The outcome of this decision is that code executed within the context of this action will
not have access to classes/resources in the par unless the action classloader is an
explicit parameter.
One example of this is the RMI marshalling layer, which has an implication on JNDI
lookups.
--
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