Discussion:
[openjms-developer] [ openjms-Bugs-945785 ] NullPointerException using async delivery, selectors, queue
SourceForge.net
2004-05-01 07:28:00 UTC
Permalink
Bugs item #945785, was opened at 2004-05-01 17:28
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=945785&group_id=54559

Category: message engine
Group: v0.7.6
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: NullPointerException using async delivery, selectors, queue

Initial Comment:
(Originally from
http://article.gmane.org/gmane.comp.java.openjms.user/
1774 ):

The following exception occurs intermittently, when
using message selectors on a queue, with asynchronous
delivery and message expiration:

java.lang.NullPointerException
at
org.exolab.jms.selector.Identifier.evaluate
(Identifier.java:142)
at
org.exolab.jms.selector.LogicalOperator.evaluate
(LogicalOperator.java:86)
at org.exolab.jms.selector.Selector.selects
(Selector.java:262)
at
org.exolab.jms.messagemgr.QueueDestinationCache.getM
essage(QueueDestinationCache.java:510)
at
org.exolab.jms.messagemgr.QueueConsumerEndpoint.deliv
erMessages(QueueConsumerEndpoint.java:164)
at
org.exolab.jms.messagemgr.ConsumerEndpoint.run
(ConsumerEndpoint.java:425)
at
org.exolab.core.threadPool.ThreadPoolWorker.runIt
(ThreadPoolWorker.java:191)
at
org.exolab.core.threadPool.ThreadPoolWorker.runWork
(ThreadPoolWorker.java:178)
at
org.exolab.core.threadPool.ThreadPoolWorker.access$000
(ThreadPoolWorker.java:67)
at
org.exolab.core.threadPool.ThreadPoolWorker$1.run
(ThreadPoolWorker.java:122)
at java.lang.Thread.run(Thread.java:536)



----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=945785&group_id=54559
SourceForge.net
2004-05-01 12:07:04 UTC
Permalink
Bugs item #945785, was opened at 2004-05-01 17:28
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=945785&group_id=54559

Category: message engine
Group: v0.7.6
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: NullPointerException using async delivery, selectors, queue

Initial Comment:
(Originally from
http://article.gmane.org/gmane.comp.java.openjms.user/
1774 ):

The following exception occurs intermittently, when
using message selectors on a queue, with asynchronous
delivery and message expiration:

java.lang.NullPointerException
at
org.exolab.jms.selector.Identifier.evaluate
(Identifier.java:142)
at
org.exolab.jms.selector.LogicalOperator.evaluate
(LogicalOperator.java:86)
at org.exolab.jms.selector.Selector.selects
(Selector.java:262)
at
org.exolab.jms.messagemgr.QueueDestinationCache.getM
essage(QueueDestinationCache.java:510)
at
org.exolab.jms.messagemgr.QueueConsumerEndpoint.deliv
erMessages(QueueConsumerEndpoint.java:164)
at
org.exolab.jms.messagemgr.ConsumerEndpoint.run
(ConsumerEndpoint.java:425)
at
org.exolab.core.threadPool.ThreadPoolWorker.runIt
(ThreadPoolWorker.java:191)
at
org.exolab.core.threadPool.ThreadPoolWorker.runWork
(ThreadPoolWorker.java:178)
at
org.exolab.core.threadPool.ThreadPoolWorker.access$000
(ThreadPoolWorker.java:67)
at
org.exolab.core.threadPool.ThreadPoolWorker$1.run
(ThreadPoolWorker.java:122)
at java.lang.Thread.run(Thread.java:536)



----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2004-05-01 22:07

Message:
Logged In: YES
user_id=557161

Fixed in CVS. Fix will be available in the 0.7.6.1 release.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=945785&group_id=54559
Loading...