There isn't enough information here to really make a guess as to the
root cause but likely ServiceBus is closing the resources for some
reason such as exceeding some capacity restriction or idle period etc.
This is something you'd need to investigate yourself via client and
server logs as well as perhaps contacting the ServiceBus folks as we
here aren't able to give you insights into that bit.
As usual collecting AMQP frame traces can help to determine when the
session was closed and what the remote indicated in its error condition
supplied at the time of closing (if any was offered).
On 1/27/21 6:57 AM, akabhishek1 wrote:
Hi Team,
We are using Qpid-JMS-Client-56.0 to publish/consume from ServiceBus.
We are getting "javax.jms.IllegalStateException - The MessageProducer is
closed" error.
We reset the Producer whenever we got "The MessageProducer is closed"
error. At this time, Producer and Session, both was closed. I am trying to
find out the reason for closed JMS Session.
Can you please guide us, What are the criteria can trigger to close the JMS
Session? So I can replicate with real enironment.
Regards,
Abhishek Kumar
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Tim Bish
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
