Red Hat Bugzilla – Bug 838856
Insufficient logging in jbpm-console relating to ksession initialization
Last modified: 2016-09-20 01:16:17 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run into a problem involving jbpm-console initialization
2. Look at the error log.
3. Be confounded.
You look at the server log and see something like this:
org.jboss.resteasy.spi.UnhandledException: java.lang.NoClassDefFoundError: Could not initialize class org.jbpm.integration.console.StatefulKnowledgeSessionUtil$SessionHolder
You are confounded and frustrated and you possibly even curse the developers -- given that the error is not helping you at all with figuring out what the @#$% that stupid software is doing!
You look at the server log and see an error that actually helps you.
What's going on here is that the StatefulKnowledgeSessionUtil.initializeStatefulKnowledgeSession() method is throwing an exception, but that this exception is being swallowed up because it's called during initalization of the StatefulKnowledgeSessionUtil$SessionHolder inner class.
I'm seeing this error in messages on internal lists where people are having problems with the console -- without appropriate information, it's very hard for them (or me helping them) to figure out what the problem is.
The fix is to add logging at one or two points so that the appropriate (error/exception) information shows up in the server logs.
fyi - this was taken under consideration as part of https://issues.jboss.org/browse/JBPM-3724 - configurable session in jbpm-console but since that jira is much more than just logging don't know if it is going to be included in 5.3.1
Moving to future and setting MODIFIED, as this can he expected in future versions of jBPM.
Setting the release flag to - as this issue will not make it into 5.3.1