Can you raise a Jira for this?

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Feb 16, 2010 at 11:04 PM, wrfeldmann <w...@rf-consulting.com> wrote:

>
> Not really.  We're running 2 servers for failover reasons, and would really
> like to run them in a cluster with failover.  Multiple instances on 1
> server
> won't provide failover.
>
> activemq-admin stop --all
>
> does not stop the jvm if the server is waiting for the exclusive lock.  it
> does stop the jvm if the server is actively processing messages.
>
> activemq-admin stop --all should stop the jvm even if the server is waiting
> for an exclusive lock.
>
>
> Marc Schöchlin wrote:
> >
> > Hi,
> >
> > maybe the following init-script might be an option.
> >
> > https://issues.apache.org/activemq/browse/AMQ-2453
> >
> > This script is also capable to run multiple instances of activemq.
> >
> > -- Usage:
> >
> > $ ./activemq
> > INFO: loading '/home/mschoechlin/.activemqrc'
> > INFO: useing java '/home/mschoechlin/myroot/ibm-java-x86_64-60/bin/java'
> > Java Runtime: IBM Corporation 1.6.0
> > /home/mschoechlin/myroot/ibm-java-x86_64-60/jre
> >   Heap sizes: current=4096k  free=3080k  max=524288k
> >     JVM args: -Xjcl:jclscar_24
> >
> -Dcom.ibm.oti.vm.bootstrap.library.path=/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/amd64/default:/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/amd64
> >
> -Dsun.boot.library.path=/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/amd64/default:/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/amd64
> >
> -Djava.library.path=/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/amd64/default:/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/amd64:/usr/lib
> > -Djava.home=/home/mschoechlin/myroot/ibm-java-x86_64-60/jre
> > -Djava.ext.dirs=/home/mschoechlin/myroot/ibm-java-x86_64-60/jre/lib/ext
> > -Duser.dir=/home/mschoechlin/temp/apache-activemq-data/conf
> > _j2se_j9=1119744 -Djava.runtime.version=pxa6460sr6-20090925_01 (SR6)
> > -Xdump -Djava.class.path=.
> > -Dactivemq.classpath=/home/mschoechlin/temp/apache-activemq-data/conf/;
> > -Dactivemq.home=/home/mschoechlin/temp/apache-activemq-5.3.0
> > -Dactivemq.base=/home/mschoechlin/temp/apache-activemq-5.3.0
> >
> -Djava.class.path=/home/mschoechlin/temp/apache-activemq-5.3.0/bin/run.jar
> >
> -Dsun.java.command=/home/mschoechlin/temp/apache-activemq-5.3.0/bin/run.jar
> > -Dsun.java.launcher=SUN_STANDARD -Dsun.java.launcher.pid=7620
> > _port_library _org.apache.harmony.vmi.portlib
> > ACTIVEMQ_HOME: /home/mschoechlin/temp/apache-activemq-5.3.0
> > ACTIVEMQ_BASE: /home/mschoechlin/temp/apache-activemq-5.3.0
> > Usage: Main [--extdir <dir>] [task] [task-options] [task data]
> >
> > Tasks (default task is start):
> >     start           - Creates and starts a broker using a configuration
> > file, or a broker URI.
> >     stop            - Stops a running broker specified by the broker
> name.
> >     list            - Lists all available brokers in the specified JMX
> > context.
> >     query           - Display selected broker component's attributes and
> > statistics.
> >     browse          - Display selected messages in a specified
> > destination.
> >
> > Task Options (Options specific to each task):
> >     --extdir <dir>  - Add the jar files in the directory to the
> classpath.
> >     --version       - Display the version information.
> >     -h,-?,--help    - Display this help information. To display task
> > specific help, use Main [task] -h,-?,--help
> >
> > Task Data:
> >     - Information needed by each specific task.
> >
> >
> > Tasks provided by the sysv init script:
> >     restart         - stop running instance (is there is one), start new
> > instance
> >     fgstart         - start daemon in foreground, usful for debugging
> > purposes
> >     status          - check if activemq process is running
> >     setup           - create the specified configuration file for this
> > init script
> >                       (see next usage section)
> >
> > Configuration of this script:
> >     The configuration of this script can be placed on
> > /etc/default/activemq or /home/mschoechlin/.activemqrc.
> >     To use addtional configurations for running multiple instances on
> > the same operating system
> >     rename or symlink script to a name matching to
> > activemq-instance-<INSTANCENAME>.
> >     This changes the configuration location to
> > /etc/default/activemq-instance-<INSTANCENAME> and
> >     $HOME/.activemqrc-instance-<INSTANCENAME>. Configuration files in
> > /etc have higher precedence.
> > ---
> >
> > Regards
> > Marc
> >
> > wrfeldmann schrieb:
> >> I've searched both forums and have found nothing specific to the problem
> >> I'm
> >> having.  I'm using activemq 5.3.0 with 2 servers running.  I've enabled
> >> all
> >> of the jmx components in the activemq.xml file
> >>
> >>         <managementContext>
> >>             <managementContext
> >> connectorPath="service:jmx:rmi://${backside.server.name}:1099/jmxrmi"
> />
> >>         </managementContext>
> >>
> >> and in both the bin/activemq and bin/activemq-admin
> >>
> >> SUNJMX="-Dcom.sun.management.jmxremote.port=1099
> >> -Dcom.sun.management.jmxremote.authenticate=false
> >> -Dcom.sun.management.jmxremote.ssl=false"
> >>
> >> We have 2 activemq servers up and running.  The server that starts first
> >> will stop properly when activemq-admin stop is issued.  The server that
> >> was
> >> started second and is attempting to acquire the exclusive lock will not
> >> stop
> >> when the activemq-admin stop is issued.
> >>
> >> before stop:
> >>
> >>  /usr/java/jre1.6.0_17/bin/java -Xmx512M
> >> -Dorg.apache.activemq.UseDedicatedTaskRunner=true
> >> -Dcom.sun.management.snmp.port=1161
> >> -Dcom.sun.management.snmp.interface=acsamq00.int.brivo.net
> >> -Dcom.sun.management.snmp.acl.file=/home/jboss/brivo/snmp.acl
> >> -Dcom.sun.management.jmxremote.port=1099
> >> -Dcom.sun.management.jmxremote.authenticate=false
> >> -Dcom.sun.management.jmxremote.ssl=false
> >> -Dactivemq.classpath=/usr/local/messaging/messaging/conf;
> >> -Dactivemq.home=/usr/local/messaging/messaging
> >> -Dactivemq.base=/usr/local/messaging/messaging -jar
> >> /usr/local/messaging/messaging/bin/run.jar start
> >>
> >> actvemq-admin stop output:
> >>
> >> Java Runtime: Sun Microsystems Inc. 1.6.0_17 /usr/java/jre1.6.0_17
> >>   Heap sizes: current=7680k  free=7281k  max=506816k
> >>     JVM args: -Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true
> >> -Dactivemq.classpath=/usr/local/messaging/messaging/conf;
> >> -Dactivemq.home=/usr/local/messaging/messaging
> >> -Dactivemq.base=/usr/local/messaging/messaging
> >> ACTIVEMQ_HOME: /usr/local/messaging/messaging
> >> ACTIVEMQ_BASE: /usr/local/messaging/messaging
> >> Connecting to JMX URL:
> >> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> >> INFO: There are no brokers to stop.
> >>
> >> after stop
> >>
> >> /usr/java/jre1.6.0_17/bin/java -Xmx512M
> >> -Dorg.apache.activemq.UseDedicatedTaskRunner=true
> >> -Dcom.sun.management.snmp.port=1161
> >> -Dcom.sun.management.snmp.interface=acsamq00.int.brivo.net
> >> -Dcom.sun.management.snmp.acl.file=/home/jboss/brivo/snmp.acl
> >> -Dcom.sun.management.jmxremote.port=1099
> >> -Dcom.sun.management.jmxremote.authenticate=false
> >> -Dcom.sun.management.jmxremote.ssl=false
> >> -Dactivemq.classpath=/usr/local/messaging/messaging/conf;
> >> -Dactivemq.home=/usr/local/messaging/messaging
> >> -Dactivemq.base=/usr/local/messaging/messaging -jar
> >> /usr/local/messaging/messaging/bin/run.jar start
> >>
> >> Thanks,
> >>
> >> Rick
> >>
> >
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/activemq-admin-stop-does-not-work-tp27609710p27615555.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Reply via email to