2 Replies Latest reply on Jul 23, 2015 1:43 AM by UDAYAN BHOWMIK

    failed to start controlller

    Karthik Dhamodharan Newbie

      I am trying to install BPM Suite on my local desktop (win 7) and getting following error repeatedly..

       

      Please assist.

       

       

      Failed to start Server after 6 attempts.

      org.jboss.as.cli.CliInitializationException: Failed to connect to the controller

          at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:280)

          at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:246)

          at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

          at java.lang.reflect.Method.invoke(Method.java:611)

          at org.jboss.modules.Module.run(Module.java:270)

          at org.jboss.modules.Main.main(Main.java:411)

      Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9999

          at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:951)

          at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:790)

          at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:766)

          at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:278)

          ... 8 more

      Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out

          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)

          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)

          at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:929)

          ... 11 more

      Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out

          at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)

          at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)

          at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)

          at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)

          at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:156)

          at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:118)

          at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)

          at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)

          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)

          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)

          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)

          ... 13 more

       

       

      Trying to connect to Management Interface...(2/3).

      Trying to connect to Management Interface...(3/3).

      Failed to connect to Management Interface after 3 attempts.

      Post-installation configuration has failed. See the log for a list of commands that were run. These can be manually run to achieve the same effect as the installation process.

      Running on-fail server check.

      Shutting server down.

      WARN: can't find jboss-cli.xml. Using default configuration values.

      Trying to connect to Management Interface...(1/5).

      Trying to connect to Management Interface...(2/5).

      Trying to connect to Management Interface...(3/5).

      Trying to connect to Management Interface...(4/5).

      Trying to connect to Management Interface...(5/5).

      Failed to connect to Management Interface after 5 attempts.

      org.jboss.as.cli.CommandFormatException: You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.

       

       

       

      Summary of my Install

       

      Installation path

      C:\Program Files (x86)

      Administrative User

      Username: admin

      Business Process Management Suite User

      BPMS username: bpmsAdmin

      Java Security Manager Configuration

      Enable the Java security manager: true

      Client Keystores Configuration

      Number of client keystores to generate: 1

      IPv6 configuration

      Enable pure IPv6 configuration: false

      Additional Configuration

      Vault Configuration: off SSL Configuration: off LDAP Configuration selected: off Install security-domain: off

        • 1. Re: failed to start controlller
          Kris Verlaenen Master

          It seems not to be able to connect to the application server, most likely because it didn't start up correctly.  It might be worth looking into the server.log (in jboss-eap-6.1\standalone\log) to see if there are any errors in there.

           

          Most common problems are either another server already running (on port 8080) and preventing this server from starting up, or some firewall or antivirus blocking something.

          • 2. Re: failed to start controlller
            UDAYAN BHOWMIK Newbie

            Hi,

             

            I am trying to install jboss-bpms-installer-6.0.2.GA-redhat-5.jar

             

            I am getting below error during installation.

             

            Exit code: 0

            Command completed successfully.

            JBOSS_HOME adjusted to: C:\Redhat jboss bpm suite 6_older_version\fresh bpm install\jboss-eap-6.1

            Starting Server.

            Calling "C:\Redhat jboss bpm suite 6_older_version\fresh bpm install\jboss-eap-6.1\bin\standalone.conf.bat"

            Setting JAVA property to 'C:\Program Files\Java\jdk1.6.0_11\bin\bin\java'

            Waiting for server to be ready. This could take up to 15 seconds.

            .

            .

            .

            .

            .

            .

            Failed to start Server after 6 attempts.

            The system cannot find the path specified.

            The system cannot find the path specified.

            The system cannot find the path specified.

            Trying to connect to Management Interface...(1/3).

            Trying to connect to Management Interface...(2/3).

            Trying to connect to Management Interface...(3/3).

            Failed to connect to Management Interface after 3 attempts.

            Post-installation configuration has failed. See the log for a list of commands that were run. These can be manually run to achieve the same effect as the installation process.

            Running on-fail server check.

            Shutting server down.

            Trying to connect to Management Interface...(1/5).

            Trying to connect to Management Interface...(2/5).

            Trying to connect to Management Interface...(3/5).

            Trying to connect to Management Interface...(4/5).

            Trying to connect to Management Interface...(5/5).

            Failed to connect to Management Interface after 5 attempts.

            Application Server successfully stopped.