[
https://issues.apache.org/jira/browse/QPIDJMS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796377#comment-15796377
]
ASF subversion and git services commented on QPIDJMS-243:
---------------------------------------------------------
Commit 91e1b02ad42fcd734c411cac311fe6da228e1a38 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=91e1b02 ]
QPIDJMS-243 Fix potential NPE on close of resource
On close of a not fully initialized connection resource it could
encounter an NPE because the connection session was not created.
> NPE is reported when failover tries to connect to stopped/not available broker
> ------------------------------------------------------------------------------
>
> Key: QPIDJMS-243
> URL: https://issues.apache.org/jira/browse/QPIDJMS-243
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.20.0
> Environment: Qpid Broker 7.0.0-SNAPSHOT
> Reporter: Alex Rudyy
> Assignee: Timothy Bish
> Priority: Minor
>
> I see the following log issued on failure attempt to establish connection to
> a stopped(not available) broker listed in failover URL
> {noformat}
> 2016-12-30 16:42:24,738 [localhost:5672]] - WARN AmqpProvider
> - Caught problem during update processing: null
> java.lang.NullPointerException
> at
> org.apache.qpid.jms.provider.amqp.AmqpConnection.handleResourceClosure(AmqpConnection.java:124)
> at
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.closeResource(AmqpAbstractResource.java:151)
> at
> org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:257)
> at
> org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:850)
> at
> org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1800(AmqpProvider.java:93)
> at
> org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:784)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The exception does not impact client functionality as client seems continue
> to work as normal. The exception is reported only on trunk. 0.11 client does
> not have this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
