[JBoss JIRA] Created: (JBAS-3704) Add a notion of available interfaces to org.jboss.test.util.server.*
by Scott M Stark (JIRA)
Add a notion of available interfaces to org.jboss.test.util.server.*
--------------------------------------------------------------------
Key: JBAS-3704
URL: http://jira.jboss.com/jira/browse/JBAS-3704
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.4.GA
Reporter: Scott M Stark
Fix For: JBossAS-4.0.6.CR1
An issue with automating testing involving binding to specific addresses is that there is no predefined set of properties a testsuite descriptor can reference. The qa env has MYTESTIP_1 type of env vars set, and java 1.4.2+ has java.net.NetworkInterface, that could be used as the basis for defining jboss.server.iface.0..N system properties that configurations could rely on for setting one or more bind interfaces.
We need to add this functionality to the server startup tasks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
- 5
- 10
[JBoss JIRA] Updated: (JBREM-166) JMXConnectorServer will not start if using rmi invoker elsewhere
by Ron Sigal (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-166?page=all ]
Ron Sigal updated JBREM-166:
----------------------------
Fix Version/s: 2.4.0.Beta1 (Pinto)
Assignee: (was: Tom Elrod)
Adding fix version 2.4.0.Beta1.
This issue seems to be related to JBAS-3885: JMXConnectorServer not respecting the -b value, recently fixed by Dimitris, who changed the creation of the RMI registry in org.jboss.mx.remoting.service.JMXConnectorServerService.start() to use a ServerSocketFactory that binds to a single host. Maybe the same needs to be done in org.jboss.remoting.transport.rmi.RMIServerInvoker.
> JMXConnectorServer will not start if using rmi invoker elsewhere
> ----------------------------------------------------------------
>
> Key: JBREM-166
> URL: http://jira.jboss.com/jira/browse/JBREM-166
> Project: JBoss Remoting
> Issue Type: Bug
> Components: jmx remoting
> Affects Versions: JMX Remoting 1.0.1
> Reporter: Tom Elrod
> Fix For: JMX Remoting 1.0.2, 2.4.0.Beta1 (Pinto)
>
>
> If have a remoting invoker using rmi transport, it will create a rmi registry. Then when the JMXConnectorServer starts, it will also try to create one. Even though is on a different port, will get the following exception:
> java.rmi.server.ExportException: internal error: ObjID already in use
> at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> at sun.rmi.transport.Transport.exportObject(Transport.java:69)
> at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190)
> at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
> at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
> at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
> at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
- 1
- 0