On 01/07/2011 12:07, Rohan Kadam wrote:
> I have tries to set this java option in catalane .bat, but no success
>=20
> -Djava.net.preferIPv4Stack=3Dtrue
>=20
> I am using tomcat as a service, so configures the same in Java properti=
es as well. But it is not working.
How are you setting it, exactly?
p
> -----Original Message-----
> From: Pid [mailto:pid@pidster.com]=20
> Sent: Friday, July 01, 2011 4:18 PM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.=
0.14)
>=20
> On 30/06/2011 21:57, Christopher Schultz wrote:
>> Rohan,
>>
>> On 6/30/2011 8:01 AM, Rohan Kadam wrote:
>>> We had recently upgraded tomcat from 5.5.30 to 7.0.14. We were=20
>>> earlier facing problem that tomcat was not able to connect using=20
>>> Static IP address. The fix that we found was adding address =3D=20
>>> "0.0.0.0" in the Connector tag of server.xml in the "conf" directory.=
>>
>> This was likely because your JVM prefers an IPv6 stack, while using an=
>> IPv4 address (0.0.0.0) explicitly causes it to bind to an IPv4 address=
=2E
>>
>> When you say "not able to connect", do you mean that the client=20
>> couldn't reach Tomcat, or that Tomcat couldn't connect to some other s=
erver?
>>
>>> After upgrading tomcat to 7.0.14, we have done the same process, but =
>>> we are not able to connect.
>=20
> Hint: JAVA_OPTS=3D"-Djava.net.preferIPv4Stack=3Dtrue" can be set in s=
etenv.sh|bat
>=20
>=20
> p
>=20
>=20
> "Legal Disclaimer: This electronic message and all contents contain inf=
ormation from Cybage Software Private Limited which may be privileged, co=
nfidential, or otherwise protected from disclosure. The information is in=
tended to be for the addressee(s) only. If you are not an addressee, any =
disclosure, copy, distribution, or use of the contents of this message is=
strictly prohibited. If you have received this electronic message in err=
or please notify the sender by reply e-mail to and destroy the original m=
essage and all copies. Cybage has taken every reasonable precaution to mi=
nimize the risk of malicious content in the mail, but is not liable for a=
ny damage you may sustain as a result of any malicious content in this e-=
mail. You should carry out your own malicious content checks before openi=
ng the e-mail or attachment."=20
> www.cybage.com
|