Hello Richard,
It's really easy to reproduce.
Just this class to be deploy in a war:
@Stateless
@Path("v1/notifications")
public class NotificationResource {
public static final String QUEUE_NAME = "jms/myQueue";
@Resource(name = QUEUE_NAME)
private Queue messageQueue;
Hello Jonathan,
As I have mentioned, we see the issue in TomEE MP but not in TomEE Plus !
So I did a comparison of the 2 flavors: lib + conf
The only difference I have seen is in the system.properties where I have the
line below in TomEE MP and not this one in TomEE Plus !
This could explain.
Awesome, thanks for the feedback. We'd still want to fix the actual issue.
If you get time, if you can file a JIRA, that would be great.
Jon
On Tue, Feb 11, 2020 at 6:01 PM COURTAULT Francois <
francois.courta...@thalesgroup.com> wrote:
> Hello Jonathan,
>
> We did the test (remove
Hello Jonathan,
We did the test (remove tomee.mp.scan = all entry in system.properties) with
TomEE MP and it solves the issue we have: a lot of opentracing objects created.
We don't have this issue (a lot of opentracing objects created) in TomEE Plus
because this entry doesn't exist in
Hi All,
I'm running service that is using Deltaspike + Primefaces in TomEE (7.0.6)
quite successfully, but experiencing some issue when trying to add Omnifaces
components to the page (full stacktrace below). Note, adding Omnifaces
websocket (o:socket) works pretty good, but I had to register
