[
https://issues.apache.org/jira/browse/ARTEMIS-2327?focusedWorklogId=235794&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235794
]
ASF GitHub Bot logged work on ARTEMIS-2327:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/19 13:25
Start Date: 01/May/19 13:25
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #2655:
ARTEMIS-2327 ExceptionListener invoked when connection level exception
URL: https://github.com/apache/activemq-artemis/pull/2655#discussion_r280070256
##########
File path:
artemis-core-client/src/main/java/org/apache/activemq/artemis/core/protocol/core/impl/ChannelImpl.java
##########
@@ -451,7 +451,9 @@ public Packet sendBlocking(final Packet packet,
}
if (response == null) {
- throw
ActiveMQClientMessageBundle.BUNDLE.timedOutSendingPacket(connection.getBlockingCallTimeout(),
packet.getType());
+ ActiveMQException e =
ActiveMQClientMessageBundle.BUNDLE.timedOutSendingPacket(connection.getBlockingCallTimeout(),
packet.getType());
+ connection.fail(e);
Review comment:
@michaelandrepearce I ran the 2 hours:40 min test with on a jenkins server I
have:
```
mvn test -Ptests
```
apparently there are tests hunging because of this.
I couldn't figure out what test is it.. as the build generate zillions of:
```
med out after waiting 2,000 ms for response when sending packet 32
[code=CONNECTION_TIMEDOUT]
[main] 09:19:18,204 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
2019-05-01 09:19:18,204 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
2019-05-01 09:19:18,204 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
[main] 09:19:20,210 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
2019-05-01 09:19:20,210 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
2019-05-01 09:19:20,210 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
[main] 09:19:22,216 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014: Timed out after
waiting 2,000 ms for response when sending packet 32 [code=CONNECTION_TIMEDOUT]
2019-05-01 09:19:22,216 WARN [org.apache.activemq.artemis.core.client]
AMQ212037: Connection failure has been detected: AMQ219014:
```
I am taking a break today.. I can take a look on more details later today /
tomorrow morning.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 235794)
Time Spent: 7h 10m (was: 7h)
> JMS Connection ExceptionListener not invoked when
> ActiveMQConnectionTimedOutException occurs on sendPacket
> ----------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2327
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2327
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Michael Andre Pearce
> Priority: Major
> Time Spent: 7h 10m
> Remaining Estimate: 0h
>
> When a connection level exception occurs it seems in one case, whilst the
> exception is returned to calling code, exception listeners set at the
> connection are not being invoked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
