>> André Warnier wrote: >> Just to complete your report : >> - is the JVM used in both cases exactly the same ? >> - are either one of the Tomcats (or both) using the "native APR" library ? >> (although I have no idea really if this is relevant or not when a >> webapp makes its own connections)
>Could the app contain code which uses a specific proxy? >p The same Sun 1.6.29 jvm is being used in both instances, and native APR is not involved here. I don't believe app code is to blame as the proxy chosen is not a normal one for our environments. It looks more like it is being "discovered" to me. I have used CXF code to specifically set the proxy, and nonProxyHosts. If I do this, if the web service host defined in nonProxyHosts it will fall back through the "alien" proxy. i.e. For Tomcat: 1. No known proxy set: Client IP at the web service appears as proxy A 2. CXF code to set to Proxy B: Client IP is proxy B 3. CXF code to set to Proxy B and App Server hostname in nonProxyhosts: Client IP is proxy A 4. Tomcat jvm -Dhttp.proxy=proxyA and -Dhttp.nonProxyHosts=appserver: Client IP is app server (desired outcome) Whereas the same code running on the console as the tomcat user never uses proxy A, unless specifically asked to in CXF code. I would like to know where that proxy is coming from. Dale --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
