[
https://issues.apache.org/jira/browse/QPID-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128133#comment-13128133
]
Keith Wall commented on QPID-3274:
----------------------------------
Setting -Djava.rmi.server.hostname=localhost does not work around this problem.
JMXManagedObjectRegistry manually builds an external JMX service URL using the
value returned from InetAddress.getLocalHost().getHostName(). On the (Jenkins
Solaris) box with the illegal hostname, the resulting URL is illegal and fails
its own validation (method (JMXServiceURL#validate()).
java.rmi.server.hostname is not considered.
It seems to me that it would be a useful enhancement if
JMXManagedObjectRegistry used the contents of java.rmi.server.hostname when
building the *external* URL and only fell back to getHostName() when
unavailable. But the internal url should continue to use
InetAddress.getLocalHost().getHostName() (so would still fail with illegal
hostnames).
I think we should pursue getting the Solaris hostname corrected. Is an email
to the APache infrastructure list best?
> Jenkins CI - JMX test failures under Solaris
> --------------------------------------------
>
> Key: QPID-3274
> URL: https://issues.apache.org/jira/browse/QPID-3274
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Tests
> Affects Versions: 0.11
> Environment: Solaris/Hudson
> Reporter: Keith Wall
> Assignee: Keith Wall
> Labels: Hudson, Jenkins, Solaris
>
> Andrew K noticed whilst setting up Qpid under Hudson that the JMX tests fail
> under Hudson on Solaris.
> The first error was:
> https://builds.apache.org/hudson/view/M-R/view/Qpid/job/qpid-java-build/3/testReport/junit/org.apache.qpid.management.jmx/ManagementActorLoggingTest/testJMXManagementConsoleConnection/
> {code}
> java.net.MalformedURLException: Bad URL path:
> _solaris:30099/jndi/rmi://hudson_solaris:29999/jmxrmi
> {code}
> followed by many instances of:
> https://builds.apache.org/hudson/view/M-R/view/Qpid/job/qpid-java-build/3/testReport/junit/org.apache.qpid.management.jmx/ManagementActorLoggingTest/testConnectionCloseViaManagement/
> {code}
> internal error: ObjID already in use
> {code}
> The full list of test failures is recorded here:
> https://builds.apache.org/hudson/view/M-R/view/Qpid/job/qpid-java-build/3/#showFailuresLink
> I tried the test cases standalone under OpenSolaris 11 and could not
> reproduce the problem.
> However, I notice that the initial error looks very much like the issue
> discussed here:
> http://apache-qpid-users.2158936.n2.nabble.com/Run-qpid-0-6-broker-error-in-Linux-td5517015.html
> Is the problem just being caused by the hostname on the Solaris host in the
> Jenkins build farm?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
