You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Knut Aksnes-NOR <Kn...@jeppesen.com> on 2012/03/27 10:53:59 UTC
Strange behavior of the servlet component
I have a route collection packaged as a jar using 2.9.1 the routes are deployed on Geronimo 2.2.1 and consists of a couple of incoming servlets as well as some seda routes. The routes invoke other seda routes, some ActiveMQ routes as well as one external http server using the http component. Everything is done using ExchangePattern.InOut.
The war file is packaged inside an EAR before being deployed to Geronimo.
The problem is that it seems to be something very strange with the servlet component.
1. It won't work at all unless matchOnUriPrefix=true for the servlet.
2. After reloading my EAR, the first invocation of one of the servlets works as expected. The problem being that from the second invocation onwards all calls seems to be routed to the servlet I invoked first. For me this is totally unexpected behavior and seems like a quite serious bug.
RE: Strange behavior of the servlet component
Posted by Knut Aksnes-NOR <Kn...@jeppesen.com>.
One extra detail. I am using Geronimo with Jetty.
-----Original Message-----
From: Knut Aksnes-NOR [mailto:Knut.Aksnes@jeppesen.com]
Sent: 27. mars 2012 10:54
To: users@camel.apache.org
Subject: Strange behavior of the servlet component
I have a route collection packaged as a jar using 2.9.1 the routes are deployed on Geronimo 2.2.1 and consists of a couple of incoming servlets as well as some seda routes. The routes invoke other seda routes, some ActiveMQ routes as well as one external http server using the http component. Everything is done using ExchangePattern.InOut.
The war file is packaged inside an EAR before being deployed to Geronimo.
The problem is that it seems to be something very strange with the servlet component.
1. It won't work at all unless matchOnUriPrefix=true for the servlet.
2. After reloading my EAR, the first invocation of one of the servlets works as expected. The problem being that from the second invocation onwards all calls seems to be routed to the servlet I invoked first. For me this is totally unexpected behavior and seems like a quite serious bug.