You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com> on 2015/06/30 19:27:50 UTC
Jetty upgrade on recent commit
Hi, Dan.
Latest commit made that upgrades Jetty to 9.2 introduces a issue to those using the generated WAR file “as is" on Tomcat.
It fails with the following exception:
GRAVE: Error during ServletContainerInitializer processing
javax.servlet.ServletException: Not running on Jetty, JSR-356 support unavailable
at org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:146)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5513)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecuto
Simply removing the " jetty-all-9.2.11.v20150529.jar” jar from the WAR avoids it.
On [1] seems there’s a way to avoid it by defining a property the WebAppContext.
Might it be better managed through Maven ?
HTH,
Oscar
[1] http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html <http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html>
Re: Jetty upgrade on recent commit
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
Many thanks, Dan.
We will try this.
Cheers,
Oscar
> El 7/7/2015, a las 9:00, Dan Haywood <da...@haywood-associates.co.uk> escribió:
>
> (I just posted a similar message to users@i.a.o)
> ~~~~~~~~~~~~
>
>
> OK, I believe I have this issue (if using 1.9.0-SNAPSHOT, of not being able
> to deploy the built WAR to Tomcat) fixed.
>
> It requires an adjustment to your webapp's pom.xml file; I've updated the
> migration notes [1] (for existing code) and the archetype (for new)
>
> Any probs, let me know.
> Thx
> Dan
>
> [1]
> http://isis.apache.org/migration-notes.html#_migration-notes_1.8.0-to-1.9.0_war-packaging
>
> On 1 July 2015 at 09:05, Dan Haywood <da...@haywood-associates.co.uk> wrote:
>
>> Thanks for digging into this Oscar... I'll look at tomorrow.
>>
>> Cheers
>> Dan
>>
>>
>>
>> On 30 June 2015 at 18:27, GESCONSULTOR - Óscar Bou <o.bou@gesconsultor.com
>>> wrote:
>>
>>> Hi, Dan.
>>>
>>> Latest commit made that upgrades Jetty to 9.2 introduces a issue to those
>>> using the generated WAR file “as is" on Tomcat.
>>>
>>> It fails with the following exception:
>>>
>>> GRAVE: Error during ServletContainerInitializer processing
>>> javax.servlet.ServletException: Not running on Jetty, JSR-356 support
>>> unavailable
>>> at
>>> org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:146)
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5513)
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> at
>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>>> at
>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>>> at
>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
>>> at
>>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
>>> at
>>> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecuto
>>>
>>>
>>> Simply removing the " jetty-all-9.2.11.v20150529.jar” jar from the WAR
>>> avoids it.
>>>
>>> On [1] seems there’s a way to avoid it by defining a property the
>>> WebAppContext.
>>>
>>> Might it be better managed through Maven ?
>>>
>>>
>>> HTH,
>>>
>>> Oscar
>>>
>>> [1] http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html <
>>> http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html>
>>
>>
>>
Óscar Bou Bou
Responsable de Producto
Auditor Jefe de Certificación ISO 27001 en BSI
CISA, CRISC, APMG ISO 20000, ITIL-F
902 900 231 / 620 267 520
http://www.twitter.com/oscarbou <http://www.twitter.com/oscarbou>
http://es.linkedin.com/in/oscarbou <http://es.linkedin.com/in/oscarbou>
http://www.GesConsultor.com <http://www.gesconsultor.com/>
Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen información reservada que no puede ser difundida. Si usted ha recibido este correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al remitente mediante reenvío a su dirección electrónica; no deberá copiar el mensaje ni divulgar su contenido a ninguna persona.
Su dirección de correo electrónico junto a sus datos personales constan en un fichero titularidad de Gesdatos Software, S.L. cuya finalidad es la de mantener el contacto con Ud. Si quiere saber de qué información disponemos de Ud., modificarla, y en su caso, cancelarla, puede hacerlo enviando un escrito al efecto, acompañado de una fotocopia de su D.N.I. a la siguiente dirección: Gesdatos Software, S.L. , Paseo de la Castellana, 153 bajo - 28046 (Madrid), y Avda. Cortes Valencianas num. 50, 1ºC - 46015 (Valencia). Asimismo, es su responsabilidad comprobar que este mensaje o sus archivos adjuntos no contengan virus informáticos, y en caso que los tuvieran eliminarlos.
Re: Jetty upgrade on recent commit
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
(I just posted a similar message to users@i.a.o)
~~~~~~~~~~~~
OK, I believe I have this issue (if using 1.9.0-SNAPSHOT, of not being able
to deploy the built WAR to Tomcat) fixed.
It requires an adjustment to your webapp's pom.xml file; I've updated the
migration notes [1] (for existing code) and the archetype (for new)
Any probs, let me know.
Thx
Dan
[1]
http://isis.apache.org/migration-notes.html#_migration-notes_1.8.0-to-1.9.0_war-packaging
On 1 July 2015 at 09:05, Dan Haywood <da...@haywood-associates.co.uk> wrote:
> Thanks for digging into this Oscar... I'll look at tomorrow.
>
> Cheers
> Dan
>
>
>
> On 30 June 2015 at 18:27, GESCONSULTOR - Óscar Bou <o.bou@gesconsultor.com
> > wrote:
>
>> Hi, Dan.
>>
>> Latest commit made that upgrades Jetty to 9.2 introduces a issue to those
>> using the generated WAR file “as is" on Tomcat.
>>
>> It fails with the following exception:
>>
>> GRAVE: Error during ServletContainerInitializer processing
>> javax.servlet.ServletException: Not running on Jetty, JSR-356 support
>> unavailable
>> at
>> org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:146)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5513)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
>> at
>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
>> at
>> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at java.util.concurrent.ThreadPoolExecuto
>>
>>
>> Simply removing the " jetty-all-9.2.11.v20150529.jar” jar from the WAR
>> avoids it.
>>
>> On [1] seems there’s a way to avoid it by defining a property the
>> WebAppContext.
>>
>> Might it be better managed through Maven ?
>>
>>
>> HTH,
>>
>> Oscar
>>
>> [1] http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html <
>> http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html>
>
>
>
Re: Jetty upgrade on recent commit
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Thanks for digging into this Oscar... I'll look at tomorrow.
Cheers
Dan
On 30 June 2015 at 18:27, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>
wrote:
> Hi, Dan.
>
> Latest commit made that upgrades Jetty to 9.2 introduces a issue to those
> using the generated WAR file “as is" on Tomcat.
>
> It fails with the following exception:
>
> GRAVE: Error during ServletContainerInitializer processing
> javax.servlet.ServletException: Not running on Jetty, JSR-356 support
> unavailable
> at
> org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:146)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5513)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
> at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecuto
>
>
> Simply removing the " jetty-all-9.2.11.v20150529.jar” jar from the WAR
> avoids it.
>
> On [1] seems there’s a way to avoid it by defining a property the
> WebAppContext.
>
> Might it be better managed through Maven ?
>
>
> HTH,
>
> Oscar
>
> [1] http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html <
> http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html>