activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sid <hiremat...@gmail.com>
Subject Fixing following issue:- WARN | Transport Connection to: blockingQueue_1942843618 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long
Date Thu, 18 Dec 2014 09:14:45 GMT
Fixing following issue:- WARN  | Transport Connection to:
blockingQueue_1942843618 failed:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long

Made following change:-
activemq.xml:-
<transportConnector
uri="${connection.uri}?wireFormat.maxInactivityDuration=0&amp;keepAlive=true&amp;wireFormat.maxFrameSize=104857600"/>


Client broker url:-
failover:(nio://127.0.0.1:61616?wireFormat.maxInactivityDuration=0&keepAlive=true&wireFormat.maxFrameSize=104857600)?jms.blobTransferPolicy.defaultUploadUrl=http://127.0.0.1:8161/fileserver/&initialReconnectDelay=10000&useExponentialBackOff=false&randomize=false

Please let me know if this is good to go on live.

Thanks,
Sid



--
View this message in context: http://activemq.2283324.n4.nabble.com/Fixing-following-issue-WARN-Transport-Connection-to-blockingQueue-1942843618-failed-org-apache-activg-tp4689070.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message