Hi everyone. I am in a new project, which uses ServiceMix 3.3 deployed in a Tomcat.
Currently I am working on the following requirements: a) A loadlimiter, which counts the size/content-length of requests, that a currently processed and rejects new requests depending on a certain limit. b) A similar protection on TCP/IP level: Limit the maximum number of parallel HTTP-Requests and send TCP/IP Connection refused. c) As the ServiceMix is running inside Tomcat, my first approach was: a) writing a standard servlet.filter and perform filtering on requests going to Tomcat b) configure Tomcats http-connector for requirement ”b”. Unfortunately I realized, that ServiceMix starts it’s own Jetty. Therefore my solution is not working: All relevant requests go straight to Jetty and ignore Tomcat. Is there any recommendation for solving this problem? I am currently considering these solutions: 1) Configure ServiceMix to use the Tomcat instead of Jetty. 2) Deploy the servlet.filter to the embedded Jetty and configure it’s http-connector as required Sadly I have no clue how to do these. Thanks alot! -- View this message in context: http://servicemix.396122.n5.nabble.com/Using-Servlet-filter-and-configure-connector-tp4981491p4981491.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
