[INT-3066] Possible NPE In JMS OB Gateway ReplyListener During Connection Recovery - Spring JIRA

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Critical
Resolution: Complete
Affects Version/s: 3.0 M2, 2.2.4
Fix Version/s: 2.2.5, 3.0 M3
Component/s: None
Labels:
- PullRequest

Reference URL:
http://forum.springsource.org/showthread.php?138795-reply-listener-may-not-recover-from-network-outage

Description

Reply ListenerContainer (if configured) can throw an NPE while the DMLC is trying to recover the connection.

It is benign (in that it doesn't affect functtionality) but it prevents logging the status message about the inability to reconnect.

Exception in thread "org.springframework.integration.jms.JmsOutboundGateway#0.replyListener-55" java.lang.NullPointerException
     at org.springframework.jms.listener.AbstractMessageListenerContainer.getDestinationDescription(AbstractMessageListenerContainer.java:207)
     at org.springframework.integration.jms.JmsOutboundGateway$GatewayReplyListenerContainer.getDestinationDescription(JmsOutboundGateway.java:1034)
     at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:881)
     at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:851)
     at org.springframework.integration.jms.JmsOutboundGateway$GatewayReplyListenerContainer.recoverAfterListenerSetupFailure(JmsOutboundGateway.java:1041)
     at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:982)
     at java.lang.Thread.run(Thread.java:680)

Attachments

Activity

People

Assignee:: Gary Russell

Reporter:: Gary Russell

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 14/Jun/13 8:51 AM

Updated:: 05/Sep/13 10:22 AM

Resolved:: 12/Jul/13 4:52 PM

Time Tracking

Estimated:

Remaining:

Logged:

Not Specified