[
https://jira.jboss.org/jira/browse/JBPM-2501?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-2501:
-----------------------------------
also revisit DispatcherThread line 93:
// the exception doesn't have to be logged if jboss is still booting
// this should be replaced with proper dependency configuration
//
https://jira.jboss.org/jira/browse/JBPM-2501
if (e.getMessage().indexOf("couldn't lookup 'UserTransaction'
from jndi: UserTransaction not bound: UserTransaction not bound")==-1) {
log.error("exception in job executor thread. waiting " +
currentIdleInterval + " milliseconds", e);
}
revisit jboss jbpm service archive architecture
-----------------------------------------------
Key: JBPM-2501
URL:
https://jira.jboss.org/jira/browse/JBPM-2501
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.2
revisit the jbpm service archive and the way that the process engine is published into
JNDI
the process/businessarchive deployer should be removed
--
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