[
https://issues.apache.org/jira/browse/QPID-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649939#action_12649939
]
Robert Gemmell commented on QPID-1482:
--------------------------------------
Whilst investigating this issue I was given the runaround by another issue,
whereby the broker would report the following exception instead of the one
listed above.
GenericConnectorServer ClientCreation.run
WARNING: Failed to open connection: java.lang.NullPointerException
java.lang.NullPointerException
at
com.sun.jmx.remote.generic.ProfileServerFactory.getProvider(ProfileServerFactory.java:272)
at
com.sun.jmx.remote.generic.ProfileServerFactory.createProfile(ProfileServerFactory.java:220)
at
com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:206)
at
com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98)
at
javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443)
at
com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:248)
at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:99)
A lot of debugging later and examining open source code from the OpenJVM and
the OpenDMK (the exception was occurinng within the jmxremote_optional.jar's
class files), I devised a workaround in setting the
"jmx.remote.profile.provider.class.loader" property within the environment map
used by the broker to start the JMXMP connector server. Shortly after that, i
found the real solution - it was my use of Eclipse to launch the broker to
debug the authentication issue which was itself causing this issue. Doh :)
> Management Console cant complete user authentication process
> ------------------------------------------------------------
>
> Key: QPID-1482
> URL: https://issues.apache.org/jira/browse/QPID-1482
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Management : JMX Console
> Affects Versions: M4
> Reporter: Robert Gemmell
>
> When the patches I supplied for QPID-1481 and QPID-794 are used, the
> management console is able to communicate with the broker across the
> JMXMPConnector link but is still unable to successfully complete the
> connection, however the failure now occurs during the authentication process
> as opposed to before it like previously. Despite this, the management console
> reports that "Qpid server is not running."
> Enabling debug console output for the management console yields the following
> exception listing:
> java.io.IOException: java.lang.NullPointerException
> at
> com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379)
> at
> com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:184)
> at
> com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:112)
> at
> javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:217)
> at
> javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:159)
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
> at
> org.apache.qpid.management.ui.jmx.JMXServerRegistry$ConnectorThread.run(JMXServerRegistry.java:204)
> at java.lang.Thread.run(Thread.java:619)
> java.io.IOException: java.lang.NullPointerException
> at
> com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379)
> at
> com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:184)
> at
> com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:112)
> at
> javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:217)
> at
> javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:159)
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
> at
> org.apache.qpid.management.ui.jmx.JMXServerRegistry$ConnectorThread.run(JMXServerRegistry.java:204)
> at java.lang.Thread.run(Thread.java:619)
> The broker was slightly more informative however, giving:
> GenericConnectorServer ClientCreation.run
> WARNING: Failed to open connection: java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.qpid.server.security.auth.database.PlainPasswordFilePrincipalDatabase.compareCharArray(PlainPasswordFilePrincipalDatabase.java:182)
> at
> org.apache.qpid.server.security.auth.database.PlainPasswordFilePrincipalDatabase.verifyPassword(PlainPasswordFilePrincipalDatabase.java:130)
> at
> org.apache.qpid.server.management.JMXManagedObjectRegistry$UserCallbackHandler.handle(JMXManagedObjectRegistry.java:267)
> at
> org.apache.qpid.server.security.auth.sasl.plain.PlainSaslServer.evaluateResponse(PlainSaslServer.java:81)
> at
> com.sun.jmx.remote.opt.security.SASLServerHandler.consumeMessage(SASLServerHandler.java:164)
> at
> com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:216)
> at
> com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98)
> at
> javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443)
> at
> com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadS
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
