activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-2329) Queue.send NPE in broker => inoperative broker
Date Mon, 15 Aug 2011 22:41:29 GMT

     [ https://issues.apache.org/jira/browse/AMQ-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-2329.
-----------------------------

    Resolution: Incomplete

Unable to reproduce, no test case attached.  User can reopen if the problem reappears in a
later release.

> Queue.send NPE in broker => inoperative broker
> ----------------------------------------------
>
>                 Key: AMQ-2329
>                 URL: https://issues.apache.org/jira/browse/AMQ-2329
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: craig mcmillan
>             Fix For: 5.6.0
>
>
> after correct operation for some time, an NPE in the broker renders the broker inoperable.
restart is required
> these mails describe two instances of what seem to be the same problem :
> http://www.nabble.com/NPE-in-broker-%3D%3E-inoperative-broker-to24586798.html
> http://www.nabble.com/What-can-be-the-reason---td21750762.html#a21750762
> below is activemq related logging from broker start to failure. info level and above
only unfortunately 
> the tcp:///127.0.0.1:55870 is a client connection
> i only have one broker. there were two clients, one in the same vm, producing only, and
one in a different vm both consuming and producing, each using a single tcp connection
> ------------------------>
> 20 Jul 2009 14:01:21,134 INFO  [BrokerService] (main:) - Using Persistence Adapter: AMQPersistenceAdapter(/home/sonar/sonar/local_storage/production_devcrunch01-reeep/amq)
> 20 Jul 2009 14:01:21,219 INFO  [KahaStore] (main:) - Kaha Store using data directory
/home/sonar/sonar/local_storage/production_devcrunch01-reeep/amq/kr-store/state
> 20 Jul 2009 14:01:21,348 INFO  [BrokerService] (main:) - ActiveMQ 5.2.0 JMS Message Broker
(sonar-production-devcrunch01-reeep) is starting
> 20 Jul 2009 14:01:21,348 INFO  [BrokerService] (main:) - For help or more information
please see: http://activemq.apache.org/
> 20 Jul 2009 14:01:21,527 INFO  [KahaStore] (main:) - Kaha Store using data directory
/home/sonar/sonar/local_storage/production_devcrunch01-reeep/amq/kr-store/data
> 20 Jul 2009 14:01:21,595 INFO  [TransportServerThreadSupport] (main:) - Listening for
connections at: tcp://devcrunch01:50639
> 20 Jul 2009 14:01:21,667 INFO  [TransportConnector] (main:) - Connector openwire Started
> 20 Jul 2009 14:01:21,668 INFO  [BrokerService] (main:) - ActiveMQ JMS Message Broker
(sonar-production-devcrunch01-reeep, ID:devcrunch01-55590-1248098481379-0:0) started
> 20 Jul 2009 14:02:19,904 INFO  [DiscoveryTransport] (Multicast Discovery Agent Notifier:)
- Adding new broker connection URL: tcp://devcrunch01:50639
> 20 Jul 2009 14:02:19,934 INFO  [FailoverTransport] (ActiveMQ Task:) - Successfully connected
to tcp://devcrunch01:50639
> 20 Jul 2009 14:36:24,989 INFO  [DiscoveryTransport] (Multicast Discovery Agent Notifier:)
- Adding new broker connection URL: tcp://devcrunch01:50639
> 20 Jul 2009 19:53:24,757 INFO  [DiscoveryTransport] (Multicast Discovery Agent Notifier:)
- Adding new broker connection URL: tcp://devcrunch01:50639
> 20 Jul 2009 19:53:25,249 WARN  [FailoverTransport] (ActiveMQ Transport: tcp://localhost/127.0.0.1:50639:)
- Transport failed to tcp://devcrunch01:50639 , attempting to automatically reconnect due
to: java.net.SocketException: Connection reset
> 20 Jul 2009 19:53:25,322 INFO  [FailoverTransport] (ActiveMQ Task:) - Successfully reconnected
to tcp://devcrunch01:50639
> 21 Jul 2009 09:03:59,091 INFO  [DiscoveryTransport] (Multicast Discovery Agent Notifier:)
- Adding new broker connection URL: tcp://devcrunch01:50639
> 21 Jul 2009 09:03:59,341 INFO  [FailoverTransport] (ActiveMQ Task:) - Successfully reconnected
to tcp://devcrunch01:50639
> 21 Jul 2009 09:03:59,362 WARN  [FailoverTransport] (InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@719bd84b:)
- Transport failed to tcp://devcrunch01:50639 , attempting to automatically reconnect due
to: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long:
localhost/127.0.0.1:50639
> 21 Jul 2009 09:04:14,136 ERROR [Service] (ActiveMQ Transport: tcp:///127.0.0.1:55870:)
- Async error occurred: java.lang.NullPointerException
> java.lang.NullPointerException
> 	at org.apache.activemq.broker.region.Queue.send(Queue.java:328)
> 	at org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:350)
> 	at org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:437)
> 	at org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:224)
> 	at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
> 	at org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:95)
> 	at org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
> 	at org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:450)
> 	at org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:639)
> 	at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:305)
> 	at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:179)
> 	at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
> 	at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:143)
> 	at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:206)
> 	at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> 	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
> 	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:185)
> 	at java.lang.Thread.run(Thread.java:619)

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

        

Mime
View raw message