owners@jersey.java.net

Re: Jersey 2.0 and JBoss 7

From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Wed, 31 Oct 2012 19:48:17 +0100

There seems to be some weird processing happening on the JBoss side. I do not understand what is it trying to do. It seems it has a problem with registration of Jersey javax.servlet.AsyncListener anonymous class implementation. But really not sure why. I don't see us doing anything that would violate standard Servlet spec.

You may need to send your question to JBoss guys... or switch to GlassFish or WebLogic :)

Marek

On Oct 29, 2012, at 10:29 PM, j0naht_at_yahoo.com wrote:

> Hey guys,
>
> I saw your presentation of jersey 2.0 at JavaOne and was really
> interested in the Async feature to get a performance boost in one of
> our jersey services. I know that version 2.0 is still a work in
> progress at this point, but I thought it wouldn't hurt to ask and see
> if you guys had any ideas of a work around for this issue I'm seeing
> with JBoss and hoping that it may be something very simple. I have our
> service working great now in our maven-jetty development environment
> using the Async annotation and seeing about 50 times faster
> performance. Now I'm testing it out in the production environment which
> is JBoss 7. I thought this would work because it supports
> javax.servlet 3.0, but I am seeing this error on war deployment:
>
> 16:02:49.027 [MSC service thread 1-2] WARN org.jboss.as.ee -
> JBAS011006: Not installing optional component
> org.glassfish.jersey.servlet.async.AsyncContextDelegateProviderImpl$Ext
> ensionImpl$1 due to exception:
> org.jboss.as.server.deployment.DeploymentUnitProcessingException:
> JBAS011054: Could not find default constructor for class
> org.glassfish.jersey.servlet.async.AsyncContextDelegateProviderImpl$Ext
> ensionImpl$1
> at
> org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigur
> ator.configure(ComponentDescription.java:606)
> at
> org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.depl
> oy(EEModuleConfigurationProcessor.java:81)
> at
> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(Deploym
> entUnitPhaseService.java:113)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Serv
> iceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContro
> llerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source) [rt.jar:1.7.0_05]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source) [rt.jar:1.7.0_05]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_05]
>
> I am not sure why JBoss is trying to construct this class or if it
> should be doing this. I may have to ask the JBoss experts out there if
> you guys don't have any ideas. My impression was that Jersey 2.0 would
> work in any Java server container. Thanks in advance for your time!
>
> Jonah