3 Replies Latest reply on Nov 28, 2011 12:34 PM by tsurdilovic

    jbpm console - process definitions load timeout issue

    anand.awasthi

      Hi

       

      I am trying to load the process definitions in Console. The bpmn files are in local file system. 9 out of 10 times, I am not able to see these process definitions in console and  I keep getting time out error as mentioned below:

       

       

      Request timeout

       

       

      How do I increase the timeout setting ? or what i m doing wrong ?

       

       

      Thanks

        • 1. Re: jbpm console - process definitions load timeout issue
          tsurdilovic

          When you get this error, can you try to hit the "Refresh" button again and let us know if the list gets populated? We are aware of the issue and will look into it for future releases of the bpm console.

           

          Hope this helps.

          • 2. Re: jbpm console - process definitions load timeout issue
            anand.awasthi

            Thanks for prompt response.

             

            Refreshing does not work either.  I forgot to mention that I am running it on IE7. Not that it matters in this case but I am seen other issues

            while using Console on IE7.

             

            Is this a problem only when I load process definitions from local file system (total 6 simple bpmn files) ? or it applies to resources hosted in Guvnor Repository as well ?

             

            Also , can you please tell me in what release this issue might be fixed. I am working for a customer and this information will be helpful given that process management is a big feature of Console and if we cant load the processes then it's a big concern.

             

            Thanks in advance

            • 3. Re: jbpm console - process definitions load timeout issue
              tsurdilovic

              We have increased the timeout for loading resources and it will be available in jBPM 5.2. I am not sure why hitting the Refresh button in your case does not work. Anything in the server logs or any JS errors in IE? Does the same happen on Firefox and/or Chrome for you?