Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run into a problem involving jbpm-console initialization
2. Look at the error log. 
3. Be confounded. 
  
Actual results:

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
org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:345)
org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:321)

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! 
	
Expected results:

You look at the server log and see an error that actually helps you. 

Additional info:

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.