Yes!!! This seems to be the exact issue. I have worked around it by getting
jsonb to do a simple string to object mapping as soon as I've configured it
in my provider. Only then do I allow multiple threads to use it.
On Tue, 26 Feb 2019, 13:26 Jonathan Gallimore,
wrote:
> Hi Paul
>
> Does this
Hi Paul
Does this (from the Johnzon mailing list yesterday):
http://mail-archives.apache.org/mod_mbox/johnzon-dev/201902.mbox/browser
sound similar to your issue?
Regards
Jon
On Tue, Feb 26, 2019 at 12:29 AM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:
> I'd be pretty surprised
I'd be pretty surprised if the ear vs war deployment made a difference, but
you never know... feel free to send your working war sample over, it might
just help us bootstrap something. It would be useful to get the full
guru.jini.arch.impl.json.JsonImpl.toObject and
Hi Daniel,
For the life of me I cannot recreate the issue in a simple project with a
WAR. My project is an EAR with multiple WARS. I will continue trying but in
the meantime wondered if anyone has any clues where to look?
Paul Carter-Brown
Director
Jini Guru
m: +27 (0) 83 442 7179 <+27834427179>
Hi Paul,
could you share a sample project with your issue?
It will help to reproduce and analyze your case.
Thank you.
Em seg, 25 de fev de 2019 às 14:35, Paul Carter-Brown
escreveu:
> Hi,
>
> I'm using Johnzon in TomEE 8.0.0-M2. In some rest calls, I do my own
> marshalling from a string to
Hi,
I'm using Johnzon in TomEE 8.0.0-M2. In some rest calls, I do my own
marshalling from a string to an Object. Intermittently (maybe 50% of the
times I bounce TomEE), after TomEE starts and I send rest requests to the
server, threads lock up and I get timeouts. It appears as though the
threads
