You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ignacio Ybarra (JIRA)" <qp...@incubator.apache.org> on 2009/10/17 13:11:31 UTC
[jira] Created: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPID-2152:
------------------------------------
Assignee: Robbie Gemmell
> 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
> Assignee: Robbie Gemmell
>
> - 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2152:
---------------------------------
Fix Version/s: 0.6
> 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
> Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> - 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2152:
---------------------------------
Status: Ready To Review (was: In Progress)
> 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
> Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> - 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-2152.
----------------------------------
Resolution: Fixed
> 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
> Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> - 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767153#action_12767153 ]
Robbie Gemmell commented on QPID-2152:
--------------------------------------
I have tested this on Windows XP and Vista and am able to successfully connect to the broker with the console. However, examining the code I have identified one issue that might cause the problem you are seeing, whereby if a connection is actually in progress but taking an unexpected amount of time to complete then a NullPointerException can occur which would lead to the connection appearing to fail and generate the output you are seeing.
If this is indeed the cause of the problem you are seeing, as a workaround you can alter the console configuration to allow an increased time for the connection to succeed or fail:
1. Open the qpidmc.ini file at the root of the console release
2. Add the value "-Dtimeout=15000" (without the quotes) on the empty line below "-Declipse.consoleLog=true"
We will look to correct the situation leading to the inaccurate error message in a future release, but if you confirm this workaround enables you to connect we will increase the default timeout currently in place as well.
> 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-2152:
---------------------------------
Fix Version/s: (was: 0.5)
> 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
>
> - 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2152) qPID JMX Management Console does not
connect to qpid java broker on Windows. Server Connection Failed. Reason:
An unknown error has occurred.
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785608#action_12785608 ]
Robbie Gemmell commented on QPID-2152:
--------------------------------------
I have increased the default timeout to 15 seconds, and updated the connection process to properly time out without resulting in the NPE leading to 'an unknown error has occured'.
> 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
> Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> - 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.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@df48c4 with routing key 'queue' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,270 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 INFO [main] virtualhost.VirtualHost (VirtualHost.java:358) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@dc86eb with routing key 'ping' to exchange:org.apache.qpid.server.virtualhost.VirtualHost@1226a77
> 2009-10-17 12:07:26,285 DEBUG [main] exchange.DirectExchange (DirectExchange.java:178) - Binding queue:org.apache.qpid.server.queue.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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.SimpleAMQQueue@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:dev-subscribe@qpid.apache.org