qPID JMX Management Console does not connect to qpid java broker on Windows.
Server Connection Failed. Reason: An unknown error has occurred.
---------------------------------------------------------------------------------------------------------------------------------------------
Key: QPID-2152
URL: https://issues.apache.org/jira/browse/QPID-2152
Project: Qpid
Issue Type: Bug
Components: Java Management : JMX Console
Affects Versions: 0.5
Environment: Windows XP, Java 1.6.0_16
Reporter: Ignacio Ybarra
Fix For: 0.5
- qpid-management-eclipse-plugin-0.5-win32-win32-x86\qpidmc.exe does not
connect to qpid-server on port 8999
- error message: Server Connection Failed. Reason: An unknown error has
occurred.
- telnet to 8999 works ok
- config.xml used contains following section: <management>
<enabled>true</enabled>
<jmxport>8999</jmxport>
<ssl>
<enabled>false</enabled>
<!-- Update below path to your keystore location, eg
${conf}/qpid.keystore -->
<keyStorePath>${conf}/qpid.keystore</keyStorePath>
<keyStorePassword>password</keyStorePassword>
</ssl>
</management>
- passwd file contains admin:admin
- jmxremote.access contains admin=admin
- log4j configured for additional debug info
- log shows
2009-10-17 12:07:25,910 INFO [main]
database.ConfigurationFilePrincipalDatabaseManager
(ConfigurationFilePrincipalDatabaseManager.java:54) - Initialising
PrincipleDatabase authentication manager
2009-10-17 12:07:25,910 INFO [main]
database.ConfigurationFilePrincipalDatabaseManager
(ConfigurationFilePrincipalDatabaseManager.java:54) - Initialising
PrincipleDatabase authentication manager
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:96) - PlainPasswordFile using file
D:\ig\installs\amqp\qpid\qpid-java-0.5\qpid-0.5\etc\passwd
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:96) - PlainPasswordFile using file
D:\ig\installs\amqp\qpid\qpid-java-0.5\qpid-0.5\etc\passwd
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:guest
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:guest
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:client
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:client
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:server
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:server
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:admin
2009-10-17 12:07:25,926 INFO [main]
database.PlainPasswordFilePrincipalDatabase
(PlainPasswordFilePrincipalDatabase.java:368) - Created user:admin
2009-10-17 12:07:25,926 INFO [main]
database.ConfigurationFilePrincipalDatabaseManager
(ConfigurationFilePrincipalDatabaseManager.java:100) - Initialised principal
database 'passwordfile' successfully
2009-10-17 12:07:25,926 INFO [main]
database.ConfigurationFilePrincipalDatabaseManager
(ConfigurationFilePrincipalDatabaseManager.java:100) - Initialised principal
database 'passwordfile' successfully
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:66) - Initialising Default
PrincipleDatabase authentication manager.
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:66) - Initialising Default
PrincipleDatabase authentication manager.
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:173) - Initialised AMQPLAIN SASL
provider successfully
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:173) - Initialised AMQPLAIN SASL
provider successfully
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:173) - Initialised PLAIN SASL
provider successfully
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:173) - Initialised PLAIN SASL
provider successfully
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:173) - Initialised CRAM-MD5 SASL
provider successfully
2009-10-17 12:07:25,926 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:173) - Initialised CRAM-MD5 SASL
provider successfully
2009-10-17 12:07:26,035 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:111) - Additional SASL providers
successfully registered.
2009-10-17 12:07:26,035 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:111) - Additional SASL providers
successfully registered.
2009-10-17 12:07:26,067 DEBUG [main] management.AMQUserManagementMBean
(AMQUserManagementMBean.java:497) - Setting Access Rights:{admin=admin}
2009-10-17 12:07:26,067 DEBUG [main] management.AMQUserManagementMBean
(AMQUserManagementMBean.java:497) - Setting Access Rights:{admin=admin}
2009-10-17 12:07:26,067 WARN [main] management.JMXManagedObjectRegistry
(JMXManagedObjectRegistry.java:196) - Starting JMX ConnectorServer on port
'8999' (+9099)
2009-10-17 12:07:26,067 WARN [main] management.JMXManagedObjectRegistry
(JMXManagedObjectRegistry.java:196) - Starting JMX ConnectorServer on port
'8999' (+9099)
2009-10-17 12:07:26,067 WARN [main] management.JMXManagedObjectRegistry
(JMXManagedObjectRegistry.java:197) - Starting JMX ConnectorServer on port
'8999' (+9099)
2009-10-17 12:07:26,238 DEBUG [main] virtualhost.VirtualHost
(VirtualHost.java:287) - Loading configuration for virtualhost: development
2009-10-17 12:07:26,238 DEBUG [main] virtualhost.VirtualHost
(VirtualHost.java:287) - Loading configuration for virtualhost: development
2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost
(VirtualHost.java:358) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@df48c4 with routing key
'queue' to exchange:org.apache.qpid.server.virtualhost.virtualh...@1226a77
2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost
(VirtualHost.java:358) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@df48c4 with routing key
'queue' to exchange:org.apache.qpid.server.virtualhost.virtualh...@1226a77
2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@df48c4 with routing key
'queue' to exchange:DirectExchange[amq.direct]
2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@df48c4 with routing key
'queue' to exchange:DirectExchange[amq.direct]
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@df48c4 with routing key
'queue' to exchange:DirectExchange[<<default>>]
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@df48c4 with routing key
'queue' to exchange:DirectExchange[<<default>>]
2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost
(VirtualHost.java:358) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@dc86eb with routing key
'ping' to exchange:org.apache.qpid.server.virtualhost.virtualh...@1226a77
2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost
(VirtualHost.java:358) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@dc86eb with routing key
'ping' to exchange:org.apache.qpid.server.virtualhost.virtualh...@1226a77
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@dc86eb with routing key
'ping' to exchange:DirectExchange[amq.direct]
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@dc86eb with routing key
'ping' to exchange:DirectExchange[amq.direct]
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@dc86eb with routing key
'ping' to exchange:DirectExchange[<<default>>]
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange
(DirectExchange.java:178) - Binding
queue:org.apache.qpid.server.queue.simpleamqqu...@dc86eb with routing key
'ping' to exchange:DirectExchange[<<default>>]
2009-10-17 12:07:26,285 INFO [main] store.MemoryMessageStore
(MemoryMessageStore.java:69) - Using capacity 50000 for hash tables
2009-10-17 12:07:26,285 INFO [main] store.MemoryMessageStore
(MemoryMessageStore.java:69) - Using capacity 50000 for hash tables
2009-10-17 12:07:26,285 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:66) - Initialising 'development'
PrincipleDatabase authentication manager.
2009-10-17 12:07:26,285 INFO [main]
manager.PrincipalDatabaseAuthenticationManager
(PrincipalDatabaseAuthenticationManager.java:66) - Initialising 'development'
PrincipleDatabase authentication manager.
2009-10-17 12:07:26,285 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section principal-databases is
2009-10-17 12:07:26,285 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section principal-databases is
2009-10-17 12:07:26,301 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section access is
2009-10-17 12:07:26,301 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section access is
2009-10-17 12:07:26,301 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section msg-auth is
2009-10-17 12:07:26,301 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section msg-auth is
2009-10-17 12:07:26,301 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section jmx is
2009-10-17 12:07:26,301 WARN [main] access.ACLManager (ACLManager.java:99) -
Plugin handling security section jmx is
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
