3 Replies Latest reply on Jul 2, 2008 11:14 AM by brian.stansberry

    Port 4448 is already in use

    mbreuer

      While starting jboss 4.2.2.GA i get follwoing exception:

      2008-07-02 12:50:50,676 30122 WARN [org.jboss.system.ServiceController] (main:) Problem starting service jboss:service=invoker,type=po
      oledha
      java.lang.Exception: Port 4448 is already in use
       at org.jboss.invocation.pooled.server.PooledInvoker.startService(PooledInvoker.java:230)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      

      I think of an conflict in conf/jboss-service.xml and and deploy/cluster-service.xml.

      jboss-service.xml:
      <mbean code="org.jboss.remoting.transport.Connector"
       name="jboss.remoting:service=Connector,transport=socket"
       display-name="Socket transport Connector">
      ...
       <attribute name="Configuration">
      ...
       <attribute name="serverBindPort">4448</attribute>
      


      cluster-service.xml:
      <mbean code="org.jboss.invocation.pooled.server.PooledInvokerHA"
       name="jboss:service=invoker,type=pooledha">
       <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">4448</attribute>
      
      

      I am using cluster configuration (with jboss messaging, but i think that isn't the problem)

      Any ideas?

      markus



        • 1. Re: Port 4448 is already in use
          brian.stansberry

          In my checkout of 4.2.2, the serverBindPort in conf/jboss-service.xml is 4446.

          • 2. Re: Port 4448 is already in use
            mbreuer

            What about cluster-service.xml definitions? How should they be changed?
            I am using a standard jboss all-configuration.

            • 3. Re: Port 4448 is already in use
              brian.stansberry

              If you change the conf/jboss-service.xml to 4446 the conflict is gone; no need to change cluster-service.xml.

              I don't have the binary download for 4.2.2.GA on hand, just the source code (which is identical to the SVN tag for that release). In the source (and in a build from that source) the jboss.remoting:service=Connector,transport=socket serverBindPort value is 4446. Suggest you compare your conf/jboss-service.xml file with one from an unaltered 4.2.2.GA download and look for any other differences. IIRC, 4448 was used for jboss.remoting:service=Connector,transport=socket serverBindPort in some earlier releases. It's possible I'm wrong.