tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <>
Subject Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Date Fri, 01 Jul 2011 11:36:52 GMT
On 01/07/2011 12:07, Rohan Kadam wrote:
> I have tries to set this java option in catalane .bat, but no success
> I am using tomcat as a service, so configures the same in Java properties as well. But
it is not working.

How are you setting it, exactly?


> -----Original Message-----
> From: Pid [] 
> 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)
> 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 
>>> earlier facing problem that tomcat was not able to connect using 
>>> Static IP address. The fix that we found was adding address = 
>>> "" 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 ( explicitly causes it to bind to an IPv4 address.
>> When you say "not able to connect", do you mean that the client 
>> couldn't reach Tomcat, or that Tomcat couldn't connect to some other server?
>>> After upgrading tomcat to 7.0.14, we have done the same process, but 
>>> we are not able to connect.
> Hint:  JAVA_OPTS=""  can be set in|bat
> p
> "Legal Disclaimer: This electronic message and all contents contain information from
Cybage Software Private Limited which may be privileged, confidential, or otherwise protected
from disclosure. The information is intended 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 error please notify the
sender by reply e-mail to and destroy the original message and all copies. Cybage has taken
every reasonable precaution to minimize the risk of malicious content in the mail, but is
not liable for any 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 opening the e-mail or attachment."


View raw message