Re: Not running on Jetty, JSR-356 support unavailable

2019-12-06 Thread Tim Bain
So we're repackaging com.sun.xml classes in the ActiveMQ JARs? Are you using activemq-all.jar by any chance? If so, please switch to using the individual JARs and see if that solves the problem; activemq-all.jar is intended as a quick-start for standalone use, but anytime that users find that they

Re: Not running on Jetty, JSR-356 support unavailable

2019-12-02 Thread Naveen Kumar
Hi Tim, Thank you for the suggestion. I tried using TCP transport in place of HTTP and now I get another problem: SEVERE [main] com.sun.xml.ws.transport.http.servlet.WSServletContextListener.parseAdaptersAndCreateDelegate WSSERVLET11: failed to parse runtime descriptor:

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-29 Thread Tim Bain
In the short term, one option would be to simply not include the Jetty JAR in the ActiveMQ classpath. I'd expect you might lose access to the web console and possibly also to the HTTP transport (I'm not sure if that relies on Jetty, but it wouldn't surprise me if it did), but if you could live

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-28 Thread Naveen Kumar
Hi JB, For a test, I just placed the jetty-all jar in tomcat 9 lib and server start up reports the same error. I did not keep activemq or any other jar. Thanks Naveen -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-28 Thread Jean-Baptiste Onofré
Hi, I don't think the conflict is related to jetty-all use. Let me try to reproduce it first. But clearly, it's related to the fact you are embedding ActiveMQ in Tomcat. Regards JB On 29/11/2019 07:56, Naveen Kumar wrote: > Hi JB, > > Thanks for the quick response. Is there any way I can fix

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-28 Thread Naveen Kumar
Hi JB, Thanks for the quick response. Is there any way I can fix the existing problem of JSR-356 conflicts with tomcat ? I can see something related to this was mentioned here http://activemq.apache.org/tomcat.html and https://issues.apache.org/jira/browse/AMQ-6154 But somehow it didn't help me.

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-28 Thread Jean-Baptiste Onofré
Hi, ActiveMQ 5.15.11 uses Jetty 9.4.22, using jetty-all artifact. It's just fine for ActiveMQ standalone. Anyway, I will improve (mostly to reduce the Jetty deps volume). If you use ActiveMQ in Karaf, you don't have the issue as Jetty artifacts are already provided by Karaf. I created

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-28 Thread Naveen Kumar
As per the below post at Jetty, the jar jetty-all should not be used by any other projects. https://www.eclipse.org/lists/jetty-users/msg06030.html Can someone please help to confirm if my understanding is correct that activemq-all-5.15.10.jar has a dependency on

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-22 Thread Naveen Kumar
Hi JB, I am starting it from code using brokerservice. Thanks Naveen -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-22 Thread Jean-Baptiste Onofré
have current setup as Tomcat 9 + ActiveMQ 5.12 + jetty-all-8.1. > I want to upgrade it as Tomcat 9 + ActiveMQ 5.15 + jetty-all-9.4. > > After doing the changes when I try to start tomcat, it gives me below error: > > javax.servlet.ServletException: Not running on Je

Not running on Jetty, JSR-356 support unavailable

2019-11-22 Thread Naveen Kumar
, it gives me below error: javax.servlet.ServletException: Not running on Jetty, JSR-356 support unavailable at org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:200