qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3743) [Java Broker] Remove catching of Exception during metadata retrieval in BDB store
Date Fri, 17 Feb 2012 09:43:59 GMT

    [ https://issues.apache.org/jira/browse/QPID-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210162#comment-13210162
] 

Robbie Gemmell commented on QPID-3743:
--------------------------------------

Updated title to reflect new scope. It has not been possible to reproduce the NPE seen above,
and Rob is unsure it was on a clean trunk following some changes to persistence etc. What
is clear though is that the NPE should only be possible if an exception was caught and null
returned, where really the exception should have been thrown. This JIRA will now be used to
make that change.
                
> [Java Broker] Remove catching of Exception during metadata retrieval in BDB store
> ---------------------------------------------------------------------------------
>
>                 Key: QPID-3743
>                 URL: https://issues.apache.org/jira/browse/QPID-3743
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Broker BDB Store
>            Reporter: Rob Godfrey
>            Assignee: Alex Rudyy
>            Priority: Blocker
>             Fix For: 0.15
>
>         Attachments: 0001-QPID-3743-Remove-try-catch-block-on-converting-BDB-m.patch
>
>
> Occurred while using BDB store with more messages than could be held in RAM (1 million
1Kb messages in a 2Gb heap on a 64-bit VM).
> ########################################################################
> #
> # Unhandled Exception java.lang.NullPointerException in Thread pool-3-thread-16
> #
> # Exiting
> #
> ########################################################################
> java.lang.NullPointerException
> 	at org.apache.qpid.server.message.MessageTransferMessage.getExpiration(MessageTransferMessage.java:89)
> 	at org.apache.qpid.server.queue.QueueEntryImpl.expired(QueueEntryImpl.java:151)
> 	at org.apache.qpid.server.queue.SimpleAMQQueue.getNextAvailableEntry(SimpleAMQQueue.java:1846)
> 	at org.apache.qpid.server.queue.SimpleAMQQueue.attemptDelivery(SimpleAMQQueue.java:1781)
> 	at org.apache.qpid.server.queue.SimpleAMQQueue.processQueue(SimpleAMQQueue.java:1964)
> 	at org.apache.qpid.server.queue.QueueRunner.run(QueueRunner.java:77)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:722)

--
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

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message