On 29/05/18 20:24, Rob Godfrey wrote:
On Tue, 29 May 2018 at 19:45, akabhishek1 <[email protected]>
wrote:
HI Robbie,
Thanks a lot for details. I am able to reproduce this issue with your
finding, i am facing same idle timeOut issue for every 10m.
As MessageProducer have no internal operation which will tell us that
MessageProducer is active or not. DO we have any library or facility
available which will refresh MessageProducer in every 10m for idle
scenario?
Since the "idling" after 10 minutes is a ServiceBus specific "feature" then
I would not expect any client library (except perhaps for those written by
Microsoft) to handle this scenario.
The problem with the JMS API specifically though, is that there is no
way to be notified that a producer has been closed or even to test
whether it has been closed...
If not available then we have to write some custom logic to handle this
scenario.
Yes - I think the best option here is for you to write your own custom
logic here. You could, for instance, write a wrapper around
MessageProducer that keeps track of the last time a message was sent and if
that time was > 10 minutes ago could close the wrapped MessageProducer and
create a new one.
Does the send() method throw a recognisable error if the underlying
producer link has been detached?
Your solution sounds like a good one for the case in question. More
generally though, JMS users would probably need a way to handle links
closed for less predictable reasons.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
