3 Replies Latest reply on Jun 20, 2008 1:53 PM by Joe Smith

    Out-Of-Box server start-up error Port 4445 is already in use

    Danny Lin Newbie

      In Windows environment (XP Pro), I downloaded JBoss 4.2.1.GA zip file. Unzip the server and execute the run.bat. It is giving me a Java exception, stating Port 4445 is already in use. What is this? It appears the server did start up.


        • 2. Re: Out-Of-Box server start-up error Port 4445 is already in
          Danny Lin Newbie

          I used netstat -o but it did not show port 4445 was used. I noticed that port 4445 was defined in the jboss-service.xml out-of-the-box. I also added ReservedPorts to the registry with value 4445-4445. After rebooting the machine, I am still getting the same error.

          Any ideas? Thanks.

           <mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
           <attribute name="NumAcceptThreads">1</attribute>
           <attribute name="MaxPoolSize">300</attribute>
           <attribute name="ClientMaxPoolSize">300</attribute>
           <attribute name="SocketTimeout">60000</attribute>
           <attribute name="ServerBindAddress">${jboss.bind.address}</attribute>
           <attribute name="ServerBindPort">4445</attribute>
           <attribute name="ClientConnectAddress">${jboss.bind.address}</attribute>
           <attribute name="ClientConnectPort">0</attribute>
           <attribute name="ClientRetryCount">1</attribute>
           <attribute name="EnableTcpNoDelay">false</attribute>
           <!-- Customized socket factory attributes
           <attribute name="ClientSocketFactoryName">custom.client.factory</attribute>
           <attribute name="ServerSocketFactoryName">custom.server.factory</attribute>
           <attribute name="SslDomain">java:/jaas/pooledInvoker</attribute>
           <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>

          • 3. Re: Out-Of-Box server start-up error Port 4445 is already in
            Joe Smith Newbie

            Check to see if you are running a service called enstart.exe. If so, your company is running Encase Enterprise Edition and there is no way you are going to get Encase to stop using 4445 unless your support staff is willing to change it. I would change your jboss serverbindport to something else.

            If you can't find enstart.exe or this is a personal computer, try TCPView. It is part of the Sysinternals Suite (http://technet.microsoft.com/en-gb/sysinternals/0e18b180-9b7a-4c49-8120-c47c5a693683.aspx) by Microsoft. The Local Address will be your ComputerName:4445. It will tell you what process, the process ID, and if you double click on the process it will tell you where it is located on the Hard Drive.

            Good Luck