On Wed, 2015-06-10 at 14:18 +, Kritikos, Alex wrote:
> Hi Alan,
>
> thanks for your response. We also use an engine per connection
> however there are different read and write threads interacting with
> it and the issues only occur under load.
> I guess we should try to create a repro case.
Hi Alan,
thanks for your response. We also use an engine per connection however there
are different read and write threads interacting with it and the issues only
occur under load.
I guess we should try to create a repro case.
Thanks,
Alex Kritikos
Software AG
On 10 Jun 2015, at 16:50, aconway
On 06/10/2015 10:18 AM, Kritikos, Alex wrote:
> Hi Alan,
>
> thanks for your response. We also use an engine per connection however there
> are different read and write threads interacting with it and the issues only
> occur under load.
> I guess we should try to create a repro case.
>
> Thanks,
On Wed, 2015-06-10 at 09:34 +, Kritikos, Alex wrote:
> [Resending as it ended up in the wrong thread]
>
> Hi all,
>
> is the proton-j engine meant to be thread safe?
The C engine is definitely NOT meant to be thread safe. Unless you have
found an explicit written declaration that the java en
[Resending as it ended up in the wrong thread]
Hi all,
is the proton-j engine meant to be thread safe?
We have been experiencing some sporadic issues where under load, the engine
sends callbacks to registered handlers with null as the event. We do not have a
standalone repro case yet but just w
Hi all,
is the proton-j engine meant to be thread safe?
We have been experiencing some sporadic issues where under load, the engine
sends callbacks to registered handlers with null as the event. We do not have a
standalone repro case yet but just wondered what other people’s experience is
as we