could you run netstat -a and make sure that port 1099 is open. That's the JMX management port that the broker will open to receive those JMX commands like shutdown.
On Tue, May 13, 2008 at 6:36 PM, Mike Miljour <[EMAIL PROTECTED]> wrote: > > I am encountering the same problem. Even if I use the default port of 61616, > I get the exact same exceptions. I am trying to upgrade from a snapshot 5.0 > from January. We need the ability to shutdown ActiveMQ from a script. > > Here is my configuration: > <broker xmlns="http://activemq.org/config/1.0"; > deleteAllMessagesOnStartup="true" > dataDirectory="//data" > persistent="true"> > > <!-- The transport connectors ActiveMQ will listen to --> > <transportConnectors> > <transportConnector name="openwire" > uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/> > </transportConnectors> > > </broker> > > > > Badri wrote: >> >> Hi >> >> I am using AMQ 5.1.0. I am unable to stop Active MQ. >> > > -- > View this message in context: > http://www.nabble.com/activemq-admin-error-during-stop-tp17218304s2354p17219861.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
