You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (Created) (JIRA)" <ji...@apache.org> on 2012/04/12 07:48:42 UTC
[jira] [Created] (APLO-189) UDP connector cannot be killed
UDP connector cannot be killed
------------------------------
Key: APLO-189
URL: https://issues.apache.org/jira/browse/APLO-189
Project: ActiveMQ Apollo
Issue Type: Bug
Environment: apollo-99-trunk-20120409.204714-16
Reporter: Lionel Cons
After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
The console reports (just after the ^C):
WARN | java.lang.NullPointerException
INFO | Stopped connector at: tls://0.0.0.0:6133
INFO | Stopped connector at: tcp://0.0.0.0:6123
INFO | Stopped connector at: wss://0.0.0.0:6134
INFO | Stopped connector at: ws://0.0.0.0:6124
INFO | broker shutdown is waiting on stop connector: udp
Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-189) UDP connector cannot be stopped
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-189:
-------------------------------
Fix Version/s: (was: 1.2)
1.3
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.3
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-189) UDP connector cannot be stopped
Posted by "Lionel Cons (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253164#comment-13253164 ]
Lionel Cons commented on APLO-189:
----------------------------------
For the record, my apollo.xml contains:
<connector id="udp" bind="udp://0.0.0.0:12345" protocol="udp">
<udp topic="syslog"/>
</connector>
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.2
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-189) UDP connector cannot be stopped
Posted by "Lionel Cons (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253163#comment-13253163 ]
Lionel Cons commented on APLO-189:
----------------------------------
Here are the traces. I've realized that the UDP port is incorrect. This is very weird since I copy/pasted the example you gave and it did work in the past...
2012-04-13 08:19:25,081 | INFO | Opening the log file took: 88.85 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
2012-04-13 08:19:25,198 | INFO | Accepting connections at: tls://0.0.0.0:6133 | console | hawtdispatch-DEFAULT-1
2012-04-13 08:19:25,246 | WARN | Error occured while accepting client connection. | org.apache.activemq.apollo.broker.Connector | hawtdispatch-DEFAULT-1
2012-04-13 08:19:25,260 | DEBUG | java.net.BindException: Address already in use | org.apache.activemq.apollo.broker.Connector | hawtdispatch-DEFAULT-1
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.DatagramChannelImpl.bind(DatagramChannelImpl.java:484)
at sun.nio.ch.DatagramSocketAdaptor.bind(DatagramSocketAdaptor.java:80)
at org.fusesource.hawtdispatch.transport.UdpTransportServer.accept(UdpTransportServer.java:92)
at org.fusesource.hawtdispatch.transport.UdpTransportServer._start(UdpTransportServer.java:67)
at org.fusesource.hawtdispatch.transport.ServiceBase$2.run(ServiceBase.java:95)
at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:96)
at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
2012-04-13 08:19:25,262 | INFO | Accepting connections at: tcp://0.0.0.0:6123 | console | hawtdispatch-DEFAULT-1
2012-04-13 08:19:25,262 | INFO | Accepting connections at: udp://0.0.0.0:0 | console | hawtdispatch-DEFAULT-1
2012-04-13 08:19:25,368 | INFO | Accepting connections at: ws://0.0.0.0:61124/ | console | Apollo Task
2012-04-13 08:19:25,553 | INFO | Accepting connections at: wss://0.0.0.0:61134/ | console | Apollo Task
2012-04-13 08:19:26,928 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
2012-04-13 08:19:26,929 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
I then ^C:
2012-04-13 08:19:34,927 | WARN | java.lang.NullPointerException | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-3
2012-04-13 08:19:34,927 | DEBUG | java.lang.NullPointerException | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-3
java.lang.NullPointerException
at org.fusesource.hawtdispatch.transport.ServiceBase.stop(ServiceBase.java:123)
at org.fusesource.hawtdispatch.transport.UdpTransportServer._stop(UdpTransportServer.java:107)
at org.fusesource.hawtdispatch.transport.ServiceBase$3.run(ServiceBase.java:129)
at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:96)
at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
2012-04-13 08:19:34,928 | INFO | Stopped connector at: tls://0.0.0.0:6133 | console | hawtdispatch-DEFAULT-3
2012-04-13 08:19:34,928 | INFO | Stopped connector at: tcp://0.0.0.0:6123 | console | hawtdispatch-DEFAULT-3
2012-04-13 08:19:34,950 | INFO | Stopped connector at: ws://0.0.0.0:6124 | console | Apollo Task
2012-04-13 08:19:34,950 | INFO | Stopped connector at: wss://0.0.0.0:6134 | console | Apollo Task
2012-04-13 08:19:35,921 | INFO | stopping broker is waiting on stop broker: default | org.apache.activemq.apollo.util.LoggingTracker | hawtdispatch-DEFAULT-1
2012-04-13 08:19:39,926 | INFO | broker shutdown is waiting on stop connector: udp | console | hawtdispatch-DEFAULT-1
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.2
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-189) UDP connector cannot be stopped
Posted by "Lionel Cons (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lionel Cons updated APLO-189:
-----------------------------
Summary: UDP connector cannot be stopped (was: UDP connector cannot be killed)
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-189) UDP connector cannot be stopped
Posted by "Lionel Cons (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253170#comment-13253170 ]
Lionel Cons commented on APLO-189:
----------------------------------
One more test, one more piece of information...
It seems that Apollo did pick the right port number and did fail to bind (Address already in use). After that, it goes mad:
- it does not report the bind() error message as an error
- it tries to continue the startup
- it reports NPE
- it incorrectly reports 0 as the port number
- it cannot be stopped, only kill -9 gets rid of it
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.2
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (APLO-189) UDP connector cannot be stopped
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved APLO-189.
--------------------------------
Resolution: Duplicate
Closing as a dup of APLO-265. This is due to a generalized problem that we need to more consistently solve.
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.5
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-189) UDP connector cannot be stopped
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-189:
-------------------------------
Fix Version/s: (was: 1.4)
1.5
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.5
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-189) UDP connector cannot be stopped
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-189:
-------------------------------
Fix Version/s: (was: 1.3)
1.4
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.4
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-189) UDP connector cannot be stopped
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-189:
-------------------------------
Component/s: apollo-broker
Fix Version/s: 1.2
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.2
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-189) UDP connector cannot be stopped
Posted by "Hiram Chirino (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252580#comment-13252580 ]
Hiram Chirino commented on APLO-189:
------------------------------------
If you enable debug logging in the broker, the stack trace for the NullPointerException should appear in the apollo.log file. Could you fish that out an paste that into the issue?
> UDP connector cannot be stopped
> -------------------------------
>
> Key: APLO-189
> URL: https://issues.apache.org/jira/browse/APLO-189
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120409.204714-16
> Reporter: Lionel Cons
> Fix For: 1.2
>
>
> After enabling the UDP connector in apollo.xml and starting the broker interactively, it cannot be stopped on the command line by typing ^C.
> The console reports (just after the ^C):
> WARN | java.lang.NullPointerException
> INFO | Stopped connector at: tls://0.0.0.0:6133
> INFO | Stopped connector at: tcp://0.0.0.0:6123
> INFO | Stopped connector at: wss://0.0.0.0:6134
> INFO | Stopped connector at: ws://0.0.0.0:6124
> INFO | broker shutdown is waiting on stop connector: udp
> Then it is stuck. Further ^C or kill -TERM have no effect. It has to be killed with kill -KILL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira