RE: Tomcat 5.5.28 on 64 bit windows server 2008.
> -Original Message- > From: eurotrans-Verlag [mailto:verlag.preis...@t-online.de] > Sent: Tuesday, August 23, 2011 7:14 AM > To: 'Tomcat Users List' > Subject: RE: Tomcat 5.5.28 on 64 bit windows server 2008. > > Hi, > > > This seems to only apply to Tomcat 5.5.x, however. When Tomcat 7.0.20 > and > Tomcat 6.0.33 are run on a Windows 2008 machine without editing the > config > and using the (default) HTTP-APR / AJP-APR connectors, they only bind > to the > IPv4 "any" address. Only Tomcat 5.5.x binds to the IPv6 address, by > default. > Maybe 7.0.x and 6.0.x have been changed to use the IPv4 any address by > default with the APR connectors, but not 5.5 Thanks for the update. My experience so far has just been with 5.5.x, but we are moving to 6.0.x with our next software release, so I will be testing this soon. It's good to hear that it appears to have been addressed. Jeff __ Confidentiality Notice: This Transmission (including any attachments) may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this transmission in error, please immediately reply to the sender or telephone (512) 343-9100 and delete this transmission from your system. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
Hi, > -Original Message- > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] > Sent: Monday, August 22, 2011 5:35 PM > To: 'Tomcat Users List' > Subject: RE: Tomcat 5.5.28 on 64 bit windows server 2008. > > > > Allow me to clear that up: > 1) If no "address=" parameter is given in the when running > under Windows 2008/Vista/7, then the APR will only bind to the IPv6 > "any" address of [::] for the specified port. > 2) If you need IPv4 support under APR, you will need to either specify > the "address=0.0.0.0" parameter to get the IPv4 "any" address, or > specify the actual IP address to listen on. > 3) If you need to support both IPv4 & IPv6, you will need to set up two > connectors, one for each protocol. > 4) This only applies if you are using the APR/native libraries. > > This was originally discussed on this list in May of 2010, and I think > this was determined to be due to Microsoft deciding to implement two > protocol stacks, but no one was exactly sure. > > Also, this only applies to APR/native version 1.1.12 and later, but I > doubt anyone really wants to use the earlier versions any more. This seems to only apply to Tomcat 5.5.x, however. When Tomcat 7.0.20 and Tomcat 6.0.33 are run on a Windows 2008 machine without editing the config and using the (default) HTTP-APR / AJP-APR connectors, they only bind to the IPv4 "any" address. Only Tomcat 5.5.x binds to the IPv6 address, by default. Maybe 7.0.x and 6.0.x have been changed to use the IPv4 any address by default with the APR connectors, but not 5.5.x. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
> -Original Message- > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] > Sent: Monday, August 22, 2011 9:08 AM > To: 'Tomcat Users List' > Subject: RE: Tomcat 5.5.28 on 64 bit windows server 2008. > > This is a known issue with the APR library, though I don't know if a > bug has ever been entered for it. The APR connectors will only bind to > IPv6-any by default. If you search the list, you will see that it has > been a problem for about a year, and, I think, only affects the > implementation on Windows systems. Therefore, the underlying issue may > be a Windows one. > Allow me to clear that up: 1) If no "address=" parameter is given in the when running under Windows 2008/Vista/7, then the APR will only bind to the IPv6 "any" address of [::] for the specified port. 2) If you need IPv4 support under APR, you will need to either specify the "address=0.0.0.0" parameter to get the IPv4 "any" address, or specify the actual IP address to listen on. 3) If you need to support both IPv4 & IPv6, you will need to set up two connectors, one for each protocol. 4) This only applies if you are using the APR/native libraries. This was originally discussed on this list in May of 2010, and I think this was determined to be due to Microsoft deciding to implement two protocol stacks, but no one was exactly sure. Also, this only applies to APR/native version 1.1.12 and later, but I doubt anyone really wants to use the earlier versions any more. __ Confidentiality Notice: This Transmission (including any attachments) may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this transmission in error, please immediately reply to the sender or telephone (512) 343-9100 and delete this transmission from your system. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
This is a known issue with the APR library, though I don't know if a bug has ever been entered for it. The APR connectors will only bind to IPv6-any by default. If you search the list, you will see that it has been a problem for about a year, and, I think, only affects the implementation on Windows systems. Therefore, the underlying issue may be a Windows one. > -Original Message- > From: Stefan Mayr [mailto:ste...@mayr-stefan.de] > Sent: Sunday, August 21, 2011 10:16 AM > To: Tomcat Users List > Subject: Re: Tomcat 5.5.28 on 64 bit windows server 2008. > > Hello, > > Am 21.08.2011 15:01, schrieb Venkata Surapaneni: > > Verlag, > > > > Both the suggestions worked and We are going to add address > line to the server.xml file. > > > > Is the support for IP 4 dropped by plan or by accident ? If it is by > plan, isn't it early ? There are still lot of applications running on > IP 4 and it will be while before every one is ready for IP 6. > > > > If it is by accident, I believe the versions from 5.5.29 have this > issue. > > I guess this is not a Tomcat issue. In your server.xml you habe the > org.apache.catalina.core.AprLifecycleListener enabled which uses the > dll > named by Eurotrans-Verlag. It should be enough to remove this line from > your config to disable native APR. Another solution might be to keep > your old Tomcat version and update only the binaries für your operating > system. Maybe your dlls are not meant for 64bit Windows. See > http://tomcat.apache.org/download-native.cgi. > > For further JVM IPv6 documentation check first > http://download.oracle.com/javase/6/docs/technotes/guides/net/ipv6_guid > e/index.html > Especially java.net.preferIPv4Stack is interesting to enforce a certain > protocol behaviour. > > Stefan > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > __ Confidentiality Notice: This Transmission (including any attachments) may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this transmission in error, please immediately reply to the sender or telephone (512) 343-9100 and delete this transmission from your system. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 5.5.28 on 64 bit windows server 2008.
Hello, Am 21.08.2011 15:01, schrieb Venkata Surapaneni: Verlag, Both the suggestions worked and We are going to add address line to the server.xml file. Is the support for IP 4 dropped by plan or by accident ? If it is by plan, isn't it early ? There are still lot of applications running on IP 4 and it will be while before every one is ready for IP 6. If it is by accident, I believe the versions from 5.5.29 have this issue. I guess this is not a Tomcat issue. In your server.xml you habe the org.apache.catalina.core.AprLifecycleListener enabled which uses the dll named by Eurotrans-Verlag. It should be enough to remove this line from your config to disable native APR. Another solution might be to keep your old Tomcat version and update only the binaries für your operating system. Maybe your dlls are not meant for 64bit Windows. See http://tomcat.apache.org/download-native.cgi. For further JVM IPv6 documentation check first http://download.oracle.com/javase/6/docs/technotes/guides/net/ipv6_guide/index.html Especially java.net.preferIPv4Stack is interesting to enforce a certain protocol behaviour. Stefan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
Verlag, Both the suggestions worked and We are going to add address line to the server.xml file. Is the support for IP 4 dropped by plan or by accident ? If it is by plan, isn't it early ? There are still lot of applications running on IP 4 and it will be while before every one is ready for IP 6. If it is by accident, I believe the versions from 5.5.29 have this issue. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
Hi,
> -Original Message-
> From: Venkata Surapaneni [mailto:vsurapan...@imedx.com]
> Sent: Sunday, August 21, 2011 12:26 PM
> To: Tomcat Users List
> Subject: RE: Tomcat 5.5.28 on 64 bit windows server 2008.
>
> And on top of this all the log look clean. Nothing looks suspicious.
>
> ===
> =
>
> As suggested I have installed the latest version(5.5.33) of Tomcat
> 5.5.x. After installing I have typed in the browser 'http://localhost'
> to check if the tomcat is installed properly. The home page is
> displayed indicating that the installation is fine. Then I typed in ip
> address of the machine 'http://10.4.2.10' and page not found page is
> displayed. This is exactly the same problem why we have downgraded the
> version. There are no changes or customizations made to the
> installation. It was default installation and the only change is to use
> port 80 instead of 8080.
>
> (...)
I see the same behavior when installing Tomcat 5.5.33 (Core) on Windows 7 32
bit. Without changing anything in the config nor other Tomcat files, after
starting Tomcat, http://localhost:8080/ works, whereas
http://192.168.0.4:8080/ (the LAN IP) does not (Connecting to that port
fails). Note that also http://127.0.0.1:8080/ does not work.
>From looking at netstat, it looks like Tomcat is only binding to the IPv6
addresses, but not to IPv4 addresses, so http://127.0.0.1:8080/ can't work.
Netstat's output for the Tomcat process ("ABHÖREN" means "LISTENING"):
TCP[::]:8009 [::]:0 ABHÖREN 3028
TCP[::]:8080 [::]:0 ABHÖREN 3028
The default installation of Tomcat 5.5.33 uses Tomcat Native 1.1.20. After I
remove/rename the tcnative-1.dll in Tomcat's bin directory and restarting
Tomcat, now Tomcat binds also to IPv4 addresses and http://127.0.0.1:8080/
(and the variant with the LAN IP) works.
Netstat:
TCP0.0.0.0:8009 0.0.0.0:0 ABHREN 3596
TCP0.0.0.0:8080 0.0.0.0:0 ABHREN 3596
TCP[::]:8009 [::]:0 ABHREN 3596
TCP[::]:8080 [::]:0 ABHREN 3596
With Tomcat 7.0.20 (using TC Native) and without changing anything in the
config, it seems to only bind to the IPv4 addresses, but no IPv6.
TCP0.0.0.0:8009 0.0.0.0:0 ABHREN 2864
TCP0.0.0.0:8080 0.0.0.0:0 ABHREN 2864
When using Tomcat 7.0.20 (without Native), it binds to IPv4 as well as IPv6
(like Tomcat 5.5.33 without Native).
However I could get TC 5.5.33 to bind on the IPv4 address, by adding the
"address" attribute to the element in server.xml. Maybe you
could try this and see if it solves the problem?
However it seems a bit strange that TC 5.5.33 is only binding to the IPv6
addresses by default/using Native.
Regards,
Konstantin Preißer
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
And on top of this all the log look clean. Nothing looks suspicious. As suggested I have installed the latest version(5.5.33) of Tomcat 5.5.x. After installing I have typed in the browser 'http://localhost' to check if the tomcat is installed properly. The home page is displayed indicating that the installation is fine. Then I typed in ip address of the machine 'http://10.4.2.10' and page not found page is displayed. This is exactly the same problem why we have downgraded the version. There are no changes or customizations made to the installation. It was default installation and the only change is to use port 80 instead of 8080. The below is the server.xml file. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Sunday, August 21, 2011 2:55 PM To: Tomcat Users List Subject: Re: Tomcat 5.5.28 on 64 bit windows server 2008. Venkata Surapaneni wrote: > We have a requirement to stick to 5.x version as of now. We tried using the > latest version of 5.5.x, but we encountered a issue. After installing the > tomcat and if we check in the browser as localhost, it is working fine. But > if we try accessing using IP address, then the Tomcat home page is not > displayed. The result is same for all the versions later than 5.5.28. Not > sure what is causing this or what needs to be done to fix this. So we started > using 5.5.28. > That sounds like a network misconfiguration issue or a misconfiguration within Tomcat's server.xml, not a Tomcat problem per se. 1) download the latest version of Tomcat 5.5 and install it, even if it appears not to work 2) Note the exact problem carefully (including logfile message if any) 3) Remove all comments and sensitive information from the server.xml file, and copy and paste it in your next message. Repeat : copy and paste, do not send it as an attachment; the list strips most attachmnts. The point : better to use a known "best version" of Tomcat, and fix what appears to be a simple misconfiguration, rather than spending a lot of time looking for missing DLLs or the like. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
As suggested I have installed the latest version(5.5.33) of Tomcat 5.5.x. After installing I have typed in the browser 'http://localhost' to check if the tomcat is installed properly. The home page is displayed indicating that the installation is fine. Then I typed in ip address of the machine 'http://10.4.2.10' and page not found page is displayed. This is exactly the same problem why we have downgraded the version. There are no changes or customizations made to the installation. It was default installation and the only change is to use port 80 instead of 8080. The below is the server.xml file. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Sunday, August 21, 2011 2:55 PM To: Tomcat Users List Subject: Re: Tomcat 5.5.28 on 64 bit windows server 2008. Venkata Surapaneni wrote: > We have a requirement to stick to 5.x version as of now. We tried using the > latest version of 5.5.x, but we encountered a issue. After installing the > tomcat and if we check in the browser as localhost, it is working fine. But > if we try accessing using IP address, then the Tomcat home page is not > displayed. The result is same for all the versions later than 5.5.28. Not > sure what is causing this or what needs to be done to fix this. So we started > using 5.5.28. > That sounds like a network misconfiguration issue or a misconfiguration within Tomcat's server.xml, not a Tomcat problem per se. 1) download the latest version of Tomcat 5.5 and install it, even if it appears not to work 2) Note the exact problem carefully (including logfile message if any) 3) Remove all comments and sensitive information from the server.xml file, and copy and paste it in your next message. Repeat : copy and paste, do not send it as an attachment; the list strips most attachmnts. The point : better to use a known "best version" of Tomcat, and fix what appears to be a simple misconfiguration, rather than spending a lot of time looking for missing DLLs or the like. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 5.5.28 on 64 bit windows server 2008.
Venkata Surapaneni wrote: We have a requirement to stick to 5.x version as of now. We tried using the latest version of 5.5.x, but we encountered a issue. After installing the tomcat and if we check in the browser as localhost, it is working fine. But if we try accessing using IP address, then the Tomcat home page is not displayed. The result is same for all the versions later than 5.5.28. Not sure what is causing this or what needs to be done to fix this. So we started using 5.5.28. That sounds like a network misconfiguration issue or a misconfiguration within Tomcat's server.xml, not a Tomcat problem per se. 1) download the latest version of Tomcat 5.5 and install it, even if it appears not to work 2) Note the exact problem carefully (including logfile message if any) 3) Remove all comments and sensitive information from the server.xml file, and copy and paste it in your next message. Repeat : copy and paste, do not send it as an attachment; the list strips most attachmnts. The point : better to use a known "best version" of Tomcat, and fix what appears to be a simple misconfiguration, rather than spending a lot of time looking for missing DLLs or the like. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 5.5.28 on 64 bit windows server 2008.
We have a requirement to stick to 5.x version as of now. We tried using the latest version of 5.5.x, but we encountered a issue. After installing the tomcat and if we check in the browser as localhost, it is working fine. But if we try accessing using IP address, then the Tomcat home page is not displayed. The result is same for all the versions later than 5.5.28. Not sure what is causing this or what needs to be done to fix this. So we started using 5.5.28. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Sunday, August 21, 2011 3:15 AM To: Tomcat Users List Subject: Re: Tomcat 5.5.28 on 64 bit windows server 2008. kiran surapaneni wrote: > We are setting up Tomcat 5.5.28 on 64 bit Windows server 2008. Why are you doing this on a new system ? The current version of Tomcat is 7.0.20, and between Tomcat 5.5.28 (itself not the most recent version of Tomcat 5.5), there was already Tomcat 6.0 (current version 6.0.33). Understand : it is not /forbidden/ to use an older version, but the level of support you will get will always be better on a more recent version. Specially for issues such as the one you mention. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 5.5.28 on 64 bit windows server 2008.
kiran surapaneni wrote: We are setting up Tomcat 5.5.28 on 64 bit Windows server 2008. Why are you doing this on a new system ? The current version of Tomcat is 7.0.20, and between Tomcat 5.5.28 (itself not the most recent version of Tomcat 5.5), there was already Tomcat 6.0 (current version 6.0.33). Understand : it is not /forbidden/ to use an older version, but the level of support you will get will always be better on a more recent version. Specially for issues such as the one you mention. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 5.5.28 on 64 bit windows server 2008.
We are setting up Tomcat 5.5.28 on 64 bit Windows server 2008. The installation completes fine and also the tomcat seems to be starting correctly. But in the log files the following exception is logged. java.lang.UnsatisfiedLinkError: C:\Tomcat5.5\bin\tcnative-1.dll: Can't find dependent libraries at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(Unknown Source) at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) at org.apache.tomcat.jni.Library.(Library.java:42) at org.apache.tomcat.jni.Library.initialize(Library.java:168) 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.catalina.core.AprLifecycleListener.lifecycleEvent(AprLifecycleListener.java:83) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:757) at org.apache.catalina.startup.Catalina.load(Catalina.java:504) at org.apache.catalina.startup.Catalina.load(Catalina.java:524) 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.catalina.startup.Bootstrap.load(Bootstrap.java:267) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Any idea on how this can be resolved ?
