activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Snyder (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2759) Nullpointer-Exception in Queue.send
Date Sat, 18 Sep 2010 16:47:58 GMT

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

Bruce Snyder updated AMQ-2759:
------------------------------

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> Nullpointer-Exception in Queue.send
> -----------------------------------
>
>                 Key: AMQ-2759
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2759
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.1
>         Environment: red had enterprise
>            Reporter: Dennis Klinkott
>             Fix For: 5.5.0
>
>         Attachments: activemq.xml
>
>
> We found the following NullPointerException in our logs:
> 2010-06-02 07:13:15,434 WARN  org.apache.activemq.broker.TransportConnection.Service
- Async error occurred: java.lang.NullPointerException
> java.lang.NullPointerException
>         at org.apache.activemq.broker.region.Queue.send(Queue.java:442)
>         at org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:354)
>         at org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:445)
>         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.BrokerFilter.send(BrokerFilter.java:126)
>         at de.telefonica.CustomBrokerFilter.send(CustomBrokerFilter.java:103)
>         at org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
>         at org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:446)
>         at org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:631)
>         at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:300)
>         at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
>         at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
>         at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
>         at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:216)
>         at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>         at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:204)
>         at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:186)
>         at java.lang.Thread.run(Thread.java:619)
> This is logged only as log level WARN. Is this a severe problem that we should be concerned
about?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message