[
http://jira.jboss.com/jira/browse/JBPM-1191?page=all ]
Alejandro Guizar resolved JBPM-1191.
------------------------------------
Resolution: Done
Got it. I forgot to remove the configuration files from the standalone webapp, which
resulted in the enterprise app using the wrong configuration. The jdk logging questions
remain open, tough.
Enterprise console error: No CurrentSessionContext configured
-------------------------------------------------------------
Key: JBPM-1191
URL:
http://jira.jboss.com/jira/browse/JBPM-1191
Project: JBoss jBPM
Issue Type: Task
Components: Core Engine
Environment: JBoss 4.2.2.GA
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM jPDL 3.2.3
Attachments: logging.properties
After logging in to the web console deployed inside the enterprise archive, the following
error is reported:
Error loading process list: An exception of type
"org.hibernate.HibernateException" was thrown. The message is: No
CurrentSessionContext configured!
This happens even tough the hibernate.current_session_context_class property is
explicitly set to "jta". According to the manual, even if that property was not
set it, Hibernate would use the JTASessionContext because a
transaction.manager_lookup_class is configured. So the throwing of this exception is
really weird.
What is worse, I cannot figure out why I can't get a stack trace. The web console
uses JDK logging (in sync with the JSF implementation). I set the
java.util.logging.config.file system property to the attached config file, and actually
get some log records written to the target log file. There are two issues that strike me:
1. I see INFO records in the console. Nonetheless, only FINE-level records appear in the
log file. Why don't INFO records appear in the log file?
2. org.jbpm.jsf.core.impl.JbpmJsfContextImpl.setError(String, Throwable) has code that
logs the exception at FINE level. However, the corresponding record never appears in the
log file. Who or what slurped it?
Any help with the above would be appreciated.
That said, I hate JDK logging. log4j has an intuitive configuration. I never got weird
results like the above from it. Why log4j wasn't just standardized as it was, or at
least the JDK logging API made a clear distinction between interface and implementation?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira