On 03.01.2017 01:33, Markus Koschany wrote:
> On Wed, 14 Dec 2016 11:13:59 +0000 =?iso-8859-1?Q?Sch=F6ke=2C_Karsten?=
> <karsten.scho...@geobasis-bb.de> wrote:
>> Hi,
>> the problem is, that tomcat7 don't use the proxy.
>> The tomcat6 use this option on the same server...
>> tomcat7/javaopts: -Djava.awt.headless=true -Xmx4096m -XX:+UseConcMarkSweepGC 
>> -XX:MaxPermSize=1024m -XX:+UseParNewGC -XX:MaxNewSize=512m -XX:NewSize=512m 
>> -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 -XX:+UseTLAB 
>> -XX:+CMSClassUnloadingEnabled -Dhttp.proxySet=true 
>> -Dhttp.proxyHost=10.xxx.xx.xx -Dhttp.proxyPort=3128 
>> -Dhttps.proxyHost=10.xxx.xx.xx -Dhttps.proxyPort=3128 
>> -Dhttp.nonProxyHosts=*.domain.local
>> Tomcat Applications can't connect services over the proxy on Dhttp.proxyHost 
>> on Dhttp.proxyPort
> Hi,
> I still don't understand the actual issue. Were you able to resolve it
> in the meantime. Was it just a configuration issue? Do you use
> /etc/default/tomcat7 for passing these values or another method?

I have discussed this issue with Karsten via private email. He confirmed
to me that the version of Tomcat7 in wheezy-backports behaves
identically. Hence I think we can rule out that the recent security
updates are the root cause for this issue.

I haven't found any information about a behavioral change from Tomcat 6
to Tomcat 7 in this regard. Has anyone else an idea how we could narrow
the issue down?



Attachment: signature.asc
Description: OpenPGP digital signature

This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to