activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: 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 16:48:07 GMT
Setting wireFormat.maxInactivityDuration=0 means you'll never detect that a
client has disappeared without closing the TCP socket cleanly; I'd be very
hesitant about making that change unless you actually need to.  If you're
just trying to avoid getting those lines in your logs, I'm not sure that's
a tradeoff that's worth it.

On Thu, Dec 18, 2014 at 2:14 AM, Sid <hiremath47@gmail.com> wrote:
>
> 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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message