You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/08 08:40:01 UTC
[jira] [Work logged] (AMQ-6892) Test failing unexpectedly:
CamelVMTransportRoutingTest.testSendReceiveWithCamelRouteIntercepting
[ https://issues.apache.org/jira/browse/AMQ-6892?focusedWorklogId=562206&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562206 ]
ASF GitHub Bot logged work on AMQ-6892:
---------------------------------------
Author: ASF GitHub Bot
Created on: 08/Mar/21 08:39
Start Date: 08/Mar/21 08:39
Worklog Time Spent: 10m
Work Description: lucastetreault commented on pull request #273:
URL: https://github.com/apache/activemq/pull/273#issuecomment-792580413
Can one of the admins verify this patch?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 562206)
Remaining Estimate: 0h
Time Spent: 10m
> Test failing unexpectedly: CamelVMTransportRoutingTest.testSendReceiveWithCamelRouteIntercepting
> ------------------------------------------------------------------------------------------------
>
> Key: AMQ-6892
> URL: https://issues.apache.org/jira/browse/AMQ-6892
> Project: ActiveMQ
> Issue Type: Bug
> Components: Camel
> Affects Versions: 5.16.0
> Environment: Ubuntu, 16.04 LTS
> Reporter: Wing Lam
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When I run the test CamelVMTransportRoutingTest.testSendReceiveWithCamelRouteIntercepting, it passes, but when I run all of the tests in activemq-camel, it fails. I am running this in Intellij.
> It appears the problem is unclosed connections in some of the other tests.
> Changes that fix this can be seen in the pull request linked below.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)