The problem was solved by installed ActiveMQ to a path that no space.:)
thiamteck wrote: > > I had installed ActiveMQ 4.1 on server with JDK 1.4.2 update 12. ActiveMQ > can start and running, however, it failed to start JMX. > > Below is the logs: > ============================================== > > 2007-06-14 12:32:26,609 [main ] INFO BrokerService > - ActiveMQ Message Broker (localhost, ID:centraldb-4923-1181797195625-1:0) > is shutting down > 2007-06-14 12:32:26,609 [main ] INFO NetworkConnector > - Network Connector default-nc Stopped > 2007-06-14 12:32:35,562 [main ] INFO BrokerService > - ActiveMQ 4.1.0-incubator JMS Message Broker (localhost) is starting > 2007-06-14 12:32:35,562 [main ] INFO BrokerService > - For help or more information please see: > http://incubator.apache.org/activemq/ > 2007-06-14 12:32:36,515 [main ] INFO JDBCPersistenceAdapter > - Database driver recognized: [apache_derby_embedded_jdbc_driver] > 2007-06-14 12:32:37,984 [main ] INFO DefaultDatabaseLocker > - Attempting to acquire the exclusive lock to become the Master broker > 2007-06-14 12:32:38,000 [main ] INFO DefaultDatabaseLocker > - Becoming the master on dataSource: > [EMAIL PROTECTED] > 2007-06-14 12:32:38,343 [main ] INFO KahaStore > - Kaha Store deleted data directory activemq-data\localhost\tmp_storage > 2007-06-14 12:32:38,453 [main ] INFO > TransportServerThreadSupport - Listening for connections at: > tcp://centraldb:61616 > 2007-06-14 12:32:38,453 [main ] INFO TransportConnector > - Connector openwire Started > 2007-06-14 12:32:38,593 [JMX connector ] WARN ManagementContext > - Failed to start jmx connector: javax.naming.CommunicationException [Root > exception is java.rmi.ServerException: RemoteException occurred in server > thread; nested exception is: > java.rmi.UnmarshalException: error unmarshalling arguments; nested > exception is: > java.net.MalformedURLException: no protocol: JMS/Queue/bin/../conf/] > 2007-06-14 12:32:38,625 [main ] INFO > TransportServerThreadSupport - Listening for connections at: > ssl://centraldb:61617 > 2007-06-14 12:32:38,625 [main ] INFO TransportConnector > - Connector ssl Started > 2007-06-14 12:32:38,640 [main ] INFO > TransportServerThreadSupport - Listening for connections at: > stomp://centraldb:61613 > 2007-06-14 12:32:38,640 [main ] INFO TransportConnector > - Connector stomp Started > 2007-06-14 12:32:38,640 [main ] INFO NetworkConnector > - Network Connector default-nc Started > 2007-06-14 12:32:38,640 [main ] INFO BrokerService > - ActiveMQ JMS Message Broker (localhost, > ID:centraldb-1991-1181804555125-1:0) started > > > =============================================== > > > any idea how to solve this? > -- View this message in context: http://www.nabble.com/Failed-to-start-jmx-connector-tf3920420s2354.html#a11170567 Sent from the ActiveMQ - User mailing list archive at Nabble.com.