Re: qpid-jms-client-0.45 --> Suspected deadlocked threads - owned by JmsSession delivery dispatcher

2020-12-11 Thread akabhishek1
HI Robbie, Thanks a lot for quick feedback. I will raise this with Microsoft. Regards, Abhi -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apac

Re: qpid-jms-client-0.45 --> Suspected deadlocked threads - owned by JmsSession delivery dispatcher

2020-12-11 Thread Robbie Gemmell
If I understand your description and code correctly, you create 4 consumers (each on their own session) per 'Service Bus subscription', using 2 connections, each of which are used for 2 different subs. You then did something on the server side for a single sub and expected its related 4 consumers t

Re: [External] Re: qpid::messaging::Sender::send() sometimes takes much longer than expected (in C++)

2020-12-11 Thread Gordon Sim
On 11/12/2020 08:55, Toralf Lund wrote: I guess I'll just have to keep trying various changes etc. Although I'm a bit out of ideas just now. Would capturing tcp dumps on the host in question by feasible? (You could output N files and overwrite oldest in a ring).

Re: [External] Re: qpid::messaging::Sender::send() sometimes takes much longer than expected (in C++)

2020-12-11 Thread Toralf Lund
On 10/12/2020 22:30, Gordon Sim wrote: On 10/12/2020 16:04, Toralf Lund wrote: Where and when exactly are the heartbeats sent? The interval is negotiated at connection time. I believe the default for the 0-10 qpid::messaging client is 0, i.e. heartbeats disabled, so I suspect your client has