Bug 536115 (RHQ-4)
| Summary: | Default RHQ Server install is conflicting with JBAS ejb3 connector ports | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
| Component: | No Component | Assignee: | John Mazzitelli <mazz> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://jira.rhq-project.org/browse/RHQ-4 | ||
| Whiteboard: | |||
| Fixed In Version: | 1.0 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
rev30 This bug was previously known as http://jira.rhq-project.org/browse/RHQ-4 |
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).