You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rohan Kadam <ro...@cybage.com> on 2011/06/30 14:01:12 UTC
Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Hi All,
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 = "0.0.0.0" in the Connector tag of server.xml in the "conf" directory.
After upgrading tomcat to 7.0.14, we have done the same process, but we are
not able to connect.
The OS we found these issues are Win XP, Win 2008.
Please suggest.
Thanks,
Rohan Kadam.
"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."
www.cybage.com
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hi,
Please find answers to your question.
1. What exactly is "not able"? Do you have a stacktrace?
Ans: We are trying to connect tomcat to some static IP. When trying to connect it, we are not able to connect it. Yes the port value is right. And the tomcat is up. The problem occurs when we try to connect our application with one of the static IP. All the other pages we are able to navigate properly.
2. What exactly connector is being used?
["http-apr-/0.0.0.0-7070"-exec-8] ERROR rcl.HttpHelper - for a PUT, the response code is - 401 response message -- Unauthorized
3. "we have done the same process" means you are trying to use "0.0.0.0"
like you did with 5.5 and now it fails?
Ans: Yes
Please let me know, if more information is required.
Thanks,
Rohan Kadam.
-----Original Message-----
From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Sent: Saturday, July 02, 2011 2:08 AM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
2011/6/30 Rohan Kadam <ro...@cybage.com>:
> Hi All,
>
> 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 = "0.0.0.0" in the
> Connector tag of server.xml in the "conf" directory.
1) What exactly is "not able"? Do you have a stacktrace?
Maybe some other process already uses that port number? Was the value for address a correct one?
> <Connector port="7070" maxHttpHeaderSize="8192"
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> connectionTimeout="20000" disableUploadTimeout="true"
> address="0.0.0.0" />
2) What exactly connector is being used?
In your configuration Tomcat autoselects between two:
"Http11Protocol" or "Http11AprProtocol"
- which one is actually used is mentioned in the logs.
>
> After upgrading tomcat to 7.0.14, we have done the same process, but
> we are not able to connect.
>
"we have done the same process" means you are trying to use "0.0.0.0"
like you did with 5.5 and now it fails? (or that you tried your proper network address and failed with that, but 0.0.0.0 works)?
>
> The OS we found these issues are Win XP, Win 2008.
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hello All,
Your help for this would be appreciable. Please let me know, if more information is required on the same.
-----Original Message-----
From: Rohan Kadam
Sent: Monday, July 04, 2011 10:09 AM
To: Tomcat Users List
Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Hi,
Please find answers to your question.
1. What exactly is "not able"? Do you have a stacktrace?
Ans: We are trying to connect tomcat to some static IP. When trying to connect it, we are not able to connect it. Yes the port value is right. And the tomcat is up. The problem occurs when we try to connect our application with one of the static IP. All the other pages we are able to navigate properly.
2. What exactly connector is being used?
["http-apr-/0.0.0.0-7070"-exec-8] ERROR rcl.HttpHelper - for a PUT, the response code is - 401 response message -- Unauthorized
3. "we have done the same process" means you are trying to use "0.0.0.0"
like you did with 5.5 and now it fails?
Ans: Yes
Please let me know, if more information is required.
Thanks,
Rohan Kadam.
-----Original Message-----
From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Sent: Saturday, July 02, 2011 2:08 AM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
2011/6/30 Rohan Kadam <ro...@cybage.com>:
> Hi All,
>
> 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 = "0.0.0.0" in the
> Connector tag of server.xml in the "conf" directory.
1) What exactly is "not able"? Do you have a stacktrace?
Maybe some other process already uses that port number? Was the value for address a correct one?
> <Connector port="7070" maxHttpHeaderSize="8192"
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> connectionTimeout="20000" disableUploadTimeout="true"
> address="0.0.0.0" />
2) What exactly connector is being used?
In your configuration Tomcat autoselects between two:
"Http11Protocol" or "Http11AprProtocol"
- which one is actually used is mentioned in the logs.
>
> After upgrading tomcat to 7.0.14, we have done the same process, but
> we are not able to connect.
>
"we have done the same process" means you are trying to use "0.0.0.0"
like you did with 5.5 and now it fails? (or that you tried your proper network address and failed with that, but 0.0.0.0 works)?
>
> The OS we found these issues are Win XP, Win 2008.
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/6/30 Rohan Kadam <ro...@cybage.com>:
> Hi All,
>
> 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 = "0.0.0.0" in the Connector tag of server.xml in the "conf" directory.
1) What exactly is "not able"? Do you have a stacktrace?
Maybe some other process already uses that port number? Was the value
for address a correct one?
> <Connector port="7070" maxHttpHeaderSize="8192"
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> connectionTimeout="20000" disableUploadTimeout="true" address="0.0.0.0" />
2) What exactly connector is being used?
In your configuration Tomcat autoselects between two:
"Http11Protocol" or "Http11AprProtocol"
- which one is actually used is mentioned in the logs.
>
> After upgrading tomcat to 7.0.14, we have done the same process, but we are
> not able to connect.
>
"we have done the same process" means you are trying to use "0.0.0.0"
like you did with 5.5 and now it fails? (or that you tried your proper
network address and failed with that, but 0.0.0.0 works)?
>
> The OS we found these issues are Win XP, Win 2008.
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by André Warnier <aw...@ice-sa.com>.
Caldarale, Charles R wrote:
>> From: Rohan Kadam [mailto:rohanka@cybage.com]
>> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
>> I tried again. And still not successful, please find the stack trace below -
>
>> INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
>> Jul 13, 2011 12:10:36 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
>> INFO: Retrying request
>> java.net.ConnectException: Connection refused: connect
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
> ...
>> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
>> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
>> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
>> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
>
> Note that this has _nothing_ to do with Tomcat. Contrary to your subject line, it's not Tomcat that is unable to connect to some external server, it's your webapp, in particular code in:
>
> com.ultimatetech.console.core.presentation.action.CoreAction
>
Unless the external webserver to which this web application is trying to connect, is also
a Tomcat server, and the <Connector> shown was the one of that webserver (C in my previous
message). This is what I was trying to confirm (or not), because Rohan's communications
so far were not very clear in that respect.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Rohan Kadam [mailto:rohanka@cybage.com]
> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
> I tried again. And still not successful, please find the stack trace below -
> INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
> Jul 13, 2011 12:10:36 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
> INFO: Retrying request
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
...
> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
Note that this has _nothing_ to do with Tomcat. Contrary to your subject line, it's not Tomcat that is unable to connect to some external server, it's your webapp, in particular code in:
com.ultimatetech.console.core.presentation.action.CoreAction
There's nothing Tomcat can do to overcome bugs in your code.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by André Warnier <aw...@ice-sa.com>.
Rohan Kadam wrote:
> Hi André,
>
> Yes, whatever your understanding is correct. And also the connector tag is inside of Tomcat B.
Ok, then Charles' earlier message was correct, and the problem has nothing to do with
Tomcat per se.
Your web application A makes its own TCP connection to webserver C, using the Apache
httpclient. It does not use any of the Tomcat network code for that.
(In particular, it does not use the Tomcat <Connector>).
It would be the same if your web application A was a stand-alone Java application, running
outside of Tomcat.
It is a mystery why, in your previous installation, changing the Tomcat <Connector>
settings was changing the behaviour, but it has nothing to do with the issue you are
dealing with now, as far as I can see.
What you should maybe try :
Outside of Tomcat, from a console on the same host as Tomcat B, try to run a console
application to connect to the URL on server C.
For example, use "wget" or "curl", with the same target URL as what you used with the
browser. Maybe the Tomcat host simply cannot access server C ?
>
> Thanks.
>
> -----Original Message-----
> From: André Warnier [mailto:aw@ice-sa.com]
> Sent: Wednesday, July 13, 2011 4:52 PM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
> Rohan Kadam wrote:
>> I really apologize for the confusion created.
>>
>> We are having an application, which is deployed on tomcat. Rather we are shipping the application with tomcat. After extraction (complete installation), the application is placed under the webapps directory.
>>
>> The logs that I have shared is from the console, while debugging the application.
>
> Ok, so I understand that it is your web application A, running inside your Tomcat B, which tries to access another webserver C. And application A, to connect to webserver C, is using a httpclient object for that.
> Right ?
>
>> To summarize more, we were facing a similar kind of problem in an
>> earlier version of tomcat when we upgraded it from 5.5.26 to 5.5.30
>> (We were able to access the link through browser,
>
> What link to where ?
> Do you mean that the browser (D) can connect directly to webserver C ?
> But that when application A tries to connect to webserver C, you have the error below ?
> (java.net.ConnectException: Connection refused: connect..)
>
> but not through application). To solve this issue, we modified the connector tag in the server.xml file.
>> <Connector port="7070" maxHttpHeaderSize="8192"
>> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>> enableLookups="false" redirectPort="8443" acceptCount="100"
>> connectionTimeout="20000"
>> disableUploadTimeout="true" address="0.0.0.0" />
>>
>
> Still to make things clear : is this <Connector> inside of Tomcat B, or is it the connector of the other webserver C ?
>
>> As, it can be seen from above we have added address="0.0.0.0" in the connector tag, by doing so we were able to connect.
>>
>> Now, as per the new requirement, we are upgrading our tomcat from 5.5.30 to 7.0.14(Since the folder structure is changed, we are shipping the fresh copy of tomcat). We have modified the connector tag as we have done for 5.5.30, but still no success. Please let me know if I am missing something or you want more information for the same.
>>
>> Thanks.
>>
>> -----Original Message-----
>> From: André Warnier [mailto:aw@ice-sa.com]
>> Sent: Wednesday, July 13, 2011 3:12 PM
>> To: Tomcat Users List
>> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version :
>> 7.0.14)
>>
>> Rohan,
>>
>> what you have never clearly explained until now in this rather long thread, is what you are exactly trying to do.
>>
>> Is it :
>>
>> a) an external application written in Java, which is trying to connect to Tomcat ?
>> (and the log lines below are from the logfile of that application)
>>
>> OR
>>
>> b) is it a webapp /within Tomcat/ which is trying to connect to some other server ?
>> (and the log lines below are from a Tomcat logfile)
>>
>> Then, when you have answered the above, can you show us exactly which parameters you are using for the org.apache.commons.httpclient connection method, to set up this connection ?
>> (host, port, URL, whatever)
>>
>>
>>
>> Rohan Kadam wrote:
>>> Hi All,
>>>
>>> I tried again. And still not successful, please find the stack trace
>>> below -
>>>
>>> INFO: I/O exception (java.net.ConnectException) caught when
>>> processing request: Connection refused: connect Jul 13, 2011 12:10:36
>>> PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
>>> INFO: Retrying request
>>> java.net.ConnectException: Connection refused: connect
>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>> at java.net.PlainSocketImpl.doConnect(Unknown Source)
>>> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>>> at java.net.PlainSocketImpl.connect(Unknown Source)
>>> at java.net.SocksSocketImpl.connect(Unknown Source)
>>> at java.net.Socket.connect(Unknown Source)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>> at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
>>> at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
>>> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
>>> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
>>> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
>>> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
>>> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
>>> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
>>> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
>>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
>>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
>>> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
>>> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
>>> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
>>> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
>>> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
>>> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
>>> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>> at com.ultimatetech.console.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:82)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
>>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>>> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
>>> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
>>> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
>>> at java.lang.Thread.run(Unknown Source)
>>>
>>> I am able to open the link through browser but not through application. Also I have checked firewall setting, it is not blocking any ports.
>>>
>>> Please suggest.
>>>
>>> Thanks,
>>> Rohan Kadam.
>>>
>>> -----Original Message-----
>>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>>> Sent: Thursday, July 07, 2011 1:55 AM
>>> To: Tomcat Users List
>>> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version :
>>> 7.0.14)
>>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Rohan,
>>>
>>> On 7/5/2011 12:18 AM, Rohan Kadam wrote:
>>>> I apologize for the typo made by me. I used only
>>>> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
>>>> didn't work.
>>> Go back and read Konstantin's response.
>>>
>>> Sounds like you have two options:
>>>
>>> 1. Use another connector (BIO or NIO) 2. Configure APR to use IPv4
>>>
>>> - -chris
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.10 (MingW32)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
>>> pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
>>> =8luQ
>>> -----END PGP SIGNATURE-----
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>> "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."
>>> www.cybage.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>> "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."
>> www.cybage.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> "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."
> www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hi André,
Yes, whatever your understanding is correct. And also the connector tag is inside of Tomcat B.
Thanks.
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Wednesday, July 13, 2011 4:52 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Rohan Kadam wrote:
> I really apologize for the confusion created.
>
> We are having an application, which is deployed on tomcat. Rather we are shipping the application with tomcat. After extraction (complete installation), the application is placed under the webapps directory.
>
> The logs that I have shared is from the console, while debugging the application.
Ok, so I understand that it is your web application A, running inside your Tomcat B, which tries to access another webserver C. And application A, to connect to webserver C, is using a httpclient object for that.
Right ?
>
> To summarize more, we were facing a similar kind of problem in an
> earlier version of tomcat when we upgraded it from 5.5.26 to 5.5.30
> (We were able to access the link through browser,
What link to where ?
Do you mean that the browser (D) can connect directly to webserver C ?
But that when application A tries to connect to webserver C, you have the error below ?
(java.net.ConnectException: Connection refused: connect..)
but not through application). To solve this issue, we modified the connector tag in the server.xml file.
>
> <Connector port="7070" maxHttpHeaderSize="8192"
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> connectionTimeout="20000"
> disableUploadTimeout="true" address="0.0.0.0" />
>
Still to make things clear : is this <Connector> inside of Tomcat B, or is it the connector of the other webserver C ?
> As, it can be seen from above we have added address="0.0.0.0" in the connector tag, by doing so we were able to connect.
>
> Now, as per the new requirement, we are upgrading our tomcat from 5.5.30 to 7.0.14(Since the folder structure is changed, we are shipping the fresh copy of tomcat). We have modified the connector tag as we have done for 5.5.30, but still no success. Please let me know if I am missing something or you want more information for the same.
>
> Thanks.
>
> -----Original Message-----
> From: André Warnier [mailto:aw@ice-sa.com]
> Sent: Wednesday, July 13, 2011 3:12 PM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version :
> 7.0.14)
>
> Rohan,
>
> what you have never clearly explained until now in this rather long thread, is what you are exactly trying to do.
>
> Is it :
>
> a) an external application written in Java, which is trying to connect to Tomcat ?
> (and the log lines below are from the logfile of that application)
>
> OR
>
> b) is it a webapp /within Tomcat/ which is trying to connect to some other server ?
> (and the log lines below are from a Tomcat logfile)
>
> Then, when you have answered the above, can you show us exactly which parameters you are using for the org.apache.commons.httpclient connection method, to set up this connection ?
> (host, port, URL, whatever)
>
>
>
> Rohan Kadam wrote:
>> Hi All,
>>
>> I tried again. And still not successful, please find the stack trace
>> below -
>>
>> INFO: I/O exception (java.net.ConnectException) caught when
>> processing request: Connection refused: connect Jul 13, 2011 12:10:36
>> PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
>> INFO: Retrying request
>> java.net.ConnectException: Connection refused: connect
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net.PlainSocketImpl.doConnect(Unknown Source)
>> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>> at java.net.PlainSocketImpl.connect(Unknown Source)
>> at java.net.SocksSocketImpl.connect(Unknown Source)
>> at java.net.Socket.connect(Unknown Source)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
>> at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
>> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
>> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
>> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
>> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
>> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
>> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
>> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
>> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
>> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
>> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
>> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
>> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
>> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
>> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>> at com.ultimatetech.console.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:82)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
>> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
>> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
>> at java.lang.Thread.run(Unknown Source)
>>
>> I am able to open the link through browser but not through application. Also I have checked firewall setting, it is not blocking any ports.
>>
>> Please suggest.
>>
>> Thanks,
>> Rohan Kadam.
>>
>> -----Original Message-----
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Sent: Thursday, July 07, 2011 1:55 AM
>> To: Tomcat Users List
>> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version :
>> 7.0.14)
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Rohan,
>>
>> On 7/5/2011 12:18 AM, Rohan Kadam wrote:
>>> I apologize for the typo made by me. I used only
>>> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
>>> didn't work.
>> Go back and read Konstantin's response.
>>
>> Sounds like you have two options:
>>
>> 1. Use another connector (BIO or NIO) 2. Configure APR to use IPv4
>>
>> - -chris
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (MingW32)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
>> pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
>> =8luQ
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>> "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."
>> www.cybage.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> "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."
> www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by André Warnier <aw...@ice-sa.com>.
Rohan Kadam wrote:
> I really apologize for the confusion created.
>
> We are having an application, which is deployed on tomcat. Rather we are shipping the application with tomcat. After extraction (complete installation), the application is placed under the webapps directory.
>
> The logs that I have shared is from the console, while debugging the application.
Ok, so I understand that it is your web application A, running inside your Tomcat B, which
tries to access another webserver C. And application A, to connect to webserver C, is
using a httpclient object for that.
Right ?
>
> To summarize more, we were facing a similar kind of problem in an earlier version of tomcat when we upgraded it from 5.5.26 to 5.5.30 (We were able to access the link through browser,
What link to where ?
Do you mean that the browser (D) can connect directly to webserver C ?
But that when application A tries to connect to webserver C, you have the error below ?
(java.net.ConnectException: Connection refused: connect..)
but not through application). To solve this issue, we modified the connector tag in the
server.xml file.
>
> <Connector port="7070" maxHttpHeaderSize="8192"
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> connectionTimeout="20000" disableUploadTimeout="true" address="0.0.0.0" />
>
Still to make things clear : is this <Connector> inside of Tomcat B, or is it the
connector of the other webserver C ?
> As, it can be seen from above we have added address="0.0.0.0" in the connector tag, by doing so we were able to connect.
>
> Now, as per the new requirement, we are upgrading our tomcat from 5.5.30 to 7.0.14(Since the folder structure is changed, we are shipping the fresh copy of tomcat). We have modified the connector tag as we have done for 5.5.30, but still no success. Please let me know if I am missing something or you want more information for the same.
>
> Thanks.
>
> -----Original Message-----
> From: André Warnier [mailto:aw@ice-sa.com]
> Sent: Wednesday, July 13, 2011 3:12 PM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
> Rohan,
>
> what you have never clearly explained until now in this rather long thread, is what you are exactly trying to do.
>
> Is it :
>
> a) an external application written in Java, which is trying to connect to Tomcat ?
> (and the log lines below are from the logfile of that application)
>
> OR
>
> b) is it a webapp /within Tomcat/ which is trying to connect to some other server ?
> (and the log lines below are from a Tomcat logfile)
>
> Then, when you have answered the above, can you show us exactly which parameters you are using for the org.apache.commons.httpclient connection method, to set up this connection ?
> (host, port, URL, whatever)
>
>
>
> Rohan Kadam wrote:
>> Hi All,
>>
>> I tried again. And still not successful, please find the stack trace below -
>>
>> INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
>> Jul 13, 2011 12:10:36 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
>> INFO: Retrying request
>> java.net.ConnectException: Connection refused: connect
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net.PlainSocketImpl.doConnect(Unknown Source)
>> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>> at java.net.PlainSocketImpl.connect(Unknown Source)
>> at java.net.SocksSocketImpl.connect(Unknown Source)
>> at java.net.Socket.connect(Unknown Source)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
>> at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
>> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
>> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
>> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
>> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
>> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
>> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
>> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
>> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
>> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
>> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
>> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
>> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
>> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
>> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
>> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>> at com.ultimatetech.console.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:82)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
>> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
>> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
>> at java.lang.Thread.run(Unknown Source)
>>
>> I am able to open the link through browser but not through application. Also I have checked firewall setting, it is not blocking any ports.
>>
>> Please suggest.
>>
>> Thanks,
>> Rohan Kadam.
>>
>> -----Original Message-----
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Sent: Thursday, July 07, 2011 1:55 AM
>> To: Tomcat Users List
>> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Rohan,
>>
>> On 7/5/2011 12:18 AM, Rohan Kadam wrote:
>>> I apologize for the typo made by me. I used only
>>> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
>>> didn't work.
>> Go back and read Konstantin's response.
>>
>> Sounds like you have two options:
>>
>> 1. Use another connector (BIO or NIO)
>> 2. Configure APR to use IPv4
>>
>> - -chris
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (MingW32)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
>> pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
>> =8luQ
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>> "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."
>> www.cybage.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> "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."
> www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
I really apologize for the confusion created.
We are having an application, which is deployed on tomcat. Rather we are shipping the application with tomcat. After extraction (complete installation), the application is placed under the webapps directory.
The logs that I have shared is from the console, while debugging the application.
To summarize more, we were facing a similar kind of problem in an earlier version of tomcat when we upgraded it from 5.5.26 to 5.5.30 (We were able to access the link through browser, but not through application). To solve this issue, we modified the connector tag in the server.xml file.
<Connector port="7070" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" address="0.0.0.0" />
As, it can be seen from above we have added address="0.0.0.0" in the connector tag, by doing so we were able to connect.
Now, as per the new requirement, we are upgrading our tomcat from 5.5.30 to 7.0.14(Since the folder structure is changed, we are shipping the fresh copy of tomcat). We have modified the connector tag as we have done for 5.5.30, but still no success. Please let me know if I am missing something or you want more information for the same.
Thanks.
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Wednesday, July 13, 2011 3:12 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Rohan,
what you have never clearly explained until now in this rather long thread, is what you are exactly trying to do.
Is it :
a) an external application written in Java, which is trying to connect to Tomcat ?
(and the log lines below are from the logfile of that application)
OR
b) is it a webapp /within Tomcat/ which is trying to connect to some other server ?
(and the log lines below are from a Tomcat logfile)
Then, when you have answered the above, can you show us exactly which parameters you are using for the org.apache.commons.httpclient connection method, to set up this connection ?
(host, port, URL, whatever)
Rohan Kadam wrote:
> Hi All,
>
> I tried again. And still not successful, please find the stack trace below -
>
> INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
> Jul 13, 2011 12:10:36 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
> INFO: Retrying request
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
> at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at com.ultimatetech.console.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:82)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
> at java.lang.Thread.run(Unknown Source)
>
> I am able to open the link through browser but not through application. Also I have checked firewall setting, it is not blocking any ports.
>
> Please suggest.
>
> Thanks,
> Rohan Kadam.
>
> -----Original Message-----
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Sent: Thursday, July 07, 2011 1:55 AM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rohan,
>
> On 7/5/2011 12:18 AM, Rohan Kadam wrote:
>> I apologize for the typo made by me. I used only
>> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
>> didn't work.
>
> Go back and read Konstantin's response.
>
> Sounds like you have two options:
>
> 1. Use another connector (BIO or NIO)
> 2. Configure APR to use IPv4
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
> pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
> =8luQ
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> "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."
> www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by André Warnier <aw...@ice-sa.com>.
Rohan,
what you have never clearly explained until now in this rather long thread, is what you
are exactly trying to do.
Is it :
a) an external application written in Java, which is trying to connect to Tomcat ?
(and the log lines below are from the logfile of that application)
OR
b) is it a webapp /within Tomcat/ which is trying to connect to some other server ?
(and the log lines below are from a Tomcat logfile)
Then, when you have answered the above, can you show us exactly which parameters you are
using for the org.apache.commons.httpclient connection method, to set up this connection ?
(host, port, URL, whatever)
Rohan Kadam wrote:
> Hi All,
>
> I tried again. And still not successful, please find the stack trace below -
>
> INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
> Jul 13, 2011 12:10:36 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
> INFO: Retrying request
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
> at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
> at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
> at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
> at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
> at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
> at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at com.ultimatetech.console.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:82)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
> at java.lang.Thread.run(Unknown Source)
>
> I am able to open the link through browser but not through application. Also I have checked firewall setting, it is not blocking any ports.
>
> Please suggest.
>
> Thanks,
> Rohan Kadam.
>
> -----Original Message-----
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Sent: Thursday, July 07, 2011 1:55 AM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rohan,
>
> On 7/5/2011 12:18 AM, Rohan Kadam wrote:
>> I apologize for the typo made by me. I used only
>> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
>> didn't work.
>
> Go back and read Konstantin's response.
>
> Sounds like you have two options:
>
> 1. Use another connector (BIO or NIO)
> 2. Configure APR to use IPv4
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
> pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
> =8luQ
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> "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."
> www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hi All,
I tried again. And still not successful, please find the stack trace below -
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect
Jul 13, 2011 12:10:36 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at com.symantec.lua.util.rcl.HttpHelper.open(HttpHelper.java:209)
at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:82)
at com.symantec.lua.manager.config.ConfigManagerUtil.testServerConnection(ConfigManagerUtil.java:30)
at com.symantec.lua.presentation.common.ServerStatusAction.doAction(ServerStatusAction.java:148)
at com.ultimatetech.console.core.presentation.action.ActionThread.run(ActionThread.java:76)
at com.ultimatetech.console.core.presentation.action.CoreAction.execute(CoreAction.java:184)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.ultimatetech.console.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:82)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
at java.lang.Thread.run(Unknown Source)
I am able to open the link through browser but not through application. Also I have checked firewall setting, it is not blocking any ports.
Please suggest.
Thanks,
Rohan Kadam.
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]
Sent: Thursday, July 07, 2011 1:55 AM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rohan,
On 7/5/2011 12:18 AM, Rohan Kadam wrote:
> I apologize for the typo made by me. I used only
> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
> didn't work.
Go back and read Konstantin's response.
Sounds like you have two options:
1. Use another connector (BIO or NIO)
2. Configure APR to use IPv4
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
=8luQ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rohan,
On 7/5/2011 12:18 AM, Rohan Kadam wrote:
> I apologize for the typo made by me. I used only
> "-Djava.net.preferIPv4Stack=true" in the java option pane. But it
> didn't work.
Go back and read Konstantin's response.
Sounds like you have two options:
1. Use another connector (BIO or NIO)
2. Configure APR to use IPv4
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4UxJUACgkQ9CaO5/Lv0PBpagCfbk2I1OflSti0DwkNzekOH9dG
pAAAn0M7VXdoeo3LnMygLDMY4vwVA6/p
=8luQ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
I apologize for the typo made by me. I used only "-Djava.net.preferIPv4Stack=true" in the java option pane. But it didn't work.
-----Original Message-----
From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Sent: Tuesday, July 05, 2011 12:17 AM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
2011/7/4 Caldarale, Charles R <Ch...@unisys.com>:
>> From: Rohan Kadam [mailto:rohanka@cybage.com]
>> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version :
>> 7.0.14)
>
>> This is the line I was talking about -
>> JAVA_OPTS="-Djava.net.preferIPv4Stack=true"
>
> Which explains why it's being ignored. The line should simply be:
>
> -Djava.net.preferIPv4Stack=true
>
> Just like all the other -D lines shown in the Java tab of tomcat7w...
>
> (If you don't have any other -D lines in the Java tab, your Tomcat
> installation is broken.)
>
It is ignored, because OP uses APR (aka native) connector, and Java properties have no influence on it, per
> ["http-apr-/0.0.0.0-7070"-exec-8] ERROR rcl.HttpHelper
I do not know what "rcl.HttpHelper" is. What else is in the logs? - other messages, stack traces? What is exact text of those?
Anyway, there are two other connector implementations available, that can be used instead of the APR one.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/7/4 Caldarale, Charles R <Ch...@unisys.com>:
>> From: Rohan Kadam [mailto:rohanka@cybage.com]
>> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
>> This is the line I was talking about -
>> JAVA_OPTS="-Djava.net.preferIPv4Stack=true"
>
> Which explains why it's being ignored. The line should simply be:
>
> -Djava.net.preferIPv4Stack=true
>
> Just like all the other -D lines shown in the Java tab of tomcat7w...
>
> (If you don't have any other -D lines in the Java tab, your Tomcat installation is broken.)
>
It is ignored, because OP uses APR (aka native) connector, and Java
properties have no influence on it, per
> ["http-apr-/0.0.0.0-7070"-exec-8] ERROR rcl.HttpHelper
I do not know what "rcl.HttpHelper" is. What else is in the logs? -
other messages, stack traces? What is exact text of those?
Anyway, there are two other connector implementations available, that
can be used instead of the APR one.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Rohan Kadam [mailto:rohanka@cybage.com]
> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
> This is the line I was talking about -
> JAVA_OPTS="-Djava.net.preferIPv4Stack=true"
Which explains why it's being ignored. The line should simply be:
-Djava.net.preferIPv4Stack=true
Just like all the other -D lines shown in the Java tab of tomcat7w...
(If you don't have any other -D lines in the Java tab, your Tomcat installation is broken.)
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Thanks a lot!!!
Hi Chris,
This is the line I was talking about -
JAVA_OPTS="-Djava.net.preferIPv4Stack=true"
-----Original Message-----
From: Pid [mailto:pid@pidster.com]
Sent: Monday, July 04, 2011 2:16 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
On 04/07/2011 05:23, Rohan Kadam wrote:
> I am not getting what I am supposed to do?
>> >
>> > After that Iwent to Java Tab, and added the below line in Java Option Section.
>> > Please let me know if I am missing something.
> The line.
Chris was asking you to specify the line you refer to as being 'below', above. The thread had become lengthy by then and so you could be referring to anything. Being specific helps us help you.
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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Pid <pi...@pidster.com>.
On 04/07/2011 05:23, Rohan Kadam wrote:
> I am not getting what I am supposed to do?
>> >
>> > After that Iwent to Java Tab, and added the below line in Java Option Section.
>> > Please let me know if I am missing something.
> The line.
Chris was asking you to specify the line you refer to as being 'below',
above. The thread had become lengthy by then and so you could be
referring to anything. Being specific helps us help you.
p
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hi,
I am not getting what I am supposed to do?
Thanks,
Rohan
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]
Sent: Friday, July 01, 2011 11:52 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rohan,
On 7/1/2011 7:56 AM, Rohan Kadam wrote:
> We have created a service named say "ABCTomcat"
>
> Then we navigated to bin directory of tomcat, typed the following command -
>
> tomcat7w.exe //ES//ABCTomcat
>
> After that Iwent to Java Tab, and added the below line in Java Option Section.
>
> Please let me know if I am missing something.
The line.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4OED4ACgkQ9CaO5/Lv0PBFygCglpsASTcalnv9mU6E7+UfjQvO
BggAoJuFtVP1GbebaBvvQRPgF+at3sjI
=/xpV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rohan,
On 7/1/2011 7:56 AM, Rohan Kadam wrote:
> We have created a service named say "ABCTomcat"
>
> Then we navigated to bin directory of tomcat, typed the following command -
>
> tomcat7w.exe //ES//ABCTomcat
>
> After that Iwent to Java Tab, and added the below line in Java Option Section.
>
> Please let me know if I am missing something.
The line.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4OED4ACgkQ9CaO5/Lv0PBFygCglpsASTcalnv9mU6E7+UfjQvO
BggAoJuFtVP1GbebaBvvQRPgF+at3sjI
=/xpV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
We have created a service named say "ABCTomcat"
Then we navigated to bin directory of tomcat, typed the following command -
tomcat7w.exe //ES//ABCTomcat
After that Iwent to Java Tab, and added the below line in Java Option Section.
Please let me know if I am missing something.
-----Original Message-----
From: Pid [mailto:pid@pidster.com]
Sent: Friday, July 01, 2011 5:07 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
On 01/07/2011 12:07, Rohan Kadam wrote:
> I have tries to set this java option in catalane .bat, but no success
>
> -Djava.net.preferIPv4Stack=true
>
> 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?
p
> -----Original Message-----
> From: Pid [mailto:pid@pidster.com]
> 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 =
>>> "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.
>>
>> 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="-Djava.net.preferIPv4Stack=true" can be set in
> setenv.sh|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."
> www.cybage.com
"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."
www.cybage.com
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Sorry Folks...I forgot to mention, I have also restarted the service after the changes were done.
-----Original Message-----
From: Rohan Kadam
Sent: Friday, July 01, 2011 5:26 PM
To: Tomcat Users List
Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
We have created a service named say "ABCTomcat"
Then we navigated to bin directory of tomcat, typed the following command -
tomcat7w.exe //ES//ABCTomcat
After that Iwent to Java Tab, and added the below line in Java Option Section.
Please let me know if I am missing something.
-----Original Message-----
From: Pid [mailto:pid@pidster.com]
Sent: Friday, July 01, 2011 5:07 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
On 01/07/2011 12:07, Rohan Kadam wrote:
> I have tries to set this java option in catalane .bat, but no success
>
> -Djava.net.preferIPv4Stack=true
>
> 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?
p
> -----Original Message-----
> From: Pid [mailto:pid@pidster.com]
> 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 =
>>> "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.
>>
>> 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="-Djava.net.preferIPv4Stack=true" can be set in
> setenv.sh|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."
> www.cybage.com
"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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Pid <pi...@pidster.com>.
On 01/07/2011 12:07, Rohan Kadam wrote:
> I have tries to set this java option in catalane .bat, but no success
>
> -Djava.net.preferIPv4Stack=true
>
> 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?
p
> -----Original Message-----
> From: Pid [mailto:pid@pidster.com]
> 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 =
>>> "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.
>>
>> 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="-Djava.net.preferIPv4Stack=true" can be set in setenv.sh|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."
> www.cybage.com
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
I have tries to set this java option in catalane .bat, but no success
-Djava.net.preferIPv4Stack=true
I am using tomcat as a service, so configures the same in Java properties as well. But it is not working.
Please suggest.
-----Original Message-----
From: Pid [mailto:pid@pidster.com]
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 =
>> "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.
>
> 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="-Djava.net.preferIPv4Stack=true" can be set in setenv.sh|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."
www.cybage.com
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Pid <pi...@pidster.com>.
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 = "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.
>
> 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="-Djava.net.preferIPv4Stack=true" can be set in
setenv.sh|bat
p
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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 = "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.
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.
What do Tomcat' logs say when started? What error message(s) do you get
(on the client?)?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4M40YACgkQ9CaO5/Lv0PDRmQCeL7LT4QgVi/VzAbwnLFECa+yI
r9cAn2TNOg50IFejixP0TNsWl0fKVSFv
=Y1qL
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hi,
I am using JAVA 1.6 update 23 version.
Thanks,
Rohan Kadam.
-----Original Message-----
From: Pid [mailto:pid@pidster.com]
Sent: Thursday, June 30, 2011 7:22 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
On 30/06/2011 13:01, Rohan Kadam wrote:
> Hi All,
>
> 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 = "0.0.0.0" in the
> Connector tag of server.xml in the "conf" directory.
>
>
> After upgrading tomcat to 7.0.14, we have done the same process, but
> we are not able to connect.
Have you also upgraded Java? What version (exactly) of Java are you using?
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."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Please find my connector tag below, I have modified it to listen 7070 -
<Connector port="7070" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" address="0.0.0.0" />
-----Original Message-----
From: André Warnier [mailto:aw@ice-sa.com]
Sent: Friday, July 01, 2011 3:00 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Well, answering Christopher's questions would be a good start.
Then also maybe paste the content of your <Connector> tag in your next message.
Rohan Kadam wrote:
> Hi All,
>
> Is some more information required for this?
>
> Thanks.
>
> -----Original Message-----
> From: Rohan Kadam
> Sent: Thursday, June 30, 2011 7:26 PM
> To: Tomcat Users List
> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version :
> 7.0.14)
>
> Hi,
>
> I am using JAVA 1.6 update 23 version.
>
> Thanks,
> Rohan Kadam.
>
> -----Original Message-----
> From: Pid [mailto:pid@pidster.com]
> Sent: Thursday, June 30, 2011 7:22 PM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version :
> 7.0.14)
>
> On 30/06/2011 13:01, Rohan Kadam wrote:
>> Hi All,
>>
>> 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 =
>> "0.0.0.0" in the Connector tag of server.xml in the "conf" directory.
>>
>>
>> After upgrading tomcat to 7.0.14, we have done the same process, but
>> we are not able to connect.
>
> Have you also upgraded Java? What version (exactly) of Java are you using?
>
>
> 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."
> www.cybage.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
"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."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by André Warnier <aw...@ice-sa.com>.
Well, answering Christopher's questions would be a good start.
Then also maybe paste the content of your <Connector> tag in your next message.
Rohan Kadam wrote:
> Hi All,
>
> Is some more information required for this?
>
> Thanks.
>
> -----Original Message-----
> From: Rohan Kadam
> Sent: Thursday, June 30, 2011 7:26 PM
> To: Tomcat Users List
> Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
> Hi,
>
> I am using JAVA 1.6 update 23 version.
>
> Thanks,
> Rohan Kadam.
>
> -----Original Message-----
> From: Pid [mailto:pid@pidster.com]
> Sent: Thursday, June 30, 2011 7:22 PM
> To: Tomcat Users List
> Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
>
> On 30/06/2011 13:01, Rohan Kadam wrote:
>> Hi All,
>>
>> 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 = "0.0.0.0" in the
>> Connector tag of server.xml in the "conf" directory.
>>
>>
>> After upgrading tomcat to 7.0.14, we have done the same process, but
>> we are not able to connect.
>
> Have you also upgraded Java? What version (exactly) of Java are you using?
>
>
> 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."
> www.cybage.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Rohan Kadam <ro...@cybage.com>.
Hi All,
Is some more information required for this?
Thanks.
-----Original Message-----
From: Rohan Kadam
Sent: Thursday, June 30, 2011 7:26 PM
To: Tomcat Users List
Subject: RE: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Hi,
I am using JAVA 1.6 update 23 version.
Thanks,
Rohan Kadam.
-----Original Message-----
From: Pid [mailto:pid@pidster.com]
Sent: Thursday, June 30, 2011 7:22 PM
To: Tomcat Users List
Subject: Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
On 30/06/2011 13:01, Rohan Kadam wrote:
> Hi All,
>
> 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 = "0.0.0.0" in the
> Connector tag of server.xml in the "conf" directory.
>
>
> After upgrading tomcat to 7.0.14, we have done the same process, but
> we are not able to connect.
Have you also upgraded Java? What version (exactly) of Java are you using?
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."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat is not able to connect to IPV4 (Tomcat Version : 7.0.14)
Posted by Pid <pi...@pidster.com>.
On 30/06/2011 13:01, Rohan Kadam wrote:
> Hi All,
>
> 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 = "0.0.0.0" in the Connector tag of server.xml in the "conf" directory.
>
>
> After upgrading tomcat to 7.0.14, we have done the same process, but we are
> not able to connect.
Have you also upgraded Java? What version (exactly) of Java are you using?
p