Re: Excessive CPU w/APR Connectors on tomcat-native 1.1.22
Brief follow up on CPU spike issue. In an attempt to work around the problem via configuration changes, we have swapped out APR connectors with NIO using an equivalent configuration. (The only meaningful changes are SSL configuration directives.) Since swapping out connectors over the weekend, we have not had any CPU spikes. That's long enough for me to consider it a suitable workaround. M - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Excessive CPU w/APR Connectors on tomcat-native 1.1.22
On 11/01/2012 22:42, Marvin Addison wrote: We are seeing excessive CPU burn (top 300% on multicore machine) in multiple versions of Tomcat that use APR connectors exclusively. The problem does not correlate with load. We initially saw it on 6.0.35 and subsequently on 7.0.23 as we attempted to upgrade around the problem. We have determined that the component common to both versions is tomcat-native 1.1.22. (We were not seeing this behavior on our previous component mix of 6.0.26/1.1.20.) Can you confirm whether or not the issue exists with 6.0.26 and 1.1.22? It would be helpful to try and track down which component is the root of the issue. How long do the periods of high CPU usage last? Graphs of CPU usage over time show a sharp increase when a second thread enters sendbb; conversely there is a sharp decrease as soon as all but a single thread drop out of the method. Additionally, there may be a correlation with CPU usage and the number of threads in sendbb; for example, the CPU burn may be greater when three threads are in sendbb versus two. How sure are you that the CPU is being burned in the threads that are in sendbb? Just because the CPU usage correlates with threads being in that method it doesn't necessarily mean that is where the CPU is being used. This feels like a concurrency bug: hard to reproduce, sporadic, and correlates with number of threads acting on the same code path. Please let me know if you'd like me to do anything further that may help determine whether this is, in fact, a bug. I'm happy to create a bug report if needed. Answers to the above questions would help with the analysis of this issue. Assuming that this is a concurrency issue, then code inspection is likely to be the best chance of finding the issue. If we can get to a point where we can say upgrading this one component from x.y.z to x.y.z+1 triggers the issue that will narrow down where we have to look. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Excessive CPU w/APR Connectors on tomcat-native 1.1.22
Can you confirm whether or not the issue exists with 6.0.26 and 1.1.22? I cannot. We have tried repeatedly to reproduce this problem in a test environment where such experimentation is tolerated, but the problem simply does not manifest using available load testing tools. We attempted to try 7.0.23+1.2.20 in production, but I couldn't get a working configuration for the supported SSL/TLS protocols we require. How long do the periods of high CPU usage last? Varies quite a bit. Based on data from our enterprise monitoring system, the problem lasts as little as 5 min or less and has lasted as much as 25 min. YourKit data from the incidents that have happened in the past 24h shows similarly wide variation: 2m40s 1m38s 13m11s 8s How sure are you that the CPU is being burned in the threads that are in sendbb? I'm certain of nothing, but I can share the evidence. YourKit CPU profiling data shows that request processing threads consume the majority of resources during these periods. No surprise there. However, the only method that is consistently executed during these periods is sendbb() by two or more threads. For the last problem period, which happens to be the shortest (8s), catalina-exec threads accounted for 89% of CPU use. Following are the RUNNABLE threads at 1s sample intervals during that period: Stacks at 09:11:01 AM (uptime 1 day 3:26:47) 1. catalina-exec-45 [RUNNABLE, IN_NATIVE] CPU time: 1:57 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:32 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:02 AM (uptime 1 day 3:26:48) 1. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:21 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:33 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:03 AM (uptime 1 day 3:26:49) 1. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:22 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:34 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:04 AM (uptime 1 day 3:26:50) 1. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:23 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:35 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:05 AM (uptime 1 day 3:26:51) 1. catalina-exec-38 [RUNNABLE, IN_NATIVE] CPU time: 1:28 java.net.SocketInputStream.socketRead0(FileDescriptor, byte[], int, int, int) 2. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:24 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 3. catalina-exec-44 [RUNNABLE] CPU time: 1:43 java.net.SocketInputStream.socketRead0(FileDescriptor, byte[], int, int, int) 4. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:35 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:06 AM (uptime 1 day 3:26:52) 1. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:25 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:36 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:07 AM (uptime 1 day 3:26:53) 1. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:25 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:37 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 3. catalina-exec-52 [RUNNABLE] CPU time: 0:04 java.lang.Throwable.fillInStackTrace() Stacks at 09:11:08 AM (uptime 1 day 3:26:54) 1. catalina-exec-39 [RUNNABLE, IN_NATIVE] CPU time: 1:26 org.apache.tomcat.jni.Socket.sendbb(long, int, int) 2. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:38 org.apache.tomcat.jni.Socket.sendbb(long, int, int) Stacks at 09:11:09 AM (uptime 1 day 3:26:55) 1. catalina-exec-51 [RUNNABLE, IN_NATIVE] CPU time: 13:39 org.apache.tomcat.jni.Socket.sendbb(long, int, int) After the last sample, CPU usage drops precipitously. Our application is a Web SSO product that writes relatively small response payloads. It's hard to explain two request processing threads that take several seconds to write small response payloads without citing a bug in the servlet container. M - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Excessive CPU w/APR Connectors on tomcat-native 1.1.22
We are seeing excessive CPU burn (top 300% on multicore machine) in multiple versions of Tomcat that use APR connectors exclusively. The problem does not correlate with load. We initially saw it on 6.0.35 and subsequently on 7.0.23 as we attempted to upgrade around the problem. We have determined that the component common to both versions is tomcat-native 1.1.22. (We were not seeing this behavior on our previous component mix of 6.0.26/1.1.20.) In addition to the circumstantial evidence of version changes, we have some JVM data that implicate tomcat-native. We've taken thread dumps and YourKit snapshots (w/CPU sampling enabled) during the problem periods and a consistent pattern appears: at least two connector threads are in org.apache.tomcat.jni.Socket.sendbb(long, int, int) throughout the period of CPU churn. The following instrumented thread dump of active threads is illustrative of this pattern: Stacks at 10:57:51 AM (uptime 5:13:38) catalina-exec-1 [WAITING] CPU time: 2:03 sun.misc.Unsafe.park(boolean, long) java.util.concurrent.locks.LockSupport.parkNanos(Object, long) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(long) java.util.concurrent.LinkedBlockingQueue.poll(long, TimeUnit) org.apache.tomcat.util.threads.TaskQueue.poll(long, TimeUnit) org.apache.tomcat.util.threads.TaskQueue.poll(long, TimeUnit) java.util.concurrent.ThreadPoolExecutor.getTask() java.util.concurrent.ThreadPoolExecutor$Worker.run() java.lang.Thread.run() catalina-exec-10 [RUNNABLE, IN_NATIVE] CPU time: 2:28 org.apache.tomcat.jni.Socket.sendbb(long, int, int) org.apache.coyote.http11.InternalAprOutputBuffer.flushBuffer() org.apache.coyote.http11.InternalAprOutputBuffer.access$100(InternalAprOutputBuffer) org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(ByteChunk, Response) org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(ByteChunk, Response) org.apache.coyote.http11.AbstractOutputBuffer.doWrite(ByteChunk, Response) org.apache.coyote.Response.doWrite(ByteChunk) org.apache.catalina.connector.OutputBuffer.realWriteBytes(byte[], int, int) org.apache.tomcat.util.buf.ByteChunk.append(byte[], int, int) org.apache.catalina.connector.OutputBuffer.writeBytes(byte[], int, int) org.apache.catalina.connector.OutputBuffer.write(byte[], int, int) org.apache.catalina.connector.CoyoteOutputStream.write(byte[], int, int) org.apache.catalina.servlets.DefaultServlet.copy(CacheEntry, InputStream, ServletOutputStream) org.apache.catalina.servlets.DefaultServlet.serveResource(HttpServletRequest, HttpServletResponse, boolean) org.apache.catalina.servlets.DefaultServlet.doGet(HttpServletRequest, HttpServletResponse) javax.servlet.http.HttpServlet.service(HttpServletRequest, HttpServletResponse) javax.servlet.http.HttpServlet.service(ServletRequest, ServletResponse) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) org.apache.catalina.core.ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) edu.vt.middleware.servlet.filter.RequestDumperFilter.doFilter(ServletRequest, ServletResponse, FilterChain) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) org.apache.catalina.core.ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) com.github.inspektr.common.web.ClientInfoThreadLocalFilter.doFilter(ServletRequest, ServletResponse, FilterChain) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) org.apache.catalina.core.ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) edu.vt.middleware.servlet.filter.CharacterEncodingFilter.doFilter(ServletRequest, ServletResponse, FilterChain) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) org.apache.catalina.core.ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) org.apache.catalina.core.StandardWrapperValve.invoke(Request, Response) org.apache.catalina.core.StandardContextValve.invoke(Request, Response) org.apache.catalina.authenticator.AuthenticatorBase.invoke(Request, Response) org.apache.catalina.core.StandardHostValve.invoke(Request, Response) org.apache.catalina.valves.ErrorReportValve.invoke(Request, Response) org.apache.catalina.valves.AccessLogValve.invoke(Request, Response) org.apache.catalina.core.StandardEngineValve.invoke(Request, Response) org.apache.catalina.connector.CoyoteAdapter.service(Request, Response) org.apache.coyote.http11.AbstractHttp11Processor.process(SocketWrapper) org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(SocketWrapper, SocketStatus) org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run() java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Runnable) java.util.concurrent.ThreadPoolExecutor$Worker.run() java.lang.Thread.run() catalina-exec-11 [RUNNABLE, IN_NATIVE] CPU time: 10:19 org.apache.tomcat.jni.Socket.sendbb(long, int, int)
Re: Connectors in Tomcat
Hi, Thanks Rajeev, i hadn't initialized the factory properly, now i don't get a null pointer exception, and it shows in the console that http connector is initialized and started at the port i'v given say 9002, but http is still not enabled in the sense that an html page does not run on http://localhost:90002/welcome.html I have initialized the factory as: factory = new MBeanFactory(); and then called the createHttpConnector( Catalina:type=Service,serviceName=Catalina, 127.0.0.1, 9002);
Re: Connectors in Tomcat
Hi, I would like to know how to link this new factory with the service Catalina. Because on checking with the JConsole, the attributes of this factory do not match with the existing one. Hence the connector is not created with the same factory and the code doesn't work. -Hemali
Re: Connectors in Tomcat
On 01/04/2010 06:33, Hemali Doshi wrote: Hi, i wanted to create an https connector on a port other than 8443. There is a method to create HttpsConnector in MBeanFactory. Could anyone kindly tell me how to use this method and what parameters to pass? Did you read the JavaDoc or look at the source code? Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Connectors in Tomcat
Yes, i did look at the source code. But there is a parameter called parent in createHttpsConnector method. I am unable to find the parent, I tried passing Catalina,StandardEngine, etc. It gives me a null pointer exception for whatever parent name I pass. Thanks. -Hemali
Re: Connectors in Tomcat
On 01/04/2010 09:30, Hemali Doshi wrote: Yes, i did look at the source code. But there is a parameter called parent in createHttpsConnector method. I am unable to find the parent, I tried passing Catalina,StandardEngine, etc. It gives me a null pointer exception for whatever parent name I pass. You need to the MBean name for the parent service. You can connect to a running Tomcat instance with JConsole to see what the name is. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Connectors in Tomcat
On 01/04/2010 11:45, Hemali Doshi wrote: Hi, We ran jconsole and found the the service is catalina and the mbean name is Catalina:type=Service,serviceName=Catalina. but still the program is giving null pointer exception. other two parameters have been passed as ip address of my machine and port as say 8443. Do you know what the problem is? My crystal ball isn't working too well today. Given that you haven't provided: - Platform - JDK version - Tomcat version - the stack trace how do you expect people here to be able to answer that question? I suggest you try reading http://www.catb.org/~esr/faqs/smart-questions.html Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Connectors in Tomcat
On Thu, Apr 1, 2010 at 4:42 PM, Hemali Doshi hemalido...@gmail.com wrote: We are using Tomcat 6.0.18 with jdk 1.5 on Windows XP. line 118 is: factory.createHttpsConnector(Catalina:type=Service,serviceName=Catalina, 127.0.0.1, 8443); * Have you instantiated the 'factory' properly? The stack trace is as follows: java.lang.NullPointerException * at toggle1.doPost(*toggle1.java:118*) at javax.servlet.http.HttpServlet.service(*HttpServlet.java:637*) at javax.servlet.http.HttpServlet.service(*HttpServlet.java:717*) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(* ApplicationFilterChain.java:290*) at org.apache.catalina.core.ApplicationFilterChain.doFilter(* ApplicationFilterChain.java:206*) at org.apache.catalina.core.StandardWrapperValve.invoke(* StandardWrapperValve.java:233*) at org.apache.catalina.core.StandardContextValve.invoke(* StandardContextValve.java:191*) at org.apache.catalina.core.StandardHostValve.invoke(* StandardHostValve.java:128*) at org.apache.catalina.valves.ErrorReportValve.invoke(* ErrorReportValve.java:102*) at org.apache.catalina.core.StandardEngineValve.invoke(* StandardEngineValve.java:109*) at org.apache.catalina.connector.CoyoteAdapter.service(* CoyoteAdapter.java:293*) at org.apache.coyote.http11.Http11Processor.process(* Http11Processor.java:849*) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(* Http11Protocol.java:583*) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(*JIoEndpoint.java:454*) at java.lang.Thread.run(Unknown Source) -Hemali
Connectors in Tomcat
Hi, i wanted to create an https connector on a port other than 8443. There is a method to create HttpsConnector in MBeanFactory. Could anyone kindly tell me how to use this method and what parameters to pass? Thanks for your help. -Hemali
Apache connectors for tomcat
Hi, Which is the recommended connector for Apache now? mod_jk or mod_proxy_ajp (with balancer) ? rahul -- 1. e4 _ - 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: Apache connectors for tomcat
personal preference in this order mod_proxy_http, mod_jk, mod_proxy_ajp rahul wrote: Hi, Which is the recommended connector for Apache now? mod_jk or mod_proxy_ajp (with balancer) ? rahul -- 1. e4 _ - 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: Apache connectors for tomcat
Not sure about the interface/protocol being depricated since there was just a new release of mod_jk 1.2.25? Also, someone put some effort into improvments into it 2.2.6 of Apache. I also noticed a 10% performance improvement in request response times using mod_jk which I was told about and proven for my web services implementation using Tomcat. Finally what to do about load balanceing if Mod_jk goes away does someone have an answer to that? Regards, -Tony --- Charlie Wingate [EMAIL PROTECTED] wrote: You may find this link helpful.it works if your using the same versions as the article. But I think JK2 has been 'deprecated'. http://www.roktech.net/devblog/enclosures/iis6-Tomcat5-JK2.pdf ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 3:25 AM To: users@tomcat.apache.org Subject: Apache connectors for tomcat Hi, Which is the recommended connector for Apache now? mod_jk or mod_proxy_ajp (with balancer) ? rahul -- 1. e4 _ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. --- This message is a CONFIDENTIAL communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz - 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: Apache connectors for tomcat
You may find this link helpful.it works if your using the same versions as the article. But I think JK2 has been 'deprecated'. http://www.roktech.net/devblog/enclosures/iis6-Tomcat5-JK2.pdf ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 3:25 AM To: users@tomcat.apache.org Subject: Apache connectors for tomcat Hi, Which is the recommended connector for Apache now? mod_jk or mod_proxy_ajp (with balancer) ? rahul -- 1. e4 _ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. --- This message is a CONFIDENTIAL communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. - 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: Apache connectors for tomcat
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: personal preference in this order mod_proxy_http, mod_jk, mod_proxy_ajp I'm interested: why choose mod_proxy_http over mod_jk? ease of configuration, no API nor configuration incompatibilities between dot (.) releases, text protocol, easier to debug, better socket handling (uses APR), ability to use smart load balancing (through appliances in between) since it uses the HTTP protocol(otherwise you can just LB TCP sessions), speed difference has been so small, that it doesn't outweigh the other pros. again, just personal opionions Filip - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/SZ19CaO5/Lv0PARAsm5AJ47ndEuIqfmT9LHA27Kl17MI13lhgCggyzy UVl1HP68RySRkjuxjAKBb9M= =rFt2 -END PGP SIGNATURE- - 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: Apache connectors for tomcat
I'm confused.Doesn't mod_jk use ajp1.3 on the tomcat side? Was that with or without the native runtime library? ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: Tony Anecito [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 12:56 PM To: Tomcat Users List Subject: Re: Apache connectors for tomcat I had heard that mod_jk was faster so I switched from ajp to mod_jk and sure enough mod_jk was 10% faster for me. -Tony --- Christopher Schultz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: personal preference in this order mod_proxy_http, mod_jk, mod_proxy_ajp I'm interested: why choose mod_proxy_http over mod_jk? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/SZ19CaO5/Lv0PARAsm5AJ47ndEuIqfmT9LHA27Kl17MI13lhgCggyzy UVl1HP68RySRkjuxjAKBb9M= =rFt2 -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. --- This message is a CONFIDENTIAL communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. - 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: Apache connectors for tomcat
Charlie Wingate wrote: I'm confused.Doesn't mod_jk use ajp1.3 on the tomcat side? Was that with or without the native runtime library? 1) mod_jk uses the protocol AJP 2) On the Tomcat side, there is a pure Java AJP connector, and a native one (called APR connector). You can choose. 3) Most likly (?) Tony meant from mod_proxy_ajp to mod_jk, although I would not expect a big performance difference between those two. The biggest difference between mod_jk and mod_proxy_ajp/mod_proxy_balancer at the moment in my opinion is - mod_jk gets released more often because it's independantly released, so it's easier for us to add features and fix bugs - mod_jk has more options to handle more complicated backend topologies - mod_proxy_* is easier to understand for simple configurations - mod_proxy_* has the advantage of automatically being installed on nearly all systems which have Apache httpd 2.2. Regards, Rainer ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: Tony Anecito [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 12:56 PM To: Tomcat Users List Subject: Re: Apache connectors for tomcat I had heard that mod_jk was faster so I switched from ajp to mod_jk and sure enough mod_jk was 10% faster for me. -Tony - 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: Apache connectors for tomcat
From: Tony Anecito [mailto:[EMAIL PROTECTED] Subject: RE: Apache connectors for tomcat Not sure about the interface/protocol being depricated It's mod_jk2 that has been abandoned for over two years; mod_jk is still in very active development. Any documentation or recommendations for mod_jk2 are sadly out of date. - 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. - 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: Apache connectors for tomcat
Thanks for the clarification. -Tony --- Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Tony Anecito [mailto:[EMAIL PROTECTED] Subject: RE: Apache connectors for tomcat Not sure about the interface/protocol being depricated It's mod_jk2 that has been abandoned for over two years; mod_jk is still in very active development. Any documentation or recommendations for mod_jk2 are sadly out of date. - 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. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.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]
RE: Apache connectors for tomcat
Mod_jk and Mod_jk2 are different animals..JK2 is deprecated. The reason I mention it is that it is easy to assume that JK2 is the latest and greatest given the naming convention. Mod_jk 1.2.25 was released late july and IS the latest in the mod_jk project; to my knowledge anyway. ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: Tony Anecito [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 10:19 AM To: Tomcat Users List Subject: RE: Apache connectors for tomcat Not sure about the interface/protocol being depricated since there was just a new release of mod_jk 1.2.25? Also, someone put some effort into improvments into it 2.2.6 of Apache. I also noticed a 10% performance improvement in request response times using mod_jk which I was told about and proven for my web services implementation using Tomcat. Finally what to do about load balanceing if Mod_jk goes away does someone have an answer to that? Regards, -Tony --- Charlie Wingate [EMAIL PROTECTED] wrote: You may find this link helpful.it works if your using the same versions as the article. But I think JK2 has been 'deprecated'. http://www.roktech.net/devblog/enclosures/iis6-Tomcat5-JK2.pdf ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 3:25 AM To: users@tomcat.apache.org Subject: Apache connectors for tomcat Hi, Which is the recommended connector for Apache now? mod_jk or mod_proxy_ajp (with balancer) ? rahul -- 1. e4 _ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. --- This message is a CONFIDENTIAL communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. --- This message is a CONFIDENTIAL communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e
Re: Apache connectors for tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: personal preference in this order mod_proxy_http, mod_jk, mod_proxy_ajp I'm interested: why choose mod_proxy_http over mod_jk? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/SZ19CaO5/Lv0PARAsm5AJ47ndEuIqfmT9LHA27Kl17MI13lhgCggyzy UVl1HP68RySRkjuxjAKBb9M= =rFt2 -END PGP SIGNATURE- - 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: Apache connectors for tomcat
I had heard that mod_jk was faster so I switched from ajp to mod_jk and sure enough mod_jk was 10% faster for me. -Tony --- Christopher Schultz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: personal preference in this order mod_proxy_http, mod_jk, mod_proxy_ajp I'm interested: why choose mod_proxy_http over mod_jk? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/SZ19CaO5/Lv0PARAsm5AJ47ndEuIqfmT9LHA27Kl17MI13lhgCggyzy UVl1HP68RySRkjuxjAKBb9M= =rFt2 -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting - 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: Apache connectors for tomcat
Hi Charlie, I heard that mod_jk was based off of ajp so I was quite surprised mod_jk was faster. Not sure how to answer your question regarding the native runtime library since all I did was download the module file for mod_jk and comment out the ajp proxy module. Regards, -Tony --- Charlie Wingate [EMAIL PROTECTED] wrote: I'm confused.Doesn't mod_jk use ajp1.3 on the tomcat side? Was that with or without the native runtime library? ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: Tony Anecito [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 12:56 PM To: Tomcat Users List Subject: Re: Apache connectors for tomcat I had heard that mod_jk was faster so I switched from ajp to mod_jk and sure enough mod_jk was 10% faster for me. -Tony --- Christopher Schultz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: personal preference in this order mod_proxy_http, mod_jk, mod_proxy_ajp I'm interested: why choose mod_proxy_http over mod_jk? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/SZ19CaO5/Lv0PARAsm5AJ47ndEuIqfmT9LHA27Kl17MI13lhgCggyzy UVl1HP68RySRkjuxjAKBb9M= =rFt2 -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. --- This message is a CONFIDENTIAL communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. http://autos.yahoo.com/index.html - 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: Apache connectors for tomcat
Hi Rainer, I am not sure if JBoss embedded Tomcat uses the native ajp but a great point. Do you know how to check for that? Also, you need to keep in mind the scale of things. In other words my measurements at the client side are in the 4 millisecond range. Depending how long the data takes to get through communications stack on the server then to the client comm stack we might actually only be seeing a millisecond or two at Tomcat. Normally overall transaction improvements of a millisecond do not matter to most people ;-) Regards, Tony Anecito, Founder MyUniPortal --- Rainer Jung [EMAIL PROTECTED] wrote: Charlie Wingate wrote: I'm confused.Doesn't mod_jk use ajp1.3 on the tomcat side? Was that with or without the native runtime library? 1) mod_jk uses the protocol AJP 2) On the Tomcat side, there is a pure Java AJP connector, and a native one (called APR connector). You can choose. 3) Most likly (?) Tony meant from mod_proxy_ajp to mod_jk, although I would not expect a big performance difference between those two. The biggest difference between mod_jk and mod_proxy_ajp/mod_proxy_balancer at the moment in my opinion is - mod_jk gets released more often because it's independantly released, so it's easier for us to add features and fix bugs - mod_jk has more options to handle more complicated backend topologies - mod_proxy_* is easier to understand for simple configurations - mod_proxy_* has the advantage of automatically being installed on nearly all systems which have Apache httpd 2.2. Regards, Rainer ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein -Original Message- From: Tony Anecito [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 12:56 PM To: Tomcat Users List Subject: Re: Apache connectors for tomcat I had heard that mod_jk was faster so I switched from ajp to mod_jk and sure enough mod_jk was 10% faster for me. -Tony - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Check out the hottest 2008 models today at Yahoo! Autos. http://autos.yahoo.com/new_cars.html - 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: Apache connectors for tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony, Tony Anecito wrote: I heard that mod_jk was based off of ajp so I was quite surprised mod_jk was faster. Yes, mod_jk does use the AJP protocol. Why were you surprised that it was faster? With what are you comparing it? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/VfY9CaO5/Lv0PARAjvKAJ9sZhZby/qVSlh/NMbnyxpfjbbkuwCgnFiZ MSudRIHxnN741iQm0jpYDCc= =DDyM -END PGP SIGNATURE- - 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: Apache connectors for tomcat
Hi Chris: 1. I am instrumenting inside the servlet code, looking at Apache web server logs then at the Rich Internet Application (RIA) For a typcial request for my Portal from client to servlet for example: 1. 4.55msec inside the RIA java code after the data was read from the SOAP message. 2. 0 microseconds read in the Apache Web Server logs 3. Under a microsecond in the servlet code for the service method. I have a multi-tier caching system so most of the request/responses are under 1500 bytes or the size of a single packet. Even if there is a cache miss most of the requests are still under 1500 bytes after compression by JAXWS web service code. Hope that helps. Tony Anecito, Founder MyUniPortal --- Christopher Schultz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony, Tony Anecito wrote: I am not sure if JBoss embedded Tomcat uses the native ajp but a great point. Do you know how to check for that? Since JBoss uses Tomcat, it can use any of the standard connectors available for it (basically HTTP(s) and/or AJP). Also, you need to keep in mind the scale of things. In other words my measurements at the client side are in the 4 millisecond range. Depending how long the data takes to get through communications stack on the server then to the client comm stack we might actually only be seeing a millisecond or two at Tomcat. Huh? I thought you were instrumenting your code within Tomcat resulting in 4ms transaction times, and you now wanted to know how much overhead was being added (on top of that) to the transaction by the other components. Is that not the case? Normally overall transaction improvements of a millisecond do not matter to most people ;-) Actually, if your transactions are taking 4ms and you can shave off 1ms, then that's a 25% performance improvement. If your transactions are taking 300ms, perhaps 1ms isn't that big of a deal. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG/Vek9CaO5/Lv0PARAkIBAJ0eGaHoEU+wDdEOYT4pXtvVOvUMhQCfWhXP 60oVc48I2SGWCqZHXVk4B0o= =WYdf -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV. http://tv.yahoo.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]
Page cannot be displayed with ssl/https connectors and Tomcat 5.5.12
Hi, I upgraded from Tomcat 5.5.9 to Tomcat 5.5.12 and cannot get https connectors to work. Here is an extract from my server.xml Connector port=443 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=false sslProtocol=TLS keystoreFile=c:\Documents and Settings\Owner\.keystore keystorePass=mypassword / It was working fine with Tomcat 5.5.9 I am using Windows XP with Service Pack 2. I tried it on both Internet Explorer 6 and Firefox. Thanks Jean-Pierre Pelletier e-djuster - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
