I am moving some working Eclipse-developed code to Guvnor and am seeing a huge number of messages logged for jackrabbit "session that has already been closed". This happens nearly continuously, with the session number ascending:
11:18:01,889 WARN [org.apache.jackrabbit.core.session.SessionState] (Finalizer) Attempt to close session-guest-45 after it has alre ady been closed. Please review your code for proper session management.: java.lang.Exception: Stack trace of the duplicate attempt t o close session-guest-45 Trying to debug the working code moved from my local system Guvnor that say to check the log. These session messages consume thousands of lines of warnings (at dozens per button press) that finding any "real" error messages seems impossible (even with automated searches). This issue has been posted on other forums but I don't see anything here. Is there a work around this issue - hopefully correcting the session persistence, as opposed to changing the logging level? I am guessing leaving Guvnor ungracefully causes an endless stream of these (forever). Thanks! -- View this message in context: http://drools.46999.n3.nabble.com/Guvnor-jackrabbit-session-issue-tp3868067p3868067.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
