RE: mod_jk.so problems going from Apache 2.0.55 to Apache 2.2.2
Any reason you can't use mod_proxy_ajp? I believe that is the recommended method with 2.2.x. , Josh. -Original Message- From: raorba [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 7:18 PM To: users@tomcat.apache.org Subject: Re: mod_jk.so problems going from Apache 2.0.55 to Apache 2.2.2 Hey man Is it possible to you to send me a copy or your brand new, recompiled mod_jk.so for 2.2.2? You will be think I'm lazy, but in fact I'm more a Linux boy than Windows boy and I don't know how use VC++ at all. My email is rafael_oropeza at hotmail.com Thanks in advance -- View this message in context: http://www.nabble.com/mod_jk.so+problems+going+from+Apache+2.0 .55+to+Apache+2.2.2-t1660137.html#a4619224 Sent from the Tomcat - User forum at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Native connector startup problem
Are you talking about the thread I had started regarding build the native connector on HP? http://marc.theaimsgroup.com/?l=tomcat-devm=113156765527679w=2 If so, I don't believe that is relevant to my current issue. , Josh. -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Friday, May 26, 2006 8:26 AM To: Tomcat Users List Subject: Re: Native connector startup problem Good Morning Josh- You asked Yoav Shapira (from Apache) on a very similar topic and he provided a suggestion last November I would be interested to know what were the results when you followed his suggestion? Thanks, Martin -- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Fenlason, Josh [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org; Martin Gainty [EMAIL PROTECTED] Sent: Friday, May 26, 2006 9:04 AM Subject: RE: Native connector startup problem Thanks for the suggestion, but the port isn't in use. If I disable the native connector, Tomcat starts up fine. I ran netstat and nothing was using that port. Changing the AJP port to something else that I know is open doesn't fix it either. I'm pretty sure there is something fishy going on (at least from AIX's perspective) in the native code when it binds the port. However, I'm not real experienced with C, so I'm not sure what else to look at. Any familiar with the native apr connector have any suggestions? Thanks. , Josh. -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 5:15 PM To: Tomcat Users List Subject: Re: Native connector startup problem Looks more like AJP port is bound ..grep thru http*.conf , find the AJPPort specifier (usually 8009) then netstat -a | grep ThatPort (then go after the process id) If that doesnt solve it shutdown Tomcat/ shutdown Apache, and start Apache / start Tomcat If that doesnt solve it you may have to power cycle the box Anyone else ??? M- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Fenlason, Josh [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Thursday, May 25, 2006 5:44 PM Subject: Native connector startup problem I'm running into the error when I try to startup Tomcat 5.5.17 with the 1.1.3 native connector on AIX. It starts up fine on the same port when not using the native connector, so there's nothing else using the port. Has anyone else seen this? Anyone have any suggestions on what's wrong? Thanks in advance. , Josh. -bash-3.00$ LD_LIBRARY_PATH=/home/snow/jfenlason/aix/install/tomcat5.5.17/ tomcat/bin /native ./catalina.sh run Using CATALINA_BASE: /home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat Using CATALINA_HOME: /home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat Using CATALINA_TMPDIR: /home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat/temp Using JRE_HOME: /usr/java5 May 25, 2006 4:35:02 PM org.apache.coyote.ajp.AjpAprProtocol init SEVERE: Error initializing endpoint java.lang.Exception: Socket bind failed: [22] A system call received a parameter that is not valid. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:571) at org.apache.coyote.ajp.AjpAprProtocol.init(AjpAprProtocol.java:183) at org.apache.catalina.connector.Connector.initialize(Connector.j ava:1016) at org.apache.catalina.core.StandardService.initialize(StandardSe rvice.java :580) at org.apache.catalina.core.StandardServer.initialize(StandardSer ver.java:7 91) at org.apache.catalina.startup.Catalina.load(Catalina.java:503) at org.apache.catalina.startup.Catalina.load(Catalina.java:523) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.jav a:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessor Impl.java:43) at java.lang.reflect.Method.invoke(Method.java:615
Native connector startup problem
I'm running into the error when I try to startup Tomcat 5.5.17 with the 1.1.3 native connector on AIX. It starts up fine on the same port when not using the native connector, so there's nothing else using the port. Has anyone else seen this? Anyone have any suggestions on what's wrong? Thanks in advance. , Josh. -bash-3.00$ LD_LIBRARY_PATH=/home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat/bin /native ./catalina.sh run Using CATALINA_BASE: /home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat Using CATALINA_HOME: /home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat Using CATALINA_TMPDIR: /home/snow/jfenlason/aix/install/tomcat5.5.17/tomcat/temp Using JRE_HOME: /usr/java5 May 25, 2006 4:35:02 PM org.apache.coyote.ajp.AjpAprProtocol init SEVERE: Error initializing endpoint java.lang.Exception: Socket bind failed: [22] A system call received a parameter that is not valid. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:571) at org.apache.coyote.ajp.AjpAprProtocol.init(AjpAprProtocol.java:183) at org.apache.catalina.connector.Connector.initialize(Connector.java:1016) at org.apache.catalina.core.StandardService.initialize(StandardService.java :580) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:7 91) at org.apache.catalina.startup.Catalina.load(Catalina.java:503) at org.apache.catalina.startup.Catalina.load(Catalina.java:523) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:266) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:431) May 25, 2006 4:35:02 PM org.apache.catalina.startup.Catalina load SEVERE: Catalina.start LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [22] A system call received a parameter that is not valid. at org.apache.catalina.connector.Connector.initialize(Connector.java:1018) at org.apache.catalina.core.StandardService.initialize(StandardService.java :580) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:7 91) at org.apache.catalina.startup.Catalina.load(Catalina.java:503) at org.apache.catalina.startup.Catalina.load(Catalina.java:523) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:266) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:431) May 25, 2006 4:35:02 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1145 ms May 25, 2006 4:35:03 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina May 25, 2006 4:35:03 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 May 25, 2006 4:35:03 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled May 25, 2006 4:35:06 PM org.apache.coyote.ajp.AjpAprProtocol start SEVERE: Error starting endpoint java.lang.Exception: Socket bind failed: [22] A system call received a parameter that is not valid. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:571) at org.apache.tomcat.util.net.AprEndpoint.start(AprEndpoint.java:681) at org.apache.coyote.ajp.AjpAprProtocol.start(AjpAprProtocol.java:211) at org.apache.catalina.connector.Connector.start(Connector.java:1089) at org.apache.catalina.core.StandardService.start(StandardService.java:459) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) May 25, 2006 4:35:06 PM org.apache.catalina.startup.Catalina start SEVERE: Catalina.start: LifecycleException: service.getName(): Catalina; Protocol handler start failed: java.lang.Exception: Socket bind failed: [22] A system call received a parameter that is not valid. at
Native Connector Question
What do I have to do to configure Tomcat to use the native connector on Unix? I've tried adding -Djava.library.path=path_to_ssl_apr_native_libraries, but it isn't loading them. It works for me on Windows, so I'm not sure what I'm doing wrong on Unix. Any suggestions? Thanks. , Josh.
RE: Native Connector Question
My native lib binary is fine because setting LD_LIBRARY_PATH works fine. I've tried adding -Djava.library.path to JAVA_OPTS and CATALINA_OPTS in my Tomcat startup script, but it isn't loading the native connector. Any thoughts on why the second method isn't working? Thanks in advance. , Josh. -Original Message- From: Markus Schönhaber [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 10:22 AM To: Tomcat Users List Subject: Re: Native Connector Question Fenlason, Josh wrote: What do I have to do to configure Tomcat to use the native connector on Unix? I've tried adding Where? -Djava.library.path=path_to_ssl_apr_native_libraries, but it isn't loading them. It works for me on Windows, so I'm not sure what I'm doing wrong on Unix. Any suggestions? Thanks. Creating a file named setenv.sh in Tomcat's bin folder that contains either export LD_LIBRARY_PATH=path to native lib or CATALINA_OPTS=-Djava.library.path=path to native lib works fine for me. To make sure the source of the problem isn't your self-compiled native lib (if you use one) you could download and try a pre-compiled one: http://www.apache.org/dist/tomcat/tomcat-connectors/native/ Regards mks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Native Connector Question
I tried each of these in tomcat_home/bin/setenv.sh #JAVA_OPTS=$JAVA_OPTS -Djava.library.path=/home/snow/jfenlason/solaris/install/tomcat/bin CATALINA_OPTS=$CATALINA_OPTS -Djava.library.path=/home/snow/jfenlason/solaris/install/tomcat/bin At the moment, I have all the native libraries in tomcat_home/bin. I'm starting Tomcat by executing startup.sh. Any other info that would be helpful? Thanks. , Josh. -Original Message- From: Markus Schönhaber [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 10:45 AM To: Tomcat Users List Subject: Re: Native Connector Question Fenlason, Josh wrote: My native lib binary is fine because setting LD_LIBRARY_PATH works fine. I've tried adding -Djava.library.path to JAVA_OPTS and CATALINA_OPTS in my Tomcat startup script, but it isn't loading the native connector. Any thoughts on why the second method isn't working? Thanks in advance. , Josh. No. At least not without knowing what exactly you are doing. Regards mks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Native Connector Question
That sucks. Thanks for the pointer though. How come it works on Windows? Thanks. , Josh. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 11:00 AM To: Tomcat Users List Subject: Re: Native Connector Question Fenlason, Josh wrote: My native lib binary is fine because setting LD_LIBRARY_PATH works fine. I've tried adding -Djava.library.path to JAVA_OPTS and CATALINA_OPTS in my Tomcat startup script, but it isn't loading the native connector. Any thoughts on why the second method isn't working? Thanks in advance. See: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4280189 java.library.path is read-only (regarding the system), so you will need LD_LIBRARY_PATH set up for natives. The major problem is that it is wrongly documented by Sun. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Native Connector Question
Thanks for the explanation. , Josh. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 11:19 AM To: Tomcat Users List Subject: Re: Native Connector Question Fenlason, Josh wrote: That sucks. Thanks for the pointer though. How come it works on Windows? Thanks. It won't work if the library you load depends on other library that is not in the PATH, so it's basically the same. For Windows we build tcnative statically linked to OpenSSL and APR, so if you wish to make libtcnatve (uses OpenSSL and APR as dll, then the java.library.path will not work, but you will need to adjust the PATH). If the .dlls are in the same path from which you start the application then the LoadLibrary WIN API will use the working directory as a dll search path, so that's why it seems to work. Try to put the tcnative-1.dll outside bin, and you'll see the difference. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building mod_jk.so on AIX
This doesn't answer your question, but is there a specific reason you don't just user mod_proxy_ajp with Apache 2.2.0? You wouldn't have to build mod_jk then. , Josh. -Original Message- From: Bernie Durfee [mailto:[EMAIL PROTECTED] Sent: Friday, March 24, 2006 12:41 PM To: Tomcat Users List Subject: Building mod_jk.so on AIX I'm trying to build mod_jk.so on an AIX 5.3 server. I compiled and installed Apache 2.2.0. I run... ./configure --with-apxs=/usr/local/apache-2.2.0/bin/apxs ...but it fails with the error... could not find /usr/local/apache-2.2.0/bin/apxs configure: error: You must specify a valid --with-apxs path ...but I know the path is correct... ls -l /usr/local/apache-2.2.0/bin/apxs 22455 Mar 24 11:46 /usr/local/apache-2.2.0/bin/apxs ...so maybe the configure script is not recognizing the apxs script? Is there a workaround? Thanks, Bernie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat not shutting down
What version of Tomcat are you using? Are you using the native APR connector? There is a bug in the native shutdown code in 5.5.15, but it's fixed in 5.5.16. , Josh. -Original Message- From: Khawaja Shams [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:27 PM To: Tomcat Users List Subject: Tomcat not shutting down Hello, Has anyone had the following problem: Tomcat refuses to shutdown and stops listening on port 8005 for the shutdown connection even though it is still listening on 8080? With the latest version of tomcat, I get nothing when I do ps -ef|grep tomcat. Is there any other way to find the process id of tomcat that is still running and kill it without restarting the server? Currently, if I try to start tomcat, I get a bind exception that the address is already in use. We have no other applications running on this port, so I know that it is a stale version of tomcat (netstat). Thanks in advance. Regards, Khawaja Shams - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat not shutting down
It sounds like you're running into the native connector shutdown issue I had a while back. http://marc.theaimsgroup.com/?l=tomcat-userm=113925257718848w=2 This problem is fixed in 5.5.16 which looks like it will be voted stable very soon. You could run with out the native connector until and then move to 5.5.16. Or rebuild the connector yourself. , Josh. -Original Message- From: Khawaja Shams [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:50 PM To: Tomcat Users List Subject: Re: Tomcat not shutting down Hello, Thank you for responding. I am using 5.5.15. I shutdown using TOMCAT_HOME/bin/shutdown.sh. Do I need to upgrade to the latest version to get this to work? Thanks again. Regards, Khawaja Shams On 3/13/06, Fenlason, Josh [EMAIL PROTECTED] wrote: What version of Tomcat are you using? Are you using the native APR connector? There is a bug in the native shutdown code in 5.5.15, but it's fixed in 5.5.16. , Josh. -Original Message- From: Khawaja Shams [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:27 PM To: Tomcat Users List Subject: Tomcat not shutting down Hello, Has anyone had the following problem: Tomcat refuses to shutdown and stops listening on port 8005 for the shutdown connection even though it is still listening on 8080? With the latest version of tomcat, I get nothing when I do ps -ef|grep tomcat. Is there any other way to find the process id of tomcat that is still running and kill it without restarting the server? Currently, if I try to start tomcat, I get a bind exception that the address is already in use. We have no other applications running on this port, so I know that it is a stale version of tomcat (netstat). Thanks in advance. Regards, Khawaja Shams - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
That depends if you want to use Apache 2.0.x, Apache 2.2.x, or some other web server (i.e. IIS). If you're planning on using Apache 2.2.x, mod_proxy_ajp is the way to go. For anything else, mod_jk is the way to go. , Josh. -Original Message- From: Brad O'Hearne [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 9:02 AM To: Tomcat Users List Subject: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?) I suppose this question deserved its own thread. Before I spend any more time trying to get this configured, I would like to know what is the best way to proceed: mod_jk or mod_proxy_ajp? Thanks, Brad On Feb 24, 2006, at 7:49 AM, Brad O'Hearne wrote: Jess, Thanks for the reply. Responses below: On Feb 24, 2006, at 6:51 AM, Jess Holle wrote: If you're using Apache 1.3.x or 2.0.x, mod_jk is pretty simple overall. No, you don't want to even try in-process stuff and, yes, if you have a firewall in between Apache and Tomcat that drops idle connections you should read carefully (this is covered by the docs). The only big complaint I have is that the mod_jk docs don't make it terribly clear (or didn't last I checked) exactly how to set jvmRoute in Tomcat and how extraordinarily critical this is when doing load balancing. The Tomcat docs don't make this terribly clear either -- apart from a comment in server.xml. Most everyone I know who tries mod_jk load balancing gets hung up on this one point unless/until I give them a detailed explanation. Apart from the lack of clear/obvious information on this in the mod_jk docs (which should include it considering most folk won't think to check both mod_jk and Tomcat docs), this is actually very simple as well, though. None of the configuration steps in and of itself are difficult. Building mod_jk is not difficult. Editing configuration files is not difficult. Its after you've put it all together, exactly as noted on a hodge-podge of Googled URLs, and it doesn't work, and one cryptic line in a log file, and the right connections not being made between apache and tomcat, which send you into hours of trial and error. With regards to your comments above, I didn't tangle with load balancing at all, and apache and tomcat reside on the same box, no firewall between them. Yes, you'd think this would be simple. I am looking forward to mod_proxy_ajp as it is supposed be a tiny bit faster. You say you are looking forward to mod_proxy_ajp -- does this mean its not available yet, or you just aren't using it yet? While I am glad to learn now of mod_proxy_ajp, I guess this kind of adds to my frustration a bit -- what is the way to go now and why: mod_proxy_ajp or mod_jk? Thanks for your help. Brad -- Jess Holle Brad O'Hearne wrote: mod_proxy_ajp? Yet another twist. Its just hard for me to believe that how do I integrate tomcat and apache httpd? is such a mystery / unknown. This seems like it would be question #1 on any Tomcat FAQ. So where can I found out more about mod_proxy_ajp. Is there a Tomcat resource which explains the configuration of it? Brad Bill Barker wrote: Brad O'Hearne [EMAIL PROTECTED] wrote in message news: [EMAIL PROTECTED] After wasting time trying to configure mod_jk, I thought I'd just wipe my mind free and just play dumb for a moment. If Apache can proxy requests using mod_proxy, what is the benefit of using mod_jk as an integration technique between httpd and tomcat, if integration is *not* in-process, which I understand is not recommended for Tomcat 5.5? Actually, in-process with mod_jk is only supported (and, I use the term lightly :) for TC 3.3.x. For any higher versions it doesn't work at all. You've managed to grasp the deep, dark plan of the Tomcat developers: It is expected that people will migrate to mod_proxy_ajp with Httpd 2.2+, and mod_jk is expected to move to supporting IIS/SunOne only (and, the later only if somebody steps up with interest :). Brad --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Issue with ajp13 socket after tomcat shutdown
Take a look at this thread to fix this problem. http://marc.theaimsgroup.com/?l=tomcat-userm=114062756728076w=2 , Josh. -Original Message- From: Joey Geiger [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 9:24 AM To: users@tomcat.apache.org Subject: Issue with ajp13 socket after tomcat shutdown After I manually shutdown tomcat (shutdown.sh) the ajp socket seems to stay open for an extended period of time. If I attempt to restart, I get the following output in catalina.out. The problem is that ajp13 should be listening on 8889, but this port is never released, and for some odd reason, it decides to move up one. If I shutdown again, it will switch the port to 8891. I noticed another thread in the archives that discussed a similar problem, but the solution was for the apr connector. The ports do release after a waiting period, but this isn't helpful during development, and I think it might also be the cause of a few errors with tomcat restarting on it's own. (The site seems unavailable but it's just not listening on the correct port) Any help is appreciated. Thank you. Subject: RE: Re: Re: APR Connector Shutdown Problem From: Fenlason, Josh jfenlason () ptc ! com Date: 2006-01-31 22:45:57 ... I added the following line to tomcat-native.1.1.1/jni/native/src/network.c (added at line 388): apr_socket_opt_set( s, APR_SO_REUSEADDR, 1 ); But I'm still running into the same problem. Feb 24, 2006 9:29:02 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: The Apache Portable Runtime which allows optimal performance in production environments was not found on the java.library.path: /usr/local/jdk1.5.0_05/jre/lib/i386/server:/usr/local/jdk1.5.0 _05/jre/lib/i386:/usr/local/jdk1.5.0_05/jre/../lib/i386 Feb 24, 2006 9:29:03 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1190 ms Feb 24, 2006 9:29:03 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Feb 24, 2006 9:29:03 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.12 Feb 24, 2006 9:29:03 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled AbandonedObjectPool is used ([EMAIL PROTECTED]) LogAbandoned: false RemoveAbandoned: true RemoveAbandonedTimeout: 300 Feb 24, 2006 9:29:30 AM org.apache.jk.common.ChannelSocket init INFO: Port busy 8889 java.net.BindException: Address already in use Feb 24, 2006 9:29:30 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8890 Feb 24, 2006 9:29:30 AM org.apache.jk.server.JkMain start INFO: Jk running ID=1 time=0/170 config=null Feb 24, 2006 9:29:30 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 27445 ms - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
The following connector exists in the Tomcat 5.5.15 OOTB server.xml. !-- Define an AJP 1.3 Connector on port 8009 -- Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / I think that is all you need on the Tomcat side. , Josh. -Original Message- From: Brad O'Hearne [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 9:14 AM To: Tomcat Users List Subject: Re: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?) Josh, Thanks a lot for your answer. I am using Apache 2.2.x. Now onto my next question. Bill Barker suggested the httpd.conf / mod_proxy_ajp directive side of the equation. Doesn't there have to be a connector in tomcat's server.xml which will allow listening for the ajp protocol? Is there documentation on this somewhere? Brad On Feb 24, 2006, at 8:07 AM, Fenlason, Josh wrote: That depends if you want to use Apache 2.0.x, Apache 2.2.x, or some other web server (i.e. IIS). If you're planning on using Apache 2.2.x, mod_proxy_ajp is the way to go. For anything else, mod_jk is the way to go. , Josh. -Original Message- From: Brad O'Hearne [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 9:02 AM To: Tomcat Users List Subject: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?) I suppose this question deserved its own thread. Before I spend any more time trying to get this configured, I would like to know what is the best way to proceed: mod_jk or mod_proxy_ajp? Thanks, Brad On Feb 24, 2006, at 7:49 AM, Brad O'Hearne wrote: Jess, Thanks for the reply. Responses below: On Feb 24, 2006, at 6:51 AM, Jess Holle wrote: If you're using Apache 1.3.x or 2.0.x, mod_jk is pretty simple overall. No, you don't want to even try in-process stuff and, yes, if you have a firewall in between Apache and Tomcat that drops idle connections you should read carefully (this is covered by the docs). The only big complaint I have is that the mod_jk docs don't make it terribly clear (or didn't last I checked) exactly how to set jvmRoute in Tomcat and how extraordinarily critical this is when doing load balancing. The Tomcat docs don't make this terribly clear either -- apart from a comment in server.xml. Most everyone I know who tries mod_jk load balancing gets hung up on this one point unless/until I give them a detailed explanation. Apart from the lack of clear/obvious information on this in the mod_jk docs (which should include it considering most folk won't think to check both mod_jk and Tomcat docs), this is actually very simple as well, though. None of the configuration steps in and of itself are difficult. Building mod_jk is not difficult. Editing configuration files is not difficult. Its after you've put it all together, exactly as noted on a hodge-podge of Googled URLs, and it doesn't work, and one cryptic line in a log file, and the right connections not being made between apache and tomcat, which send you into hours of trial and error. With regards to your comments above, I didn't tangle with load balancing at all, and apache and tomcat reside on the same box, no firewall between them. Yes, you'd think this would be simple. I am looking forward to mod_proxy_ajp as it is supposed be a tiny bit faster. You say you are looking forward to mod_proxy_ajp -- does this mean its not available yet, or you just aren't using it yet? While I am glad to learn now of mod_proxy_ajp, I guess this kind of adds to my frustration a bit -- what is the way to go now and why: mod_proxy_ajp or mod_jk? Thanks for your help. Brad -- Jess Holle Brad O'Hearne wrote: mod_proxy_ajp? Yet another twist. Its just hard for me to believe that how do I integrate tomcat and apache httpd? is such a mystery / unknown. This seems like it would be question #1 on any Tomcat FAQ. So where can I found out more about mod_proxy_ajp. Is there a Tomcat resource which explains the configuration of it? Brad Bill Barker wrote: Brad O'Hearne [EMAIL PROTECTED] wrote in message news: [EMAIL PROTECTED] After wasting time trying to configure mod_jk, I thought I'd just wipe my mind free and just play dumb for a moment. If Apache can proxy requests using mod_proxy, what is the benefit of using mod_jk as an integration technique between httpd and tomcat, if integration is *not* in-process, which I understand is not recommended for Tomcat 5.5? Actually, in-process with mod_jk is only supported (and, I use the term lightly :) for TC 3.3.x. For any higher versions it doesn't work at all. You've managed to grasp the deep, dark plan of the Tomcat developers: It is expected that people will migrate to mod_proxy_ajp with Httpd 2.2
RE: default Tomcat 5.5 won't shutdown cleanly (Was: After adding mod_jk, tomcat won't shutdown cleanly)
Are you using the native apr connector? , Josh. -Original Message- From: Brad O'Hearne [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 11:50 AM To: Tomcat Users List Subject: default Tomcat 5.5 won't shutdown cleanly (Was: After adding mod_jk, tomcat won't shutdown cleanly) I guess I have to alter my original assertion. Vanilla tomcat 5.5 isn't shutting down cleanly (default server.xml). Are there known causes for this? Anything in particular that I need to check? Brad Brad O'Hearne wrote: Ok, it appears I may have mod_jk running properly. However, now when I try to shutdown tomcat, I get the following: Using CATALINA_BASE: /opt/apache-tomcat-5.5.12 Using CATALINA_HOME: /opt/apache-tomcat-5.5.12 Using CATALINA_TMPDIR: /opt/apache-tomcat-5.5.12/temp Using JRE_HOME: /usr/java/j2sdk1.4.2_10 Created MBeanServer with ID: 1f436f5:1099d0fba63:-8000:cvs.cvs:1 But it never returns. It just sits there, indefinitely. The java process never quits, and is still hung out there. My erver.xml is below. Is there a known problem with shutdowns after adding mod_jk? Any workarounds? Brad: server.xml: Server port=8005 shutdown=SHUTDOWN !-- Comment these entries out to disable JMX MBeans support used for the administration web application -- Listener className=org.apache.catalina.core.AprLifecycleListener / Listener className=org.apache.catalina.mbeans.ServerLifecycleListener / Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleList ener / Listener className=org.apache.catalina.storeconfig.StoreConfigLifecycleLis tener/ !-- Global JNDI resources -- GlobalNamingResources !-- Test entry for demonstration purposes -- Environment name=simpleValue type=java.lang.Integer value=30/ !-- Editable user database that can also be used by UserDatabaseRealm to authenticate users -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved factory=org.apache.catalina.users.MemoryUserDatabaseFactory pathname=conf/tomcat-users.xml / /GlobalNamingResources Service name=Tomcat-Apache Connector address=127.0.0.1 port=8009 enableLookups=false protocol=AJP/1.3 / Engine name=engine_appserver defaultHost=cvs.mydomain.lcl Host name=cvs.adeq.lcl appBase=/srv/tomcat/webapps/cvs.mydomain.lcl/docs autoDeploy=true deployOnStartup=true unpackWARs=true deployXML=false / /Engine /Service /Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] W - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using APR with tomcat leaves port 8009 bound when tomcat is terminated?
I had the same problem and submitted a patch (with help from Bill Barker). The patch is below and I attached the thread Bill and I had to come to it in case your curious. You'll have to rebuild the native connector, but this should solve your problem. What platform are you on? Did you build the native connector yourself? Or where did you get the binary from? Remy or anyone else working on the native connector, I'm not the only one who has seen this problem and obviously the Java code isn't doing what you expected. Any chance you of this patch getting accepted now? If not, would you be able to explain why? Thanks in advance. , Josh. bash-2.03$ diff -c network.c network.c.orig *** network.c Mon Feb 6 12:50:54 2006 --- network.c.orig Mon Feb 6 12:50:11 2006 *** *** 385,391 UNREFERENCED_STDARGS; TCN_ASSERT(sock != 0); TCN_ASSERT(s-sock != NULL); + apr_socket_opt_set( s-sock, APR_SO_REUSEADDR, 1 ); return (jint)apr_socket_bind(s-sock, a); } -Original Message- From: Sean Neeley [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 10:06 AM To: users@tomcat.apache.org Subject: Using APR with tomcat leaves port 8009 bound when tomcat is terminated? Hi, I'm using APR 1.2.2 with Tomcat 5.5.15. Occasionally I need to restart the JVM, and so I have one of my servlets call System.exit(0). When using the APR libraries with tomcat, exiting the JVM in this manor leaves port 8009 in the FIN_WAIT2 state (see netstat man page). This prevents me from starting tomcat back up immediately. I receive an error saying that the tomcat port is already bound. If I remove the APR libraries so that tomcat does not use them, I no longer encounter this problem. Can someone help? I would like to use APR, but this problem prevents me. I have already posted this issue to the APR mailing list, and they say that the problem is with tomcat. Thanks. - Sean ---BeginMessage--- Here's a patch for the native APR connector so that fixes problems binding on restart (see attached thread for more details). Thanks go out to Bill Barker for coming up with this. I've tested this on Windows, Solaris, and AIX and it works fine. It would be great if this could be included in the 1.1.2 native connector. Thanks. , Josh. bash-2.03$ diff -c network.c network.c.orig *** network.c Mon Feb 6 12:50:54 2006 --- network.c.orig Mon Feb 6 12:50:11 2006 *** *** 385,391 UNREFERENCED_STDARGS; TCN_ASSERT(sock != 0); TCN_ASSERT(s-sock != NULL); - apr_socket_opt_set( s-sock, APR_SO_REUSEADDR, 1 ); return (jint)apr_socket_bind(s-sock, a); } --- 385,390 ---BeginMessage--- I was doing a cut-and paste from the code in Httpd. In tcnative, 's' is it's internal socket structure, and the APR socket is s-sock. Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I added the following line to tomcat-native.1.1.1/jni/native/src/network.c (added at line 388): apr_socket_opt_set( s, APR_SO_REUSEADDR, 1 ); But I'm still running into the same problem. Does anyone who works on the APR Connector have any input on this? Or do I need to post this issue on the dev list? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Monday, January 30, 2006 10:07 PM To: users@tomcat.apache.org Subject: Re: Re: APR Connector Shutdown Problem Not by me, I don't really work on the APR Connector ;-). In the bind method in network.c is probably easiest. If you want your patch to be accepted by the dev team, then you should probably wrap it in a '#ifndef WIN32' like httpd does (don't know why, and care even less :). Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Is there no intent to fix this issue? Where would I need to make that patch? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, January 27, 2006 8:59 PM To: users@tomcat.apache.org Subject: Re: APR Connector Shutdown Problem Yeah, the difference is that Httpd calls: apr_socket_opt_set(s, APR_SO_REUSEADDR, one); on the Socket before binding it. That allows it to bind even though there are still half-closed sockets on systems like Solaris. About the only work-around is to hack the tcnative code, and recompile it. Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I added the Listener you mentioned to server.xml, but I'm still seeing the issue. The problem is happening when run the shutdown.sh. I can understand if things aren't all clean and tidy if Tomcat crashed, but you shouldn't have to wait 4 minutes to restart Tomcat after a planned shutdown. Apache doesn't work like that. Any other suggestions on how to get this to shutdown properly? Thanks in advance
RE: Re: Re: Re: APR Connector Shutdown Problem
That seems to have done the trick. Thanks for your help Bill! , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, February 03, 2006 9:50 PM To: users@tomcat.apache.org Subject: Re: Re: Re: APR Connector Shutdown Problem I was doing a cut-and paste from the code in Httpd. In tcnative, 's' is it's internal socket structure, and the APR socket is s-sock. Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I added the following line to tomcat-native.1.1.1/jni/native/src/network.c (added at line 388): apr_socket_opt_set( s, APR_SO_REUSEADDR, 1 ); But I'm still running into the same problem. Does anyone who works on the APR Connector have any input on this? Or do I need to post this issue on the dev list? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Monday, January 30, 2006 10:07 PM To: users@tomcat.apache.org Subject: Re: Re: APR Connector Shutdown Problem Not by me, I don't really work on the APR Connector ;-). In the bind method in network.c is probably easiest. If you want your patch to be accepted by the dev team, then you should probably wrap it in a '#ifndef WIN32' like httpd does (don't know why, and care even less :). Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Is there no intent to fix this issue? Where would I need to make that patch? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, January 27, 2006 8:59 PM To: users@tomcat.apache.org Subject: Re: APR Connector Shutdown Problem Yeah, the difference is that Httpd calls: apr_socket_opt_set(s, APR_SO_REUSEADDR, one); on the Socket before binding it. That allows it to bind even though there are still half-closed sockets on systems like Solaris. About the only work-around is to hack the tcnative code, and recompile it. Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I added the Listener you mentioned to server.xml, but I'm still seeing the issue. The problem is happening when run the shutdown.sh. I can understand if things aren't all clean and tidy if Tomcat crashed, but you shouldn't have to wait 4 minutes to restart Tomcat after a planned shutdown. Apache doesn't work like that. Any other suggestions on how to get this to shutdown properly? Thanks in advance. , Josh. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 1:24 AM To: Tomcat Users List Subject: Re: APR Connector Shutdown Problem Fenlason, Josh wrote: I'm running into a problem with the APR connector not shutting down properly. Tomcat runs fine and there are no errors on shutdown, but if I shut Tomcat down and start it up again I get a socket bind failed error in the catalina log (attached). I have to wait for several minutes between shutdown and startup for Tomcat to be able to startup correctly. If I run Tomcat without the APR connector, I don't have this issue. This does not occur on Windows, but does on Solaris and AIX. Has anyone else seen this? One thing I noticed is that the first thing logged on shutdown is an AjpAprProtocol pause entry, but there is no shutdown, stop or destroy. Is there any chance the APR connector is just getting paused and nothing is actually stopping it? Any help would be greatly appreciated. Thanks in advance. I suppose you have: Listener className=org.apache.catalina.core.AprLifecycleListener / in your server.xml But of course it doesn't guarantee it will be executed in all cases, if the JVM crashes for example. On Solaris it can take up to 4 minutes until the OS recycles the zombie socket. You can use: ndd -set /dev/tcp tcp_time_wait_interval 6 To lower that value. APR does not try to fool the OS like JVM, but rather behaves like Apache httpd. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL
RE: Re: Re: APR Connector Shutdown Problem
I added the following line to tomcat-native.1.1.1/jni/native/src/network.c (added at line 388): apr_socket_opt_set( s, APR_SO_REUSEADDR, 1 ); But I'm still running into the same problem. Does anyone who works on the APR Connector have any input on this? Or do I need to post this issue on the dev list? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Monday, January 30, 2006 10:07 PM To: users@tomcat.apache.org Subject: Re: Re: APR Connector Shutdown Problem Not by me, I don't really work on the APR Connector ;-). In the bind method in network.c is probably easiest. If you want your patch to be accepted by the dev team, then you should probably wrap it in a '#ifndef WIN32' like httpd does (don't know why, and care even less :). Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Is there no intent to fix this issue? Where would I need to make that patch? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, January 27, 2006 8:59 PM To: users@tomcat.apache.org Subject: Re: APR Connector Shutdown Problem Yeah, the difference is that Httpd calls: apr_socket_opt_set(s, APR_SO_REUSEADDR, one); on the Socket before binding it. That allows it to bind even though there are still half-closed sockets on systems like Solaris. About the only work-around is to hack the tcnative code, and recompile it. Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I added the Listener you mentioned to server.xml, but I'm still seeing the issue. The problem is happening when run the shutdown.sh. I can understand if things aren't all clean and tidy if Tomcat crashed, but you shouldn't have to wait 4 minutes to restart Tomcat after a planned shutdown. Apache doesn't work like that. Any other suggestions on how to get this to shutdown properly? Thanks in advance. , Josh. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 1:24 AM To: Tomcat Users List Subject: Re: APR Connector Shutdown Problem Fenlason, Josh wrote: I'm running into a problem with the APR connector not shutting down properly. Tomcat runs fine and there are no errors on shutdown, but if I shut Tomcat down and start it up again I get a socket bind failed error in the catalina log (attached). I have to wait for several minutes between shutdown and startup for Tomcat to be able to startup correctly. If I run Tomcat without the APR connector, I don't have this issue. This does not occur on Windows, but does on Solaris and AIX. Has anyone else seen this? One thing I noticed is that the first thing logged on shutdown is an AjpAprProtocol pause entry, but there is no shutdown, stop or destroy. Is there any chance the APR connector is just getting paused and nothing is actually stopping it? Any help would be greatly appreciated. Thanks in advance. I suppose you have: Listener className=org.apache.catalina.core.AprLifecycleListener / in your server.xml But of course it doesn't guarantee it will be executed in all cases, if the JVM crashes for example. On Solaris it can take up to 4 minutes until the OS recycles the zombie socket. You can use: ndd -set /dev/tcp tcp_time_wait_interval 6 To lower that value. APR does not try to fool the OS like JVM, but rather behaves like Apache httpd. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Re: APR Connector Shutdown Problem
Is there no intent to fix this issue? Where would I need to make that patch? Thanks. , Josh. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, January 27, 2006 8:59 PM To: users@tomcat.apache.org Subject: Re: APR Connector Shutdown Problem Yeah, the difference is that Httpd calls: apr_socket_opt_set(s, APR_SO_REUSEADDR, one); on the Socket before binding it. That allows it to bind even though there are still half-closed sockets on systems like Solaris. About the only work-around is to hack the tcnative code, and recompile it. Fenlason, Josh [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I added the Listener you mentioned to server.xml, but I'm still seeing the issue. The problem is happening when run the shutdown.sh. I can understand if things aren't all clean and tidy if Tomcat crashed, but you shouldn't have to wait 4 minutes to restart Tomcat after a planned shutdown. Apache doesn't work like that. Any other suggestions on how to get this to shutdown properly? Thanks in advance. , Josh. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 1:24 AM To: Tomcat Users List Subject: Re: APR Connector Shutdown Problem Fenlason, Josh wrote: I'm running into a problem with the APR connector not shutting down properly. Tomcat runs fine and there are no errors on shutdown, but if I shut Tomcat down and start it up again I get a socket bind failed error in the catalina log (attached). I have to wait for several minutes between shutdown and startup for Tomcat to be able to startup correctly. If I run Tomcat without the APR connector, I don't have this issue. This does not occur on Windows, but does on Solaris and AIX. Has anyone else seen this? One thing I noticed is that the first thing logged on shutdown is an AjpAprProtocol pause entry, but there is no shutdown, stop or destroy. Is there any chance the APR connector is just getting paused and nothing is actually stopping it? Any help would be greatly appreciated. Thanks in advance. I suppose you have: Listener className=org.apache.catalina.core.AprLifecycleListener / in your server.xml But of course it doesn't guarantee it will be executed in all cases, if the JVM crashes for example. On Solaris it can take up to 4 minutes until the OS recycles the zombie socket. You can use: ndd -set /dev/tcp tcp_time_wait_interval 6 To lower that value. APR does not try to fool the OS like JVM, but rather behaves like Apache httpd. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: APR Connector Shutdown Problem
I added the Listener you mentioned to server.xml, but I'm still seeing the issue. The problem is happening when run the shutdown.sh. I can understand if things aren't all clean and tidy if Tomcat crashed, but you shouldn't have to wait 4 minutes to restart Tomcat after a planned shutdown. Apache doesn't work like that. Any other suggestions on how to get this to shutdown properly? Thanks in advance. , Josh. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 1:24 AM To: Tomcat Users List Subject: Re: APR Connector Shutdown Problem Fenlason, Josh wrote: I'm running into a problem with the APR connector not shutting down properly. Tomcat runs fine and there are no errors on shutdown, but if I shut Tomcat down and start it up again I get a socket bind failed error in the catalina log (attached). I have to wait for several minutes between shutdown and startup for Tomcat to be able to startup correctly. If I run Tomcat without the APR connector, I don't have this issue. This does not occur on Windows, but does on Solaris and AIX. Has anyone else seen this? One thing I noticed is that the first thing logged on shutdown is an AjpAprProtocol pause entry, but there is no shutdown, stop or destroy. Is there any chance the APR connector is just getting paused and nothing is actually stopping it? Any help would be greatly appreciated. Thanks in advance. I suppose you have: Listener className=org.apache.catalina.core.AprLifecycleListener / in your server.xml But of course it doesn't guarantee it will be executed in all cases, if the JVM crashes for example. On Solaris it can take up to 4 minutes until the OS recycles the zombie socket. You can use: ndd -set /dev/tcp tcp_time_wait_interval 6 To lower that value. APR does not try to fool the OS like JVM, but rather behaves like Apache httpd. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
APR Connector Shutdown Problem
Title: Message I'm running into a problem with the APR connector not shutting down properly. Tomcat runs fine and there are no errors on shutdown, but if I shut Tomcat down and start it up again I geta socketbind failed errorin the catalina log (attached). I have to wait for several minutes between shutdown and startup for Tomcat to be able to startup correctly. If I run Tomcat without the APR connector, I don't have this issue. This does not occur on Windows, but does on Solaris and AIX. Has anyone else seen this? One thing I noticed is that the first thing logged on shutdown is an "AjpAprProtocol pause" entry, but there is no shutdown, stop or destroy. Is there any chance the APR connector is just getting paused and nothing is actually stopping it? Any help would be greatly appreciated. Thanks in advance. , Josh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
apr port + tomcat
Title: Message I'm running into a problem with Tomcat 5.5.12 and tomcat-native-1.1.0. I get theexception below when I try to restart Tomcat after it has served dynamic content for Apache. If Istop both Apache and Tomcat and wait a while and restart them, they startup fine. This seems very similar to another recent post on this list, http://www.mail-archive.com/users@tomcat.apache.org/msg03327.html. I'm just calling CATALINA_HOME/bin/shutdown.sh to stop Tomcat and I don't see any errors during shutdown. Am I doing something wrong on shutdown? Or is there a bug in the shutdown process? I've only noticed this on Solaris and not on Linux and Windows. I don't experience this problem when I run Tomcat without the native connector. I've attached the complete catalina.out in case that's helpful. Thanks in advance. , Josh. Jan 4, 2006 8:33:30 AM org.apache.coyote.http11.Http11AprProtocol initSEVERE: Error initializing endpointjava.lang.Exception: Socket bind failed: 125 at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:544) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:115) at org.apache.catalina.connector.Connector.initialize(Connector.java:1016) at org.apache.catalina.core.StandardService.initialize(StandardService.java:580) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:762) at org.apache.catalina.startup.Catalina.load(Catalina.java:488) at org.apache.catalina.startup.Catalina.load(Catalina.java:508) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:247) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
