3 Replies Latest reply on Nov 25, 2008 4:52 AM by kukeltje

    Getting error in Jbpm webconsole

    manikandank

      Hi ,
      I have created the sample JBPM application in eclipse.After successful deployment ,I have tried the application through webconsole with follwing url
      http://localhost:8080/jbpm, afterwards I am getting the following error

      //jbpm - must refer to client 'guest'.

      Could you please let me where should I make the changes to resolve this issue.

      Thanks in advance

      Regards
      Manikandan.k

        • 1. Re: Getting error in Jbpm webconsole
          kukeltje

          first of al, what version are you using? /jbpm is old (3.1) , it currently is /jbpm-console.

          • 2. Re: Getting error in Jbpm webconsole [jbpm -must refer to cl
            manikandank

            Thanks for the help..! Actually this issue realted to port problem .
            My machine is already using the port 8080 .So I have changed the port number from 8080 to 8088 [server.xml].Now its works fine.

            How do react if you get the error :
            //jbpm - must refer to client 'guest

            Steps to resolve the issue
            Solution 1 : Dont try with jbpm in the URL ,instead try with jbpm-console[In the latest version console name has been changed ]

            Solution 2 :
            1 .Download the jbpm suite 3.2.2
            2. Go to Eclipse -Windows -Preference and select the Jboss Jbpm
            3. And then click the runtimelocation and mention the location of jboss suite 3.2.2
            4 And click the Server deployment and change the port number to 8088
            5 .Now create a new project .
            6 Go to jbpm-jpdl-3.2.2\server\server\jbpm\deploy\jbossweb-tomcat55.sar
            7 Open the server.xml and change the port from 8080 to 8088
            8 Now deploy the application and open the console
            http://localhost:8088/jbpm-console




            • 3. Re: Getting error in Jbpm webconsole
              kukeltje

              it's not only the latest minor verion (3.3), but it already changed in 3.2