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

ASF subversion and git services commented on AMQ-6463:
------------------------------------------------------

Commit 74a5381b9a79d2ee708345743bb128d06bd9d80b in activemq's branch 
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=74a5381 ]

AMQ-6463 - provide connection to scheduler context in case of deferred send or 
error


> NPE on scheduler send via blocked waiting for space task
> --------------------------------------------------------
>
>                 Key: AMQ-6463
>                 URL: https://issues.apache.org/jira/browse/AMQ-6463
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Job Scheduler
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.15.0
>
>
> The response cannot be processed b/c there is no connection in the context 
> provide by the scheduler plugin.
> The reply is lost so there is no message loss in this case, just a worrying 
> stack trace.
> {code}
> ERROR | Error in thread 'ActiveMQ BrokerService[ILP-B] Task-18534'
> java.lang.NullPointerException
> at 
> org.apache.activemq.broker.region.Queue$4.run(Queue.java:688)[activemq-broker-5.14.0.jar:5.14.0]
> at 
> org.apache.activemq.broker.region.Queue.iterate(Queue.java:1551)[activemq-broker-5.14.0.jar:5.14.0]
> at 
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)[activemq-client-5.14.0.jar:5.14.0]
> at 
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)[activemq-client-5.14.0.jar:5.14.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_51]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744)[:1.7.0_51]{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to