On 18/12/2019 12:33 pm, Toralf Lund wrote:
I get the exact behaviour I'm seeing now only in a version that was
deployed about a week ago, and since then, between 60 and 70
session-busy exceptions have been registered. Most of these came from
Session::nextReceiver() or Receiver::fetch(), but exa
+1
Verified checksum
Checked for LICENSE and NOTICE files.
Ran unit tests against newly released Proton 0.30.0. All tests passed.
On Mon, Dec 16, 2019 at 5:46 PM Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC3 as the
> official Qpid Dispatch Ro
On 18/12/2019 12:35, Gordon Sim wrote:
On 18/12/2019 10:42 am, Toralf Lund wrote:
On 18/12/2019 10:40, Gordon Sim wrote:
On 18/12/2019 8:45 am, Toralf Lund wrote:
An additional, more serious issue is that the system has also
locked up a couple of times following an exception during
Sender::se
On 18/12/2019 12:32, Gordon Sim wrote:
On 18/12/2019 10:42 am, Toralf Lund wrote:
On 18/12/2019 10:40, Gordon Sim wrote:
On 18/12/2019 8:45 am, Toralf Lund wrote:
I don't see any signs of connection errors or explicit reopens but
automatic reconnect with a limit has been enabled; the following
On 18/12/2019 11:30, Gordon Sim wrote:
On 18/12/2019 8:45 am, Toralf Lund wrote:
The application became responsive again after running a debug session
to get the above info.
Using pstack to get the stack traces when it hangs might be useful. It
is less likely to interfere with the running and
On 18/12/2019 10:42 am, Toralf Lund wrote:
On 18/12/2019 10:40, Gordon Sim wrote:
On 18/12/2019 8:45 am, Toralf Lund wrote:
An additional, more serious issue is that the system has also locked
up a couple of times following an exception during Sender::send().
Slightly simplified stack trace fr
On 18/12/2019 10:42 am, Toralf Lund wrote:
On 18/12/2019 10:40, Gordon Sim wrote:
On 18/12/2019 8:45 am, Toralf Lund wrote:
I don't see any signs of connection errors or explicit reopens but
automatic reconnect with a limit has been enabled; the following
connect options are used
connecti
+1
I checked things over as follows:
- Verified the signature and checksum files.
- Checked for LICENCE + NOTICE files present in the archive.
- Ran mvn apache-rat:check to verify the source licence headers.
- Built against Proton 0.30.0 and ran the tests.
- Ran the Qpid JMS 0.48.0 HelloWorld exam
On 18/12/2019 10:40, Gordon Sim wrote:
On 18/12/2019 8:45 am, Toralf Lund wrote:
On one of our installations of one of our AMQP 0-10 applications
using the QPid messaging API (in C++), we keep getting exceptions
with the message
session-busy: Session detached by peer
- usually while waiting
On 16/12/2019 10:39 pm, Ganesh Murthy wrote:
Hello All,
Please cast your vote on this thread to release RC3 as the
official Qpid Dispatch Router version 1.10.0.
RC3 of Qpid Dispatch Router version 1.10.0 can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.10.0-
On 18/12/2019 8:45 am, Toralf Lund wrote:
The application became responsive again after running a debug session to
get the above info.
Using pstack to get the stack traces when it hangs might be useful. It
is less likely to interfere with the running and it should let you get a
couple of stac
On 18/12/2019 8:45 am, Toralf Lund wrote:
On one of our installations of one of our AMQP 0-10 applications using
the QPid messaging API (in C++), we keep getting exceptions with the
message
session-busy: Session detached by peer
- usually while waiting for incoming messages, but in some cases
On one of our installations of one of our AMQP 0-10 applications using
the QPid messaging API (in C++), we keep getting exceptions with the message
session-busy: Session detached by peer
- usually while waiting for incoming messages, but in some cases also
when sending them. After resolving so
13 matches
Mail list logo
