une 24, 2022 10:50 AM
> To: users@activemq.apache.org
> Subject: Re: [External] - Re: How to avoid AMQ229014 TTL "dump" for a
> "patient" Python 3 Stomp Listener
>
> CAUTION: This email originated from outside of the organization. Do not click
> links or op
rites!
From: Robbie Gemmell
Sent: Friday, June 24, 2022 10:50 AM
To: users@activemq.apache.org
Subject: Re: [External] - Re: How to avoid AMQ229014 TTL "dump" for a "patient"
Python 3 Stomp Listener
CAUTION: This email originated from outside of the o
dy=}
>
> 2022-06-24 09:23:06,523 __main__ INFO:
> Processing message with ID:10205 and Subscription:42
>
> Heartbeat timeout: diff_receive=15.000172974017914, time=264585.48758635,
> lastrec=264570.487413376
> 2022-06-24 09:23:36,316 __main__ INFO:
> on_disconnected
>
> 202
Listener
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Thank you Justin. It's just now becoming apparent to me that the heartbeating
mechanism is built into the client connection, i.e., I
have enough to proceed for now.
Thanks again.
Regards,
Rich
From: Timothy Bish
Sent: Thursday, June 23, 2022 10:56 AM
To: users@activemq.apache.org
Subject: Re: [External] - Re: How to avoid AMQ229014 TTL "dump" for a "patient"
Python 3
o the broker every, say, 30 seconds, but
> I'm left wanting for just WHAT that heartbeat call is!
>
> Sorry, kinda frustrated here . . .
> ________________
> From: Justin Bertram
> Sent: Thursday, June 23, 2022 9:50 AM
> To: users@activemq.apache.org
> Subject: [External] - Re: Ho
m left wanting for just WHAT that heartbeat call is!
>
> Sorry, kinda frustrated here . . .
>
> From: Justin Bertram
> Sent: Thursday, June 23, 2022 9:50 AM
> To: users@activemq.apache.org
> Subject: [External] - Re: How to avoid AMQ229014 TTL "
: Timothy Bish
Sent: Thursday, June 23, 2022 10:42 AM
To: users@activemq.apache.org
Subject: Re: [External] - Re: How to avoid AMQ229014 TTL "dump" for a "patient"
Python 3 Stomp Listener
CAUTION: This email originated from outside of the organization. Do not click
links
ldn't give for actual code examples! :p
From: Timothy Bish
Sent: Thursday, June 23, 2022 10:42 AM
To: users@activemq.apache.org
Subject: Re: [External] - Re: How to avoid AMQ229014 TTL "dump" for a "patient"
Python 3 Stomp Listener
CAUTI
vemq.apache.org
Subject: [External] - Re: How to avoid AMQ229014 TTL "dump" for a "patient"
Python 3 Stomp Listener
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
frustrated here . . .
From: Justin Bertram
Sent: Thursday, June 23, 2022 9:50 AM
To: users@activemq.apache.org
Subject: [External] - Re: How to avoid AMQ229014 TTL "dump" for a "patient"
Python 3 Stomp Listener
CAUTION: This email originated from outsid
> Is there a more acceptable way to alert the broker that the listener is
still alive and well but just being patient?
Yes. STOMP already has this via heartbeating [1]. Does your Python client
support heartbeating? If so, are you configuring it?
Justin
[1] https://stomp.github.io/stomp-specific
I migrated my application from Classic to Artemis, and now my listeners are
being summarily disconnected by the broker on a TTL timeout.
My use case is that I have listeners (subscribers) that are launched as a
service and patiently wait (could be for days) for messages to arrive on a
work
13 matches
Mail list logo
