2 Replies Latest reply on Jun 19, 2014 3:07 AM by Reza Azizi

    Question about jbpm-console

    세준 김 Newbie

      Hi.

       

      I've installed and tried to use jbpm 6.0.1 final and faced a problem that I cannot find a way to resolve.

       

      I did full installation by using the command "ant install.demo" and the script said everything went well, and then I started jbpm by the command "ant start.demo", but I cannot get the jbpm console page from "http://localhost:8080/jbpm-console".

       

      The page says : The requested resource (/jbpm-console) is not available.

       

      I checked the log and I cannot find any error line. The log is the following

       

       

      12:57:17,832 INFO  [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.7.Final

       

      12:57:17,838 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

      12:57:20,357 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      12:57:20,917 WARN  [jacorb.codeset] (MSC service thread 1-4) Warning - unknown codeset (MS949) - defaulting to ISO-8859-1

      12:57:21,113 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

      12:57:21,166 INFO  [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

      12:57:21,169 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

      12:57:21,225 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started

      12:57:21,268 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

      12:57:21,300 WARN  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

      12:57:21,594 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started

      12:57:21,715 정보    [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=E:\workSpace\jbpm-installer\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=E:\workSpace\jbpm-installer\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=E:\workSpace\jbpm-installer\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=E:\workSpace\jbpm-installer\jboss-as-7.1.1.Final\standalone\data\messagingpaging)

      12:57:21,717 정보    [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) Waiting to obtain live lock

      12:57:21,851 INFO  [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-2) Using NIO Journal

      12:57:22,151 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-2) Waiting to obtain live lock

      12:57:22,152 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-2) Live Server Obtained live lock

      12:57:23,964 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

      12:57:24,248 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/jbpmDS]

      12:57:24,260 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      12:57:24,549 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-2) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5445 for CORE protocol

      12:57:24,564 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-2) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5455 for CORE protocol

      12:57:24,571 정보    [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) Server is now live

      12:57:24,575 정보    [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [5180cbab-f50a-11e3-beb2-6817295ab9e1]) started

      12:57:24,601 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory E:\workSpace\jbpm-installer\jboss-as-7.1.1.Final\standalone\deployments

      12:57:24,762 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on /127.0.0.1:9999

      12:57:24,762 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:4447

      12:57:24,855 INFO  [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

      12:57:24,869 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA

      12:57:24,870 정보    [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) trying to deploy queue jms.queue.testQueue

      12:57:24,925 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-2) HornetQ resource adaptor started

      12:57:24,930 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra

      12:57:24,941 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

      12:57:25,083 INFO  [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011601: Bound messaging object to jndi name java:/queue/test

      12:57:25,089 INFO  [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

      12:57:25,095 정보    [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.topic.testTopic

      12:57:25,215 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test

      12:57:25,219 INFO  [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test

      12:57:25,225 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

      12:57:25,230 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory

      12:57:25,316 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "jbpm-console.war"

      12:57:25,315 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dashboard-builder.war"

       

       

      I did not make any modifications on the installation and just followed just written in the installation guide. Please let me know if there is any solution that lets me get the jbpm console and studies its usage further.

        • 1. Re: Question about jbpm-console
          Ashutosh Kumar Newbie

          Please check where the dashboard-builder.war and jbpm-console.war are deployed properly? You can view location "jbpm-installer\jboss-as-7.1.1.Final\standalone\deployments" and see if you have file like dashboard-builder.war.DEPLOYED and jbpm-console.war.DEPLOYED.

           

          The console will appear only when these 2 war are deployed properly.

          • 2. Re: Question about jbpm-console
            Reza Azizi Newbie

            In last lines of log, you can see

             

            12:57:25,316 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "jbpm-console.war"

            12:57:25,315 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dashboard-builder.war"

             

            these lines say that jboss still trying to deploy projects and you can not see the login page until the deployment finish.

            please wait, it needs some time to deploy.