11 Replies Latest reply on Jun 20, 2006 11:44 AM by Brian Viveiros

    Turning off Jbpm Logging

    Santosh Bhojraj Newbie

      Hi,
      I am using JBPM 3.0.1 and I want to turn OFF the logging into JBPM_LOG table as it is creating too many rows and affecting the response time.

      1. Is there a way this can be done just for my process i.e. can it be congfigured in the processdefinition.xml file ?

      2. If the answer to the above is No, how can it be done programatically while deploying the process definition.

      I would appreciate any information.

      Cheers !!
      Santosh

        • 1. Re: Turning off Jbpm Logging
          boerse scholz Newbie

          Curious, i'm using 3.0.2 w JBoss 4.0.x and i'm desesperated to switch the logging ON as i want to know (in the near future) how long did it take to complete a process, mean times, etc. Can you tell me how do you know your logging of the PROCESS EXECUTION, not the application one? Thanks...

          • 2. Re: Turning off Jbpm Logging
            Santosh Bhojraj Newbie

            Dear Boerse,
            I dit not say that I was logging the process execution. All I see is a whole bunch of rows in the 'JBPM_LOG' table (30000+) and I want to be able to control them. It seems that it is logging the old and new values for the context varaibles, though I am not sure. What I need to know is what these entries are and if it possible to be able to control what goes into this table (using configuration mechanisms, preferrably).
            As for your question, the JBPM_PROCESSINSTANCE table has START_ and END_ columns the difference of which will you the time for a Process instance to complete.

            Santosh

            • 3. Re: Turning off Jbpm Logging
              boerse scholz Newbie

              Hi Santosh!

              Thank you for your reply, about how to configure the statistics the only thing i can recommend you (as the newbie i am) is to change in \jbpm\src\config.files-> the file hibernate.cfg.xml and set false.

              By the way, which version are using you? i do 3.0.2 w JBoss 4.0.3SP1 and when i start the JBoss after deploying (build.deploy.xml create.jbpm.configuration) i receive a lot of messages in the form:

              12:24:38,150 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
              http-invoker.sar/invoker.war/
              12:24:39,202 INFO [WebappLoader] Dual registration of jndi stream handler: fact
              ory already defined
              12:24:41,345 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbosswe
              b-tomcat55.sar/ROOT.war/
              12:24:42,296 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
              deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
              12:24:42,747 ERROR [MainDeployer] Could not create deployment: file:/C:/Server/j
              bpm-3.0.2/jbpm-server/server/jbpm/deploy/attrpm-service.xml
              org.jboss.deployment.DeploymentException: Trying to install an already registere
              d mbean: jboss:service=AttributePersistenceService
               at org.jboss.system.ServiceCreator.install(ServiceCreator.java:70)
               at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
              tor.java:431)
               at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
              :153)
               at org.jboss.system.ServiceController.install(ServiceController.java:215
              )
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
              java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy4.install(Unknown Source)
               at org.jboss.deployment.SARDeployer.create(SARDeployer.java:232)
               at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
              java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
              or.java:118)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
              BeanOperationInterceptor.java:127)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy9.deploy(Unknown Source)
               at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
              tScanner.java:319)
               at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
              canner.java:507)
               at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
              doScan(AbstractDeploymentScanner.java:192)
               at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
              bstractDeploymentScanner.java:265)
               at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
              upport.java:274)
               at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
              eanSupport.java:230)
               at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
              ler.java:943)
               at $Proxy0.start(Unknown Source)
               at org.jboss.system.ServiceController.start(ServiceController.java:428)
               at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy4.start(Unknown Source)
               at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
               at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
              java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
              or.java:118)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
              BeanOperationInterceptor.java:127)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy5.deploy(Unknown Source)
               at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
               at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
               at org.jboss.Main.boot(Main.java:187)
               at org.jboss.Main$1.run(Main.java:438)
               at java.lang.Thread.run(Thread.java:534)

              and many more... thanks...

              • 4. Re: Turning off Jbpm Logging
                boerse scholz Newbie

                Hi sbhojraj, how do you make to access this JBPM_LOGS table? i use Squirrel cliente connected with the hibernate and the only tables i see are the system tables and none of them has the name JBPM_(something).

                Thank you very much, it's hard to be a newbie...

                • 5. Re: Turning off Jbpm Logging
                  Santosh Bhojraj Newbie

                  I am running JBPM on an Oracle DB. I can look at all the tables using TOAD or SQL PLUS.

                  • 6. Re: Turning off Jbpm Logging
                    boerse scholz Newbie

                    Hi, thank you for the answer! :) i'm still trying to access the tables in the default DB (Hypersonic).

                    • 7. Re: Turning off Jbpm Logging
                      Koen Aers Master

                      To access the default HSQLDB you should open the jmx console (http://localhost:8080/jmx-console). Then locate the Hypersonic MBean and click on it. Navigate downwards to the operations and invoke the 'startDatabaseManager()' operation. The HSQLDB database manager opens and you can enter SQL to look at the contents of the table.

                      Regards,
                      Koen

                      • 8. Re: Turning off Jbpm Logging
                        Santosh Bhojraj Newbie

                        Hello Guys:
                        Can we please keep the discussion to the primary issue at hand i.e understanding what JBPM_LOG table is and how to control the data being inserted into it. Please start a new thread about HSQL DB issues.
                        It would be truly appreciated.

                        Santosh

                        • 9. Re: Turning off Jbpm Logging
                          Olivier Kloss Newbie

                          This is what the documentation has to say about turning off logging ( in http://docs.jboss.com/jbpm/v3/userguide/logging.html) :

                          "For deployments where logs are not important, it suffices to get rid of the optional LoggingDefinition in the ProcessDefinition. That will prevent LoggingInstances from being captured and hence no logs will be maintained. We will add more fine grained configuration control over logging later on. See jira issue 'log level configuration'. "


                          Don't know if it works though as we most definitely need logging in our app.

                          Good luck!

                          • 10. Re: Turning off Jbpm Logging
                            Olivier Kloss Newbie

                            (by "good luck!" I mean "hope it helps!" ;)

                            • 11. Re: Turning off Jbpm Logging
                              Brian Viveiros Newbie

                              Does anyone understand what the doc means by:

                              get rid of the optional LoggingDefinition in the ProcessDefinition.


                              I'm trying to figure out how to disable logging.