6 Replies Latest reply on Oct 30, 2013 4:37 PM by kvopmat

    Bpel-Console error in Linux

    kvopmat

      Hello everyone,

       

      I am new to Switchyard and this is my first post. My environment is:

      Red Hat Linux

      Jboss AS 7.1.1

      Switchyard 0.8

       

      I was able to install and load the Bpel-Console page on my windows machine buy when I installed switchyard on Linux, I am getting the error below when I try to load http://localhost:8080/bpel-console

       

      We need Switchyard running on Redhat Linux.  Has anyone ran into this problem before?

       

      Thanks

      Khanh

       

      ----------------------------------------

       

      HTTP 500:

      HTTP Status 500 -

       

       

      type Exception report

       

       

      message

       

       

      description The server encountered an internal error () that prevented it from fulfilling this request.

       

       

      exception

       

       

      org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalStateException: Failed to load org.jboss.bpm.console.server.plugin.GraphViewerPlugin: org.jboss.soa.bpel.console.SVGPlugin

        org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:340)

        org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214)

        org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190)

        org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:540)

        org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)

        org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)

        org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)

        org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)

        org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

        org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)

       

       

      root cause

       

       

      java.lang.IllegalStateException: Failed to load org.jboss.bpm.console.server.plugin.GraphViewerPlugin: org.jboss.soa.bpel.console.SVGPlugin

        org.jboss.bpm.console.server.utils.ServiceLoader.loadFromServices(ServiceLoader.java:94)

        org.jboss.bpm.console.server.utils.ServiceLoader.loadService(ServiceLoader.java:56)

        org.jboss.bpm.console.server.plugin.PluginMgr.load(PluginMgr.java:54)

        org.jboss.bpm.console.server.InfoFacade.getServerStatus(InfoFacade.java:83)

        org.jboss.bpm.console.server.InfoFacade.getServerInfo(InfoFacade.java:72)

        sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        java.lang.reflect.Method.invoke(Method.java:597)

        org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)

        org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)

        org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)

        org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)

        org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)

        org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)

        org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)

        org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)

        org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)

        org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

        org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)

       

       

      root cause

       

       

      java.lang.RuntimeException: Failed to initialize BPEL engine

        org.jboss.soa.bpel.console.SVGPlugin.<init>(SVGPlugin.java:82)

        sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

        sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

        sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

        java.lang.reflect.Constructor.newInstance(Constructor.java:513)

        java.lang.Class.newInstance0(Class.java:357)

        java.lang.Class.newInstance(Class.java:310)

        org.jboss.bpm.console.server.utils.ServiceLoader.loadFromServices(ServiceLoader.java:89)

        org.jboss.bpm.console.server.utils.ServiceLoader.loadService(ServiceLoader.java:56)

        org.jboss.bpm.console.server.plugin.PluginMgr.load(PluginMgr.java:54)

        org.jboss.bpm.console.server.InfoFacade.getServerStatus(InfoFacade.java:83)

        org.jboss.bpm.console.server.InfoFacade.getServerInfo(InfoFacade.java:72)

        sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        java.lang.reflect.Method.invoke(Method.java:597)

        org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)

        org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)

        org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)

        org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)

        org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)

        org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)

        org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)

        org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)

        org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)

        org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

        org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)

       

       

      note The full stack trace of the root cause is available in the JBoss Web/7.0.13.Final logs.

      JBoss Web/7.0.13.Final

        • 1. Re: Bpel-Console error in Linux
          objectiser

          Hi Khanh

           

          This problem may be the result of a known problem - you can only use the BPEL console if a BPEL process has been deployed. Did you deploy one of the switchyard bpel quickstarts before trying to access the console?

           

          If this is not the problem, then can I suggest updating to the more recent 1.0.0.Final version of switchyard to see if the problem still exists?

           

          Regards

          Gary

          • 2. Re: Bpel-Console error in Linux
            kvopmat

            Thanks Grary!

             

            Loading a BPEL process works. However, I don't see anything in data (nothing in history or instances).  I load and ran the help desk demo.

             

            I'm stuck on version 0.8 because we are working on Jboss 7.

             

            Thanks

            Khanh

            • 3. Re: Bpel-Console error in Linux
              objectiser

              Hi Khanh

               

              The help desk demo doesn't use BPEL. You will need to deploy and run one of the quickstarts under bpel_service.

               

              Regards

              Gary

              • 4. Re: Bpel-Console error in Linux
                kvopmat

                Thanks for the help!

                 

                So I deployed the bpel-service quick start.  I am able to run the exec:java command and see it in the History Instances  from the BPEL Console. However, I do not see the Proces Instance Activity diagram.  Is that a Version 1.0 feature?

                 

                Is there a console for the BPMN 2 workflows?

                 

                When I click the an Instance from the Bpel Console, I get the message below from the trace:

                 

                ------------------------------------

                 

                 

                2013-10-28 08:58:59,641 [FATAL] Uncaught Exception:
                com.google.gwt.core.client.JavaScriptException:
                (TypeError): Cannot read property '203' of undefined
                    at Unknown._E(JsArrayString.java:42)
                    at Unknown._B(StackTraceCreator.java:366)
                    at Unknown.Xlb(Exceptions.java:29)
                    at Unknown.a$(Cast.java:32)
                    at Unknown.VY(Cast.java:76)
                    at Unknown.FEc(SelectionGrid.java:646)
                    at Unknown.PEc(SelectionGrid.java:798)
                    at Unknown.MEc(SelectionGrid.java:400)
                    at Unknown.LEc(SelectionGrid.java:363)
                    at Unknown.JFc(DataTable.java:91)
                    at Unknown.xrb(DOM.java:1307)
                    at Unknown.anonymous(DOMImplStandard.java:180)
                    at Unknown.gE(Impl.java:189)
                    at Unknown.anonymous(Impl.java:56)

                 

                2013-10-28 08:58:59,838 [FATAL] Uncaught Exception:
                com.google.gwt.core.client.JavaScriptException:
                (TypeError): Cannot read property '203' of undefined

                    at Unknown._E(JsArrayString.java:42)
                    at Unknown._B(StackTraceCreator.java:366)
                    at Unknown.Xlb(Exceptions.java:29)
                    at Unknown.a$(Cast.java:32)
                    at Unknown.VY(Cast.java:76)
                    at Unknown.FEc(SelectionGrid.java:646)
                    at Unknown.DEc(SelectionGrid.java:604)
                    at Unknown.SEc(SelectionGrid.java:255)
                    at Unknown.uFc(FixedWidthGrid.java:308)
                    at Unknown.djc(SelectionGrid.java:127)
                    at Unknown.FSc(ProcessHistoryInstanceListView.java:170)
                    at Unknown.YSc(ProcessHistoryInstanceListView.java:109)
                    at Unknown.qN(com.google.gwt.dev.jjs.impl.GenerateJavaAST:0)
                    at Unknown.fS(HandlerManager.java:65)
                    at Unknown.LR(HandlerManager.java:175)
                    at Unknown.zvb(Widget.java:52)
                    at Unknown.zM(DomEvent.java:116)
                    at Unknown.JFc(DataTable.java:89)
                    at Unknown.xrb(DOM.java:1307)
                    at Unknown.anonymous(DOMImplStandard.java:180)
                    at Unknown.gE(Impl.java:146)
                    at Unknown.anonymous(Impl.java:56)

                 

                ---------

                 

                 

                Thanks for all the help.

                Khanh

                • 5. Re: Bpel-Console error in Linux
                  objectiser

                  Hi Khanh

                   

                  The activity diagrams are currently only for active process instances, to show where they currently are in their flow. If you use the simple_correlation example, and only send the 'hello' message, the BPEL process instance will remain active while awaiting the 'goodbye' message - so you should be able to look at the active process instance and it's diagram.

                   

                  I only work on the BPEL side, so someone else will need to respond regarding BPMN2.

                   

                  In terms of the exception, can you open a jira and outline what steps are required to reproduce this exception?

                   

                  Regards

                  Gary

                  • 6. Re: Bpel-Console error in Linux
                    kvopmat

                    Thanks Gary, I am able to see the current state of the flow with the simple_correlation.