Bug 536115 (RHQ-4) - Default RHQ Server install is conflicting with JBAS ejb3 connector ports
Summary: Default RHQ Server install is conflicting with JBAS ejb3 connector ports
Keywords:
Status: CLOSED NEXTRELEASE
Alias: RHQ-4
Product: RHQ Project
Classification: Other
Component: No Component
Version: unspecified
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact:
URL: http://jira.rhq-project.org/browse/RHQ-4
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-25 17:26 UTC by John Mazzitelli
Modified: 2008-07-02 18:36 UTC (History)
0 users

Fixed In Version: 1.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description John Mazzitelli 2008-02-25 17:26:00 UTC
When I start an instance of JBAS5.0 beta4 when I already have JON 2.0 running I get the following. Shutting down JON and retrying the error goes away.

We should be using a non-standard port for our ejb3 connector (just like we do for http) so that people can run JBAS and JON side by side for demo purposes.


08:54:54,171 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@11fb2e0 for BaseClassLoader@16a16ae{vfsfi
le:/C:/usr/apps/jboss/jboss-5.0.0.Beta4/server/default/deploy/ejb3-interceptors-aop.xml}
08:54:59,765 ERROR [SocketServerInvoker] Error starting ServerSocket. Bind port: 3873, bind address: /127.0.0.1
08:54:59,765 ERROR [Connector] Error starting connector.
java.net.BindException: Address already in use: JVM_Bind
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:169)
        at org.jboss.remoting.transport.socket.SocketServerInvoker.createServerSocket(SocketServerInvoker.java:264)
        at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:193)
        at org.jboss.remoting.transport.Connector.start(Connector.java:322)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

this is due to:

<attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute>

that's in our ejb3.deployer

we need a new setting in RHQ so we can easily override it (and override it from the default 3873 so we do not conflict with other JBossAS instances).


Comment 1 John Mazzitelli 2008-02-26 07:12:01 UTC
rev30

Comment 2 Red Hat Bugzilla 2009-11-10 21:10:36 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-4



Note You need to log in before you can comment on or make changes to this bug.