[JBoss jBPM] - Disabling DBLoggingService
by jbaton
Hi all,
I'm facing a problem with the DBLogging feature.
It seems not to get a working jbpmcontext.
However, I can make it without this feature, I have not found in the documentation how to disable it. I tried to comment the "<service name="logging" element but it did not work :)
Does anybody know how to disable the dblogging feature ?
Or should I stack a jbpmcontext even if I am not to use it in my programs.
Also, any light about the stack under will be highly appreciated, why is a context needed ?
Thanks
JBaton
[java] org.jbpm.JbpmException: instantiation of the DbLoggingService requires a current JbpmContext
| [java] at org.jbpm.logging.db.DbLoggingService.<init>(DbLoggingService.java:39)
| [java] at org.jbpm.logging.db.DbLoggingServiceFactory.openService(DbLoggingServiceFactory.java:32)
| [java] at org.jbpm.svc.Services.getService(Services.java:136)
| [java] at org.jbpm.svc.Services.getLoggingService(Services.java:169)
| [java] at org.jbpm.svc.save.SaveLogsOperation.save(SaveLogsOperation.java:39)
| [java] at org.jbpm.svc.Services.save(Services.java:156)
| [java] at org.jbpm.JbpmContext.save(JbpmContext.java:388)
| [java] at com.xxxxx.cerbere.Workflow.run(Workflow.java:508)
| [java] at java.lang.Thread.run(Thread.java:534)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970697#3970697
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970697
19 years, 7 months
[Tomcat, HTTPD, Servlets & JSP] - Re: Http Session Timeout does not work properly
by alesj
"bstansberry(a)jboss.com" wrote :
| Can you perhaps add a valve or something to trap and record the session id associated with any request that throws an exception? And then correlate that to your sessions that aren't expiring. If they match, the above may be the culprit.
I did write a web filter:
| public void doFilter(ServletRequest servletRequest, ServletResponse servletResponse, FilterChain filterChain) throws IOException, ServletException {
| HttpServletRequest request = (HttpServletRequest) servletRequest;
| HttpServletResponse response = (HttpServletResponse) servletResponse;
| try {
| filterChain.doFilter(request, response);
| } catch (IOException e) {
| logThrowable(request, response, e);
| throw e;
| } catch (ServletException e) {
| logThrowable(request, response, e);
| throw e;
| } catch (RuntimeException e) {
| logThrowable(request, response, e);
| throw e;
| } catch (Error e) {
| logThrowable(request, response, e);
| throw e;
| }
| }
|
Some of the non-expired sessions stem from 'caught' exception, but not all of them. ;-(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970695#3970695
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970695
19 years, 7 months