You might want to capture a stack trace of the broker while it's
trying to initialize the jmx connector to get an idea which call is
the one that's blocking excessively.  Is your DNS resolving name
quickly on that machine?

Regards,
Hiram

On Tue, Aug 5, 2008 at 5:51 PM, Dylan Vanderhoof <[EMAIL PROTECTED]> wrote:
> This is bizarre.  I have 3 servers running 5.2.0-SNAPSHOT from today.
>
> Their configuration is identical other than the broker name and broker URLs 
> in the activemq.xml file.
> On two on them activemq-admin works flawlessly, on the 3rd, it sits there for 
> 5+ minutes before returning a connection timed out for an IP address that's 
> the external network transport the others brokers connect to, but that should 
> have nothing to do with JMX.
>
> iptables shows only 1099 traffic to localhost, nothing to that IP.
>
> In addition, it takes some 5 minutes to start the ManagementContext 
> connector, which is completely at odds with what the other servers are doing. 
>  (Startup scroll pasted below with ip/host information masked)
>
> Has anybody run into a slow starting and/or non-responsive JMX connector 
> before?  The localhost:8161/admin webapp works just fine, but I'm not able to 
> use activemq-admin at all.
>
> -D
>
>
> [EMAIL PROTECTED] /var/log $ sudo cat /usr/local/activemq/data/activemq.log
> 2008-08-05 13:46:12,665 [main           ] INFO  BrokerService                 
>  - Using Persistence Adapter: AMQPersistenceAdapter(/usr/local/activemq/data)
> 2008-08-05 13:46:12,671 [main           ] INFO  AMQPersistenceAdapter         
>  - AMQStore starting using directory: /usr/local/activemq/data
> 2008-08-05 13:46:12,696 [main           ] INFO  KahaStore                     
>  - Kaha Store using data directory /usr/local/activemq/data/kr-store/state
> 2008-08-05 13:46:12,722 [main           ] INFO  AMQPersistenceAdapter         
>  - Active data files: []
> 2008-08-05 13:46:12,799 [main           ] INFO  BrokerService                 
>  - ActiveMQ 5.2-SNAPSHOT JMS Message Broker (llarian) is starting
> 2008-08-05 13:46:12,799 [main           ] INFO  BrokerService                 
>  - For help or more information please see: http://activemq.apache.org/
> 2008-08-05 13:46:12,944 [main           ] INFO  KahaStore                     
>  - Kaha Store using data directory /usr/local/activemq/data/kr-store/data
> 2008-08-05 13:46:12,961 [main           ] INFO  TransportServerThreadSupport  
>  - Listening for connections at: stomp://example.net:61613
> 2008-08-05 13:46:12,961 [main           ] INFO  TransportConnector            
>  - Connector stomp Started
> 2008-08-05 13:46:12,963 [main           ] INFO  TransportServerThreadSupport  
>  - Listening for connections at: tcp://1.2.3.4:61616
> 2008-08-05 13:46:12,963 [main           ] INFO  TransportConnector            
>  - Connector tcp://1.2.3.4:61616 Started
> 2008-08-05 13:46:12,964 [main           ] INFO  DiscoveryNetworkConnector     
>  - Establishing network connection between from vm://llarian to 
> tcp://netresponse-test.semaphore.com:61616
> 2008-08-05 13:46:12,984 [main           ] INFO  TransportConnector            
>  - Connector vm://llarian Started
> 2008-08-05 13:46:13,010 [main           ] INFO  NetworkConnector              
>  - Network Connector nr-test Started
> 2008-08-05 13:46:13,010 [main           ] INFO  BrokerService                 
>  - ActiveMQ JMS Message Broker (llarian, ID:cerberus-41952-1217969172813-0:0) 
> started
> 2008-08-05 13:46:13,049 [EMAIL PROTECTED] INFO  DemandForwardingBridge        
>  - Network connection between vm://llarian#0 and 
> tcp://netresponse-test.semaphore.com/209.221.128.8:61616(netresponse-test) 
> has been established.
> 2008-08-05 13:46:13,127 [main           ] INFO  log                           
>  - Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via 
> org.mortbay.log.Slf4jLog
> 2008-08-05 13:46:13,132 [main           ] INFO  log                           
>  - jetty-6.1.9
> 2008-08-05 13:46:13,525 [main           ] INFO  WebConsoleStarter             
>  - ActiveMQ WebConsole initialized.
> 2008-08-05 13:46:13,597 [main           ] INFO  /admin                        
>  - Initializing Spring FrameworkServlet 'dispatcher'
> 2008-08-05 13:46:13,651 [main           ] INFO  log                           
>  - ActiveMQ Console at http://0.0.0.0:8161/admin
> 2008-08-05 13:46:13,658 [main           ] INFO  log                           
>  - Started [EMAIL PROTECTED]:8161
> 2008-08-05 13:49:21,814 [JMX connector  ] INFO  ManagementContext             
>  - JMX consoles can connect to 
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Reply via email to