You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Guy Allard (JIRA)" <ji...@apache.org> on 2011/08/14 17:47:27 UTC

[jira] [Created] (APLO-73) Service does not stop, Control-C in console does not work

Service does not stop, Control-C in console does not work
---------------------------------------------------------

                 Key: APLO-73
                 URL: https://issues.apache.org/jira/browse/APLO-73
             Project: ActiveMQ Apollo
          Issue Type: Bug
          Components: apollo-broker
    Affects Versions: 1.0-beta4, 1.0-beta3
         Environment: Ubuntu 11.04
Both beta 3 and beta4 installed from binaries.
Running as a normal user (not root).
            Reporter: Guy Allard


Have been running beta2, and decided to upgrade this morning.  I started with beta4.

1) When a broker is run from the command line, control-c fails to stop the broker
2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.

In both cases, only 'kill -9' has an effect.

apollo.log repeatedly shows messages like:

2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1

Same behavior with beta3.

Brokers are running with minimal configuration changes:

a) Disable authentication
b) Connector port number changes
c) log4j tweaks





--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-73.
-------------------------------

    Resolution: Fixed

> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Guy Allard (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086747#comment-13086747 ] 

Guy Allard commented on APLO-73:
--------------------------------

Hiram - Thanks.  We seem to be part of the way there.

Info: My keyboard etc. is US standard. All local US setup.  I am in Orlando, not far from where you are I think.

I confirm that this build:

apache-apollo-1.0-20110817.153140-174-unix-distro.tar.gz

Operates as you say above regarding use from the console only.  However .....

There remains a problem with 'stop' when running a broker from this build as a daemon.  And I confess I am a bit confused.

My setup, start and stop in /etc/init.d is:

[gmallard@tjjackson init.d]$ sudo ln -s /home/apollo/mybroker-snap/bin/apollo-broker-service apollo-broker-service 
[gmallard@tjjackson init.d]$ ls -l apollo-broker-service lrwxrwxrwx 1 root root 52 2011-08-17 22:14 apollo-broker-service -> /home/apollo/mybroker-snap/bin/apollo-broker-service
[gmallard@tjjackson init.d]$ sudo /etc/init.d/apollo-broker-service start
Starting apollo-broker-service
apollo-broker-service is now running (356)
[gmallard@tjjackson init.d]$ sudo /etc/init.d/apollo-broker-service stop
Gracefully Stopping apollo-broker-service
Could not stop process 356
[gmallard@tjjackson init.d]$ ps -ef | grep mybroker
root       356     1  0 22:15 pts/1    00:00:00 sudo -n -u apollo nohup /home/apollo/mybroker-snap/bin/apollo-broker run
apollo     358   356  6 22:15 pts/1    00:00:05 apollo -server -Xmx1G -Dcom.sun.management.jmxremote -Dapollo.home=/home/apollo/apache-apollo-1.0-beta4 -Dapollo.base=/home/apollo/mybroker-snap -classpath /home/apollo/apache-apollo-1.0-beta4/lib/apollo-boot.jar org.apache.activemq.apollo.boot.Boot /home/apollo/mybroker-snap/lib:/home/apollo/apache-apollo-1.0-beta4/lib org.apache.activemq.apollo.cli.Apollo run

Where does that ".....beta4" class path come from.  That directory currently does not exist on this machine (it did at one time, but not currently).






> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Guy Allard (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086763#comment-13086763 ] 

Guy Allard commented on APLO-73:
--------------------------------

OK, update.

Confirmed that build works.

I cleared the decks here, 

- got rid of all beta* subdirectories in /home/apollo
- recreated a broker from that snapshot
- tested command line start/stop
- tested daemon start/stop

I am still not sure of why "-beta4" showed in the previous logs.....

But all looks OK so far ith this snapshot.

I think this issue can be closed/resolved.

Regards, Guy


> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Guy Allard (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085455#comment-13085455 ] 

Guy Allard commented on APLO-73:
--------------------------------

With the SVN co mentioned, I eliminated all the changes mentioned which are:

a) Disable authentication
b) Connector port number changes
c) log4j tweaks

and I still get the same results.

I killed my AMQ broker to accommodate b).  So that apparently has nothing to do with this.

Suggestions?

Thanks, Guy




> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Reopened] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Guy Allard (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guy Allard reopened APLO-73:
----------------------------


Hiram - I get the same results with both of these:

a) apache-apollo-1.0-20110815.061655-170-unix-distro.tar.gz

b) SVN checkout of:

Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1157681

Can I give you any other information?


> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-73.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0-beta5
         Assignee: Hiram Chirino

> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086398#comment-13086398 ] 

Hiram Chirino commented on APLO-73:
-----------------------------------

Hi Guy,

I just tested the latest snapshot on Ubuntu 11.04 x64 as follows:

$ tar -zxf ~/Downloads/apache-apollo-1.0-20110817.153140-174-unix-distro.tar.gz
$ ./apache-apollo-1.0-SNAPSHOT/bin/apollo create test1
...
$ ./test1/bin/apollo-broker run

    _____                .__  .__
   /  _  \ ______   ____ |  | |  |   ____
  /  /_\  \\____ \ /  _ \|  | |  |  /  _ \
 /    |    \  |_> >  <_> )  |_|  |_(  <_> )
 \____|__  /   __/ \____/|____/____/\____/
         \/|__|  Apache Apollo (1.0-SNAPSHOT)


Loading configuration file '/home/chirino/opt/test1/etc/apollo.xml'.
INFO  | OS     : Linux 2.6.38-10-generic (Ubuntu 11.04)
INFO  | JVM    : OpenJDK 64-Bit Server VM 1.6.0_22 (Sun Microsystems Inc.)
INFO  | Apollo : 1.0-SNAPSHOT (at: /home/chirino/opt/apache-apollo-1.0-SNAPSHOT)
INFO  | OS is restricting the open file limit to: 4096
WARN  | Please increase the process file limit using 'ulimit -n 4500' or configure lower connection limits on the broker connectors.
INFO  | Accepting connections at: tls://0.0.0.0:61614
INFO  | Accepting connections at: tcp://0.0.0.0:61613
INFO  | Starting store: jdbm2 store at /home/chirino/opt/test1/data
INFO  | Administration interface available at: https://127.0.0.1:61681/
INFO  | Administration interface available at: http://127.0.0.1:61680/
^CINFO  | Stopped connector at: tls://0.0.0.0:61614
INFO  | Stopped connector at: tcp://0.0.0.0:61613
$

As you can see I pressed CTRL-C and it stopped the broker properly.  Perhaps it's a problem with the way jline is interpreting your keyboard layout.  You using something different than a US keyboard layout?

You could also stop the broker by running: kill ${pid}



> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (APLO-73) Service does not stop, Control-C in console does not work

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085069#comment-13085069 ] 

Hiram Chirino commented on APLO-73:
-----------------------------------

Yes, that should have been fixed since then.  Could you verify against a recent snapshot:

http://activemq.apache.org/apollo/download.html#Development_Snapshot


> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>             Fix For: 1.0-beta5
>
>
> Have been running beta2, and decided to upgrade this morning.  I started with beta4.
> 1) When a broker is run from the command line, control-c fails to stop the broker
> 2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could not stop process ####'.
> In both cases, only 'kill -9' has an effect.
> apollo.log repeatedly shows messages like:
> 2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds). Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
> Same behavior with beta3.
> Brokers are running with minimal configuration changes:
> a) Disable authentication
> b) Connector port number changes
> c) log4j tweaks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira