3 Replies Latest reply on Sep 1, 2012 5:35 PM by nkb

    jbpm hornetq task server won´t start

    nkb

      hello,

       

      i changed my database like explained in the tutorial:

       

      http://docs.jboss.org/jbpm/v5.3/userguide/ch.installer.html#d0e597

       

      after changing to the mysql db, the human task service starts on port 9123 (hence, it´s mina)

       

      but the application expects the hornetq task server to be running

       

      by opening the console, i get the following error:

       

      java.lang.RuntimeException: Could not initialize stateful knowledge session: Could not connect task client HornetQ(127.0.0.1:5445)

       

      how it´s possible to start the hornetq task server? (on port 5445)

        • 1. Re: jbpm hornetq task server won´t start

          If your human task service is started as using jbpm-human-task-war.war , according to the documenataion  , you can change the config of the human task service in the web.xml. I think you can try to set the following <init-param> in web.xml :

           

            <init-param>
            <param-name>active.config</param-name>
            <param-value>hornetq</param-value>
            </init-param>
          • 2. Re: jbpm hornetq task server won´t start
            nkb

            hello,

             

            i´ve read the documentation. i changed the web.xml files in the following locations:

             

            \task-service\target\war

             

            E:\jbpm-installer 5.3\task-service\resources\war

             

            and as part of the war file:

             

            \jboss-as-7.0.2.Final\standalone\deployments

             

            i entered 'hornetq' in all of them. unfortunately, the problem stays the same.

             

             

            • 3. Re: jbpm hornetq task server won´t start
              nkb

              after all, i found the solution: it was also necessary to change the hibernate dialect property in the standalone.xml file located in \task-service\resources\war

               

              thread can be closed