7 Replies Latest reply: Sep 20, 2012 6:49 AM by wqe wqe RSS

http://localhost:8080/jbpm-console problem

Feki Ahmed Newbie

hi,

I have downloaded jbpm-install and installed jbpm by “ant  install.demo”.

 

After I execute “ant start.demo”, however I can’t access

http://localhost:8080/jbpm-console..

 

i checked if the server is running on http://localhost:8080/ and found the

jboss AS welcome page working.

 

i also found a similar problem on https://community.jboss.org/thread/160213

but still didn t find the problem neither in the server log.

 

windows 7, 32bits.

mozilla firefox.(i tryed chrome but didn t work neither..)

 

cheers!

  • 1. Re: http://localhost:8080/jbpm-console problem
    Feki Ahmed Newbie

    i found this in the server log :

     

    09:20:32,905 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:20:32,952 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "jbpm-gwt-console.war" was rolled back with failure message Operation cancelled

    09:20:34,311 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "jbpm-gwt-console-server.war" was rolled back with no failure message

    09:20:34,499 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "drools-guvnor.war" was rolled back with no failure message

    09:20:35,046 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "designer.war" was rolled back with no failure message

    09:20:34,311 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:20:35,046 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:20:35,171 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

     

     

    here is my server log :

     

    02:18:18,450 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)

    02:18:18,794 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.

    02:18:19,278 INFO  [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem

    02:18:19,497 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

    02:18:19,528 INFO  [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem

    02:18:19,825 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem

    02:18:19,934 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2

    02:18:20,231 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3

    02:18:20,622 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3

    02:18:24,028 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_02\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jdk1.6.0_02\bin;C:\apache-ant-1.8.3\bin;C:\apache-maven-2.2.1\bin\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    02:18:26,044 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem

    02:18:28,059 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Démarrage de Coyote HTTP/1.1 sur http-localhost-127.0.0.1-8080

    02:18:29,262 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /127.0.0.1:9999

    02:18:30,622 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-2) Starting remote JMX connector

    02:18:33,825 INFO  [org.jboss.as.connector] (MSC service thread 1-1) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)

    02:18:36,247 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS]

    02:18:36,247 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/jbpmDS]

    02:18:42,231 INFO  [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory C:\jbpm-installer\jboss-as-7.0.2.Final\standalone\deployments

    02:18:43,794 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 44719ms - Started 97 of 152 services (55 services are passive or on-demand)

    02:18:44,809 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "drools-guvnor.war"

    02:18:44,809 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "jbpm-gwt-console-server.war"

    02:18:45,153 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "jbpm-gwt-console.war"

    02:18:45,153 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "designer.war"

    09:10:18,296 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)

    09:10:18,577 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.

    09:10:19,343 INFO  [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem

    09:10:19,436 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

    09:10:19,452 INFO  [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem

    09:10:19,765 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem

    09:10:19,905 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2

    09:10:20,593 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3

    09:10:20,968 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3

    09:10:22,327 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_02\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jdk1.6.0_02\bin;C:\apache-ant-1.8.3\bin;C:\apache-maven-2.2.1\bin\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    09:10:22,921 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem

    09:10:23,015 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /127.0.0.1:9999

    09:10:23,030 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector

    09:10:25,155 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Démarrage de Coyote HTTP/1.1 sur http-localhost-127.0.0.1-8080

    09:10:25,749 INFO  [org.jboss.as.connector] (MSC service thread 1-1) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)

    09:10:26,030 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/jbpmDS]

    09:10:26,030 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/ExampleDS]

    09:10:28,624 INFO  [org.jboss.as.deployment] (MSC service thread 1-2) Started FileSystemDeploymentService for directory C:\jbpm-installer\jboss-as-7.0.2.Final\standalone\deployments

    09:10:28,765 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 36782ms - Started 97 of 152 services (55 services are passive or on-demand)

    09:10:29,046 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "drools-guvnor.war"

    09:10:29,046 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "designer.war"

    09:10:29,108 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "jbpm-gwt-console-server.war"

    09:10:29,108 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "jbpm-gwt-console.war"

    09:20:32,905 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:20:32,952 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "jbpm-gwt-console.war" was rolled back with failure message Operation cancelled

    09:20:34,311 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "jbpm-gwt-console-server.war" was rolled back with no failure message

    09:20:34,499 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "drools-guvnor.war" was rolled back with no failure message

    09:20:35,046 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "designer.war" was rolled back with no failure message

    09:20:34,311 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:20:35,046 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:20:35,171 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configurationfile and the server logs to find more about the status of the deployment.

    09:46:01,800 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)

    09:46:01,988 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.

    09:46:02,582 INFO  [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem

    09:46:02,675 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

    09:46:02,707 INFO  [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem

    09:46:02,941 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem

    09:46:03,144 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2

    09:46:03,566 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3

    09:46:03,894 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3

    09:46:05,144 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_02\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jdk1.6.0_02\bin;C:\apache-ant-1.8.3\bin;C:\apache-maven-2.2.1\bin\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

    09:46:05,566 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem

    09:46:05,957 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /127.0.0.1:9999

    09:46:06,379 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Démarrage de Coyote HTTP/1.1 sur http-localhost-127.0.0.1-8080

    09:46:06,457 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector

    09:46:08,191 INFO  [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)

    09:46:09,082 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/jbpmDS]

    09:46:09,082 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/ExampleDS]

    09:46:10,910 INFO  [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory C:\jbpm-installer\jboss-as-7.0.2.Final\standalone\deployments

    09:46:11,035 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 27735ms - Started 97 of 152 services (55 services are passive or on-demand)

  • 2. Re: http://localhost:8080/jbpm-console problem
    Feki Ahmed Newbie

    i had two jboss server starting in the same time... i found the same issue in this link https://community.jboss.org/message/649881

    even if i didn t have the same exeption ("java.net.BindException: Address already in use: JVM_Bind localhost/127.0.0.1:8080) i actually

    had both jboss versions 5 and 7 starting in the same time(it is mentionned in the command prompt when i type ant start.demo)

    and had the jboss AS 7 welcome page displaying in my localhost:8080. so i changed the build.xml like this (i ve commented the <antcall target="start.jboss5" /> and its "implementation" ):

     

    <!-- Start JBoss AS -->

      <target name="start.jboss">

        <!--<antcall target="start.jboss5" />-->

        <antcall target="start.jboss7" />

      </target>

      <target name="start.jboss7" depends="check.jboss.version" if="jboss.version.is.7">

        <property name="jboss.full.path.win" location="${jboss.home}/bin/standalone.bat" />

        <exec executable="${jboss.full.path.win}" spawn="yes"

              osfamily="windows">

          <env key="JAVA_OPTS" value="-XX:MaxPermSize=256m -Xms256m -Xmx512m" />

          <arg value="-b" />

          <arg value="${jboss.bind.address}" />

          <arg value="-Djbpm.console.directory=${install.home}/sample/evaluation/src/main/resources" />

          <arg value="-Dreporting.needcontext=true" />

        </exec>

        <property name="jboss.full.path.linux" location="${jboss.home}/bin/standalone.sh" />

        <exec executable="${jboss.full.path.linux}" spawn="yes" osfamily="unix">

          <env key="JAVA_OPTS" value="-XX:MaxPermSize=256m -Xms256m -Xmx512m" />

          <arg value="-b" />

          <arg value="${jboss.bind.address}" />

          <arg value="-Djbpm.console.directory=${install.home}/sample/evaluation/src/main/resources" />

          <arg value="-Dreporting.needcontext=true" />

        </exec>

        <waitfor maxwait="5" maxwaitunit="minute" checkevery="10"

                 checkeveryunit="second" timeoutproperty="jboss.timeout">

          <socket server="${jboss.bind.address}" port="8080" />

        </waitfor>

        <fail if="jboss.timeout" message="JBoss AS7 did not start within 5 minutes"/>

      </target>

      <!--<target name="start.jboss5" depends="check.jboss.version" unless="jboss.version.is.7">

        <property name="jboss.full.path.win" location="${jboss.home}/bin/run.bat" />

        <exec executable="${jboss.full.path.win}" spawn="yes"

              osfamily="windows">

          <env key="JAVA_OPTS" value="-XX:MaxPermSize=256m -Xms256m -Xmx512m" />

          <arg value="-b" />

          <arg value="${jboss.bind.address}" />

          <arg value="-Djbpm.console.directory=${install.home}/sample/evaluation/src/main/resources" />

        </exec>

        <property name="jboss.full.path.linux" location="${jboss.home}/bin/run.sh" />

        <exec executable="${jboss.full.path.linux}" spawn="yes" osfamily="unix">

          <env key="JAVA_OPTS" value="-XX:MaxPermSize=256m -Xms256m -Xmx512m" />

          <arg value="-b" />

          <arg value="${jboss.bind.address}" />

          <arg value="-Djbpm.console.directory=${install.home}/sample/evaluation/src/main/resources" />

        </exec>

        <waitfor maxwait="10" maxwaitunit="minute" checkevery="30"

                 checkeveryunit="second" timeoutproperty="jboss.timeout">

          <socket server="${jboss.bind.address}" port="8080" />

        </waitfor>

        <fail if="jboss.timeout" message="JBoss AS5 did not start within 10 minutes"/>

      </target>-->

     

     

    But still cant access to the http://localhost:8080/jbpm-console !!

     

    help please !!

  • 3. Re: http://localhost:8080/jbpm-console problem
    Feki Ahmed Newbie

    there were not enough space in the hard disk....pfff

  • 4. Re: http://localhost:8080/jbpm-console problem
    Sree . Newbie

    Guys,

     

    I just installed jboss-as-7.1.1.Final on windows7 64 bit. Iam could able to start Jboss server successfully.

     

    When Iam trying to access the page using http://localhost:8080, Iam getting unable to access page found.

     

    Its really frusturating with Jboss as they dont any thing straight farword.

     

    Appreciated if any help me in fixing the problem

     

    Thanks,

    Sree

  • 5. Re: http://localhost:8080/jbpm-console problem
    Sree . Newbie

    Guys,

     

    I just installed jboss-as-7.1.1.Final on windows7 64 bit. Iam could able to start Jboss server successfully.

     

    When Iam trying to access the page using http://localhost:8080, Iam getting unable to access page found.

     

    Its really frusturating with Jboss as they dont any thing straight farword.

     

    Appreciated if any help me in fixing the problem

     

    Thanks,

    Sree

  • 6. Re: http://localhost:8080/jbpm-console problem
    Feki Ahmed Newbie

    hi

    check if there is something blocking ur http such as an antivirus (i remember the nod32 antivirus was blocking it once..)

    and maybe also ur firewall configuration...

    cheers!

  • 7. Re: http://localhost:8080/jbpm-console problem
    wqe wqe Newbie

    I just ignored the form builder 's WAR  which costs about 500MB hard-disk space after explosion .The jboss 's start up time reduces 50 % after ignore this form builder.