web page rendering is slow
Hi SPEC JDK 1.5 TOMCAT 5.x (JBOSS Embedded) OS : LINUX Problem Our application caters to B2C process with embedded with 3rd party URL's for Advertisement process in display How ever some times this URL's are slow in response, hence our web page rendering is slow Is there any way to solve this issue? Note: - Need to have the 3rd party URL for sponsorship With regards N.S.Karthik
Re: web page rendering is slow
On 13/04/2010 08:53, Karthik Nanjangude wrote: Hi SPEC JDK 1.5 TOMCAT 5.x (JBOSS Embedded) OS : LINUX Problem Our application caters to B2C process with embedded with 3rd party URL's for Advertisement process in display How ever some times this URL's are slow in response, hence our web page rendering is slow How are you including the content from the URL? Is there any way to solve this issue? Note: - Need to have the 3rd party URL for sponsorship Embed them in an iframe. p With regards N.S.Karthik - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Context.xml being deleted
On 13/04/2010 02:24, Hassan Schroeder wrote: > On Mon, Apr 12, 2010 at 6:08 PM, Sam Stephens wrote: > >> I have a forum application. When we update it we want to distribute a >> new war file (previously we updated all files individually). If we >> give out a new war file to our customers the images directory, the >> attachments directory and other directories that contain user uploaded >> data will be wiped out. >> >> Is there a solution to this dilemma? Sym links are are no - you'd have >> to remake them each time so still a lot of work. > > Well, AFAIK it's either symlinks (which can be scripted in deployment > processes pretty easily) or put all that stuff in a separate context that > you never, ever, EVER undeploy :-) > > I've used both approaches, can't really say I have a preference. The > latter might be a little less work, and definitely reduces the exposure > to symlink oopsies... Tomcat 7 will have the ability to alias external content into a web app's url space. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 6.0.26, JSF problems
I have simple and standard MyFaces app. deployed, that worked successfully on
6.0.18 tomcat on the same OS(Ubuntu kernel 2.6.31-20-generic, i686).
After deploy on 6.0.26 it stops to work correctly.
1)
message bundles not recognized,
code like that not working:
it does not see the message, treats all the #{message.abc} like a simple
string.
2)
In select boxes it does not recognize value listeners. treats them like simple
strings.
It seems TomCat became unaware of JSF presence in the app.
Deployment details:
All jsf libs are under MY_WEB_APP/WEB_INF/lib, in tomcat libs I have nothing of
mine.
"myfaces" version used is 1.2.5
RE: web page rendering is slow
Hi >> Embed them in an iframe. The design of this Web application is in Tiles / Struts format. When we did load testing ..we did not encounter any problems. The Tags are in embedded in function adv1() format And the script function is provided by the 3rd party sponsor. Any ideas 's for this problem With regards karthik -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Tuesday, April 13, 2010 2:45 PM To: Tomcat Users List Subject: Re: web page rendering is slow On 13/04/2010 08:53, Karthik Nanjangude wrote: > Hi > > SPEC > > JDK 1.5 > TOMCAT 5.x (JBOSS Embedded) > OS : LINUX > > > Problem > > Our application caters to B2C process with embedded with 3rd party URL's > for Advertisement process in display > > How ever some times this URL's are slow in response, hence our web page > rendering is slow How are you including the content from the URL? > Is there any way to solve this issue? > Note: - Need to have the 3rd party URL for sponsorship Embed them in an iframe. p > With regards > > N.S.Karthik > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to reload webapp automaticly under tomcat 6.0.20
On 13/04/2010 04:38, red phoenix wrote: I set following statement in conf/server.xml, it can run well before tomcat6.0.20,when I modify class file,tomcat can reload automaticly. But when I use tomcat 6.0.2,I find it can't reload automaticly,why? Where is wrong? How to do it? Really 6.0.2 ? Where is wrong? Don't define your context in server.xml. It is not recommended for Tomcat 6 and unnecessary in your case. How to do it? By placing the Context configuration in server.xml, you are making it more difficult to achieve what you want. Instead call your app Test.war (or a directory "Test") and place your Context definition in Test/META-INF/context.xml. You won't need the path and docBase attributes anymore. If that doesn't work, post the relevant Host definition here. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0.26, JSF problems
2010/4/13 Peter Kovgan :
> I have simple and standard MyFaces app. deployed, that worked successfully on
> 6.0.18 tomcat on the same OS(Ubuntu kernel 2.6.31-20-generic, i686).
>
> After deploy on 6.0.26 it stops to work correctly.
>
For the #{} expressions to be recognized in Tomcat 6, your web
application must adhere to the Servlet 2.5 specification. Make sure,
that version and xsi:schemaLocation attributes of element in
your WEB-INF/web.xml file have the correct values. You can look into
conf/web.xml or into the examples application for an example.
In the versions 6.0.24 and earlier the deferred expressions were
processed regardless of the specification version specified in
web.xml. That was changed/fixed in 6.0.26.
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
The question of automatic restart Tomcat
Good afternoon. I apologise if this theme described in documentation Tomcat, I badly understand English language. Whether you could not answer me is in tomcat 6.0.X Service which automatically would start Tomcat, at end of its work as a result of an error or failure in software work. If such service I will is it is very grateful if you send me the reference to the documentation on adjustment of this service, or simply tell as it is called. Copy Good afternoon. I apologize if this topic is described in the documentation Tomcat, I do not understand English. Could you answer me is there in tomcat 6.0.X service that would automatically starts Tomcat, at the conclusion of his work as a result of errors or malfunction of the software. If this service is going to be very grateful if you send me a link to the documentation on configuring this service, or just tell it s called. -- С уважением, Mirgorodskiy mailto:eugene.mirgorods...@extreme-idea.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Context.xml being deleted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hassan, On 4/12/2010 9:24 PM, Hassan Schroeder wrote: > On Mon, Apr 12, 2010 at 6:08 PM, Sam Stephens wrote: > >> I have a forum application. When we update it we want to distribute a >> new war file (previously we updated all files individually). If we >> give out a new war file to our customers the images directory, the >> attachments directory and other directories that contain user uploaded >> data will be wiped out. >> >> Is there a solution to this dilemma? Sym links are are no - you'd have >> to remake them each time so still a lot of work. > > Well, AFAIK it's either symlinks (which can be scripted in deployment > processes pretty easily) or put all that stuff in a separate context that > you never, ever, EVER undeploy :-) You can also put your deployment directory outside the webapps directory. Those webapps aren't deleted when undeployed, right? Also, you can put your external content in some other directory, and write a simple servlet to serve that content based upon URL prefix. Finally, you can subclass the DefaultServlet and change the way it finds files so that it finds those files in a separate directory (instead of within your deployment directory). This is essentially the same as my second suggestion above except that you get all the benefits of using the DefaultServlet. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEcscACgkQ9CaO5/Lv0PB+jACgot4bONZXQLdPz2bPqzJ6EJYm +9UAn2e7/PFEKsUjL7Wb61GcMAiBtRqs =P0e7 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: web page rendering is slow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karthik, On 4/13/2010 5:32 AM, Karthik Nanjangude wrote: >>> Embed them in an iframe. > > The design of this Web application is in Tiles / Struts format. > When we did load testing ..we did not encounter any problems. If your load testing did not demonstrate any problems, yet you are encountering problems in production, that suggests that your load tests were not properly reproducing real-world scenarios. > The Tags are in embedded in function adv1() format Can you turn these into constructs? These will not prevent the browser from rendering the page. > And the script function is provided by the 3rd party sponsor. > > Any ideas 's for this problem Cache the 3rd-party functions locally with some timeout? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEc1UACgkQ9CaO5/Lv0PBVvQCgiNKCrJsZLuYfjrG+el6c2Qza mEMAoJGUMewDVz1I1Iy7p547cEqrVf1B =DSp5 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Installing certificate chain on Tomat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael, On 4/12/2010 4:55 PM, Michael Dockery wrote: > because tomcat has the root for the client cert loaded into its truststore, > and the matching client cert "subject" name (ie: user) loaded in its auth > realm > the client is therefore authenticated Right: Tomcat can authenticate the client certificate because it has the required trust roots. The OP as asking about the opposite: the client is complaining that the server's cert is untrusted (or, rather, that the cert chain doesn't lead to a known, trusted root). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEc90ACgkQ9CaO5/Lv0PDmCgCdE1pCXpY8yoVMmogSFPBXvvXQ WwYAnRITkLQcCnYHkp31UpUzY5FYVCQm =wp2q -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: web page rendering is slow
(With apologies to Karthik, as I inadvertently sent this to him directly) On 13/04/2010 10:32, Karthik Nanjangude wrote: Hi Embed them in an iframe. The design of this Web application is in Tiles / Struts format. When we did load testing ..we did not encounter any problems. Perhaps your load testing didn't completely accurately replicate real-world conditions. Did it simulate a browser loading each page, completely with images, CSS, javascript etc? The Tags are in embedded in function adv1() format And the script function is provided by the 3rd party sponsor. This sounds like it's an HTML problem, not a server problem. Are the scripts defined in-line in the HTML? Browsers will stop rendering the page if they find a new script tag definition, until that script is downloaded and run. Any ideas 's for this problem If possible place all of the script tags at the end of the page so they don't hold up rendering. p With regards karthik -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Tuesday, April 13, 2010 2:45 PM To: Tomcat Users List Subject: Re: web page rendering is slow On 13/04/2010 08:53, Karthik Nanjangude wrote: Hi SPEC JDK 1.5 TOMCAT 5.x (JBOSS Embedded) OS : LINUX Problem Our application caters to B2C process with embedded with 3rd party URL's for Advertisement process in display How ever some times this URL's are slow in response, hence our web page rendering is slow How are you including the content from the URL? Is there any way to solve this issue? Note: - Need to have the 3rd party URL for sponsorship Embed them in an iframe. p With regards N.S.Karthik - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: web page rendering is slow
On 13/04/2010 14:36, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karthik, On 4/13/2010 5:32 AM, Karthik Nanjangude wrote: Embed them in an iframe. The design of this Web application is in Tiles / Struts format. When we did load testing ..we did not encounter any problems. If your load testing did not demonstrate any problems, yet you are encountering problems in production, that suggests that your load tests were not properly reproducing real-world scenarios. The Tags are in embedded in function adv1() format Can you turn these into constructs? These will not prevent the browser from rendering the page. I thought that even a src referenced script stopped the page? p And the script function is provided by the 3rd party sponsor. Any ideas 's for this problem Cache the 3rd-party functions locally with some timeout? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEc1UACgkQ9CaO5/Lv0PBVvQCgiNKCrJsZLuYfjrG+el6c2Qza mEMAoJGUMewDVz1I1Iy7p547cEqrVf1B =DSp5 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Hung threads
I had a connector go from minimal connections (restart) to all threads hung overnight. The current thread dump shows the threads as follows: "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in Object.wait() [0x7063f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x1a924f00> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked <0x1a924f00> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-149" daemon prio=6 tid=0x6496d400 nid=0xe400 in Object.wait() [0x705ff000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x1a954140> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked <0x1a954140> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-148" daemon prio=6 tid=0x6496f400 nid=0xe3b0 in Object.wait() [0x705bf000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x1a8655f0> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked <0x1a8655f0> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) and so on. Other connectors are running OK, though some also show threads in the same state. All other threads look normal. This has one customer's app hung, but others in the Tomcat instance are working just fine. Any help on where to start looking here? Server Details: Windows 2000 SP4, Sun JDK 1.6.0_18, Tomcat 5.5.17, native libs 1.1.18. Waiting for TC 5.5.29 before upgrading due to bugs with APR/SSL in 5.5.28. Jeff *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments.
ASF servers hacked (JIRA, Bugzilla, Confluence)
Don't know if you guys are aware of it, but the above mentioned system have been compromised. According to their blog (https://blogs.apache.org/infra/entry/apache_org_04_09_2010), the ASF infrastructure-team recommends to change your passwords for said systems. Rgds Gregor -- just because you're paranoid, don't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 @ http://pgp.mit.edu:11371/ skype:rc46fi - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Hung threads
Before someone asks for it: -Original Message- From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Sent: Tuesday, April 13, 2010 9:44 AM To: Tomcat Users List Subject: Hung threads I had a connector go from minimal connections (restart) to all threads hung overnight. The current thread dump shows the threads as follows: "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in Object.wait() [0x7063f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x1a924f00> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked <0x1a924f00> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-149" daemon prio=6 tid=0x6496d400 nid=0xe400 in Object.wait() [0x705ff000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x1a954140> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked <0x1a954140> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-148" daemon prio=6 tid=0x6496f400 nid=0xe3b0 in Object.wait() [0x705bf000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x1a8655f0> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked <0x1a8655f0> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) and so on. Other connectors are running OK, though some also show threads in the same state. All other threads look normal. This has one customer's app hung, but others in the Tomcat instance are working just fine. Any help on where to start looking here? Server Details: Windows 2000 SP4, Sun JDK 1.6.0_18, Tomcat 5.5.17, native libs 1.1.18. Waiting for TC 5.5.29 before upgrading due to bugs with APR/SSL in 5.5.28. Jeff *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Context.xml being deleted
On Tue, Apr 13, 2010 at 6:33 AM, Christopher Schultz wrote: >> Well, AFAIK it's either symlinks (which can be scripted in deployment >> processes pretty easily) or put all that stuff in a separate context that >> you never, ever, EVER undeploy :-) Sheesh, yeah. Multitasking #FAIL. Garcon, more coffee, s'il vous plaît! > You can also put your deployment directory outside the webapps > directory. Those webapps aren't deleted when undeployed, right? Honestly, it's been so long since I learned that "o-$4!T" delete-symlink lesson that I don't remember where the app was deployed, but you're probably right. > Also, you can put your external content in some other directory, and > write a simple servlet to serve that content based upon URL prefix. > > Finally, you can subclass the DefaultServlet and change the way it finds > files so that it finds those files in a separate directory (instead of > within your deployment directory). This is essentially the same as my > second suggestion above except that you get all the benefits of using > the DefaultServlet. And of course those are both true, in increasing order of complexity. Thanks for adding those, and maybe the whole list should just be in the FAQ? If it isn't already? (haven't checked) And where /is/ that coffee?? :-) -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: web page rendering is slow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 4/13/2010 10:45 AM, Pid wrote: > On 13/04/2010 14:36, Christopher Schultz wrote: > Karthik, > > On 4/13/2010 5:32 AM, Karthik Nanjangude wrote: >> Embed them in an iframe. The design of this Web application is in Tiles / Struts format. When we did load testing ..we did not encounter any problems. > > If your load testing did not demonstrate any problems, yet you are > encountering problems in production, that suggests that your load tests > were not properly reproducing real-world scenarios. > The Tags are in embedded in function adv1() format > > Can you turn these into constructs? These > will not prevent the browser from rendering the page. > >> I thought that even a src referenced script stopped the page? I was thinking of this: http://www.stevesouders.com/blog/2009/04/09/dont-use-import/ But there's also this: http://www.stevesouders.com/blog/2009/04/27/loading-scripts-without-blocking/ - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEkJ4ACgkQ9CaO5/Lv0PB0IACgiVesyN9A2noqKAmmGfRLyHFD ysEAn2tOikNdk5VRezxFVJdoJlihV3xo =uN67 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Hung threads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 4/13/2010 10:44 AM, Jeffrey Janner wrote: > I had a connector go from minimal connections (restart) to all threads > hung overnight. > > The current thread dump shows the threads as follows: > > "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in > Object.wait() [0x7063f000] > >java.lang.Thread.State: WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > - waiting on <0x1a924f00> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) I'm pretty sure these threads are considered idle. Are you able to make a request on port 443 and have it serviced? > Other connectors are running OK, though some also show > threads in the same state. All other threads look normal. This has one > customer's app hung, but others in the Tomcat instance are working just > fine. Any help on where to start looking here? The connectors are global for the entire app server, so if any webapps are accessible, they should all be accessible (unless this is the only webapp that requires SSL, in which case a dead SSL connector would certainly affect only that one webapp). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEkWUACgkQ9CaO5/Lv0PAuIgCfULZw2F0zb+CBMWvJVUC8JIHt iuMAoJM6Cs2dC7ufRfEA/13Z513NjfdZ =WSuM -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
SSL session resuming
Hi,
I have a problem with tomcat SSL session resuming using MSIE. In my webapp,
user authentication is done using the
"org.apache.catalina.authenticator.SingleSignOn" valve and a corresponding
realm (PKI authentication). Now accessing the webapp, which uses a frameset
that might be part of the problem, results in the following logs.
*** ClientHello, TLSv1
RandomCookie: GMT: 1254330738 bytes = { 67, 136, 202, 169, 151, 124, 142,
187, 135, 183, 161, 157, 81, 240, 254, 21, 180, 139, 139, 46, 32, 65, 155,
230, 69, 24, 175, 180 }
Session ID: {75, 196, 142, 249, 121, 35, 217, 254, 49, 37, 92, 86, 255,
220, 61, 188, 8, 128, 86, 203, 172, 93, 103, 185, 114, 43, 169, 80, 236, 96,
181, 108}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA,
SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA,
SSL_RSA_EXPORT1024_WITH_RC4_56_SHA, SSL_RSA_EXPORT1024_WITH_DES_CBC_SHA,
SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5,
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA,
SSL_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA]
Compression Methods: { 0 }
***
%% Created: [Session-28, SSL_RSA_WITH_RC4_128_MD5]
*** ServerHello, TLSv1
RandomCookie: GMT: 1254330670 bytes = { 70, 109, 88, 141, 114, 86, 38, 165,
172, 3, 134, 203, 86, 192, 194, 212, 222, 116, 116, 70, 224, 228, 141, 46,
205, 21, 60, 245 }
Session ID: {75, 196, 145, 46, 223, 171, 82, 104, 96, 0, 209, 75, 145, 92,
61, 143, 30, 199, 157, 239, 160, 76, 28, 177, 71, 221, 98, 117, 244, 137,
146, 126}
As you can see, the MSIE client wants to resume the SSL session, but a new
one is created every time a new request is sent. In the logs I can also see
entries like the following:
http-8444-5, handling exception: java.net.SocketException: Connection reset
%% Invalidated: [Session-27, SSL_RSA_WITH_RC4_128_MD5]
http-8444-5, SEND TLSv1 ALERT: fatal, description = unexpected_message
Seems, the socket is closed after every request resulting in a new SSL
handshake.
Here is my connector setup:
"
keystorePass=""
keystoreType="pkcs12" truststoreFile=" truststorePass=""
truststoreType="jks" />
The strange thing is that everything works as expected using Firefox, i.e.
the SSL session is resumed for subsequent requests. But I need to get it run
on MSIE as well.
Thanks for any help on that!
Regards,
Matthias
--
View this message in context:
http://old.nabble.com/SSL-session-resuming-tp28232164p28232164.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Hung threads
Looks like just idle threads, not really a problem If you want the thread pool to shrink and stop idle threads, use an element in server.xml Filip On 04/13/2010 08:50 AM, Jeffrey Janner wrote: Before someone asks for it: -Original Message- From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Sent: Tuesday, April 13, 2010 9:44 AM To: Tomcat Users List Subject: Hung threads I had a connector go from minimal connections (restart) to all threads hung overnight. The current thread dump shows the threads as follows: "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in Object.wait() [0x7063f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on<0x1a924f00> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked<0x1a924f00> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-149" daemon prio=6 tid=0x6496d400 nid=0xe400 in Object.wait() [0x705ff000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on<0x1a954140> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked<0x1a954140> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-148" daemon prio=6 tid=0x6496f400 nid=0xe3b0 in Object.wait() [0x705bf000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on<0x1a8655f0> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 5) - locked<0x1a8655f0> (a org.apache.tomcat.util.net.AprEndpoint$Worker) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) at java.lang.Thread.run(Thread.java:619) and so on. Other connectors are running OK, though some also show threads in the same state. All other threads look normal. This has one customer's app hung, but others in the Tomcat instance are working just fine. Any help on where to start looking here? Server Details: Windows 2000 SP4, Sun JDK 1.6.0_18, Tomcat 5.5.17, native libs 1.1.18. Waiting for TC 5.5.29 before upgrading due to bugs with APR/SSL in 5.5.28. Jeff *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.a
RE: Hung threads
*** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. --- Begin Message --- Hi Chris - Sorry I was extremely clear. My config has each customer in a separate service structure, so each get his own set of connectors (IPs). Yes, I am unable to get a response on this specific IP/port combo. All other connectors were responding and all of those apps were working fine, from what I could tell. The Tomcat Manager only showed 4 sessions for this host when I started, and that eventually dropped to 1, but I could never get a response from the app. After a restart, I did a connect, and immediately had 7 threads start up and apparently end in the same state (at least it looks the same in jconsole). I was able to navigate the app and never had the thread count increase. Every check on the thread states showed the same, though the Total blocked/Total Waited counters keep increasing. The really interesting thing is that over more than an hour with virtually no traffic, should not some of the threads started shutting down? Jeff -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, April 13, 2010 10:45 AM To: Tomcat Users List Subject: Re: Hung threads -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 4/13/2010 10:44 AM, Jeffrey Janner wrote: > I had a connector go from minimal connections (restart) to all threads > hung overnight. > > The current thread dump shows the threads as follows: > > "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in > Object.wait() [0x7063f000] > >java.lang.Thread.State: WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > - waiting on <0x1a924f00> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) I'm pretty sure these threads are considered idle. Are you able to make a request on port 443 and have it serviced? > Other connectors are running OK, though some also show > threads in the same state. All other threads look normal. This has one > customer's app hung, but others in the Tomcat instance are working just > fine. Any help on where to start looking here? The connectors are global for the entire app server, so if any webapps are accessible, they should all be accessible (unless this is the only webapp that requires SSL, in which case a dead SSL connector would certainly affect only that one webapp). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEkWUACgkQ9CaO5/Lv0PAuIgCfULZw2F0zb+CBMWvJVUC8JIHt iuMAoJM6Cs2dC7ufRfEA/13Z513NjfdZ =WSuM -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --- End Message --- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Hung threads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff, On 4/13/2010 12:10 PM, Jeffrey Janner wrote: > Sorry I was extremely clear. My config has each customer in a > separate service structure, so each get his own set of connectors > (IPs). Gotcha. > Yes, I am unable to get a response on this specific IP/port combo. That's not good. Do you get a connection refused, or do you get a timeout? > The Tomcat Manager only showed 4 sessions for this host when I > started, and that eventually dropped to 1, but I could never get a > response from the app. Note that lots of requests can be services without a session being created (depending on your webapp). > After a restart, I did a connect, and immediately had 7 threads > start up and apparently end in the same state (at least it looks the > same in jconsole). The state of the threads in your thread dump is normal: WAITING means blocked on a monitor (i.e. Object.wait). Those threads are waiting to be notified by the acceptor thread that a request has been made and is ready for processing. > I was able to navigate the app and never had the thread count > increase. Every check on the thread states showed the same, though > the Total blocked/Total Waited counters keep increasing. That's strange. > The really interesting thing is that over more than an hour with > virtually no traffic, should not some of the threads started > shutting down? Read Filip's post about using an to remove unnsed threads: the standard -based thread pooling will never remove threads, even though it looks like they will based upon the configuration of the . s are much better for resource management. I'm still concerned that you are unable to get a request through to the connector. Can you double-check that you haven't grabbed the wrong section of the thread dump? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEmroACgkQ9CaO5/Lv0PAx9wCfY2cyUtTCRxDGHWH6H45KZ05L +80An25jy/aVgJ6LSdprOJI+Kcd0hbLK =N6cI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Hung threads
Thanks, but is not available in 5.5 -- at least according to the documentation. -Original Message- From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com] Sent: Tuesday, April 13, 2010 11:03 AM To: Tomcat Users List Subject: Re: Hung threads Looks like just idle threads, not really a problem If you want the thread pool to shrink and stop idle threads, use an element in server.xml Filip On 04/13/2010 08:50 AM, Jeffrey Janner wrote: > Before someone asks for it: > maxThreads="150" minSpareThreads="5" maxSpareThreads="75" > enableLookups="false" acceptCount="100" > connectionTimeout="2" disableUploadTimeout="true" > compression="on" > > compressableMimeType="text/html,text/xml,text/plain,text/css,text/csv,te > xt/javascript,text/rtf,text/richtext" > scheme="https" secure="true" clientAuth="false" > SSLEngine="on" > SSLCertificateFile="path_to_server.crt" > SSLCertificateKeyFile=" path_to_server.key" > SSLCertificateChainFile="path_to_server_chain.crt" > SSLPassword="changeit" /> > > -Original Message- > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] > Sent: Tuesday, April 13, 2010 9:44 AM > To: Tomcat Users List > Subject: Hung threads > > I had a connector go from minimal connections (restart) to all threads > hung overnight. > > The current thread dump shows the threads as follows: > > > > "http-172.16.27.1-443-150" daemon prio=6 tid=0x66793800 nid=0xe43c in > Object.wait() [0x7063f000] > > java.lang.Thread.State: WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > - waiting on<0x1a924f00> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) > > at java.lang.Object.wait(Object.java:485) > > at > org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 > 5) > > - locked<0x1a924f00> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) > > at > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) > > at java.lang.Thread.run(Thread.java:619) > > > > "http-172.16.27.1-443-149" daemon prio=6 tid=0x6496d400 nid=0xe400 in > Object.wait() [0x705ff000] > > java.lang.Thread.State: WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > - waiting on<0x1a954140> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) > > at java.lang.Object.wait(Object.java:485) > > at > org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 > 5) > > - locked<0x1a954140> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) > > at > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) > > at java.lang.Thread.run(Thread.java:619) > > > > "http-172.16.27.1-443-148" daemon prio=6 tid=0x6496f400 nid=0xe3b0 in > Object.wait() [0x705bf000] > > java.lang.Thread.State: WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > - waiting on<0x1a8655f0> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) > > at java.lang.Object.wait(Object.java:485) > > at > org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:125 > 5) > > - locked<0x1a8655f0> (a > org.apache.tomcat.util.net.AprEndpoint$Worker) > > at > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1280) > > at java.lang.Thread.run(Thread.java:619) > > > > and so on. Other connectors are running OK, though some also show > threads in the same state. All other threads look normal. This has one > customer's app hung, but others in the Tomcat instance are working just > fine. Any help on where to start looking here? > > > > Server Details: Windows 2000 SP4, Sun JDK 1.6.0_18, Tomcat 5.5.17, > native libs 1.1.18. > > > > Waiting for TC 5.5.29 before upgrading due to bugs with APR/SSL in > 5.5.28. > > > > Jeff > > > *** NOTICE > * > This message is intended for the use of the individual or entity to > which > it is addressed and may contain information that is privileged, > confidential, and exempt from disclosure under applicable law. If the > reader of this message is not the intended recipient or the employee or > agent responsible for delivering this message to the intended recipient, > > you are hereby notified that any dissemination, distribution, or copying > > of this communication is strictly prohibited. If you have received this > > communication in error, please notify us immediately by reply or by > telephone (call us collect at 512-343-9100) and immediately delete this > message and all its attachments. > > **
Re: The question of automatic restart Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eugene,
On 4/13/2010 7:18 AM, Mirgorodskiy Eugene wrote:
> I apologise if this theme described in documentation Tomcat, I badly
> understand English language.
>
> Whether you could not answer me is in tomcat 6.0.X Service which
> automatically would start Tomcat, at end of its work as a result of
> an error or failure in software work.
Tomcat does not provide this service. There may be such services
available elsewhere, but I am unaware of them.
You may be able to create your own, something like this:
#!/bin/sh
CATALINA_HOME=/opt/tomcat6
CHECK_INTERVAL=30s
RESTART_INTERVAL=10s
while true ; do
# Start TC in background
"${CATALINA_HOME}/bin/catalina.sh" start
# Repeatedly check stdout for errors
while true ; do
sleep ${CHECK_INTERVAL}
grep OutOfMemoryError "${CATALINA_HOME}/logs/catalina.out"
result = $?
if [ "0" == "${result}" ] ; then
break
fi
done
# Stop TC
"${CATALINA_HOME}/bin/catalina.sh" stop
sleep ${RESTART_INTERVAL}
done
This will run Tomcat forever and restart it if any OutOfMemoryError
messages are emitted to logs/catalina.out.
You can certainly customize this to meet whatever other needs you may
have. You can even have your webapp dump something into stdout (or some
other file) and check that, too.
Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkvEndIACgkQ9CaO5/Lv0PDORQCfcTUbMHXMqiNFLPvRl7Spfnzg
erAAoI1r5JnHFLVpmg0PereR4yBBzTAU
=/1/r
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Hung threads
I got no response. No error from Tomcat or the browser. In IE, the status bar progress bar runs a bit, then goes to the end and disappears. The page doesn't change. I had to use jstack to get the dump. I just posted a sample of a few of the connectors. I've included the entire dump file as an attachment to this post (if it doesn't get stripped). But I didn't see anything sitting in our code. Note that the 172.16.27.1 entries are for the hung host. The other IP address is for the working host. Both hosts are configured to send all traffic to HTTPS inside the app. Unfortunately, doesn't appear to be available in 5.5.x. And before the inevitable, the available heap looked just fine. -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, April 13, 2010 11:24 AM To: Tomcat Users List Subject: Re: Hung threads Jeff, On 4/13/2010 12:10 PM, Jeffrey Janner wrote: > Sorry I was extremely clear. My config has each customer in a > separate service structure, so each get his own set of connectors > (IPs). Gotcha. > Yes, I am unable to get a response on this specific IP/port combo. That's not good. Do you get a connection refused, or do you get a timeout? > The Tomcat Manager only showed 4 sessions for this host when I > started, and that eventually dropped to 1, but I could never get a > response from the app. Note that lots of requests can be services without a session being created (depending on your webapp). > After a restart, I did a connect, and immediately had 7 threads > start up and apparently end in the same state (at least it looks the > same in jconsole). The state of the threads in your thread dump is normal: WAITING means blocked on a monitor (i.e. Object.wait). Those threads are waiting to be notified by the acceptor thread that a request has been made and is ready for processing. > I was able to navigate the app and never had the thread count > increase. Every check on the thread states showed the same, though > the Total blocked/Total Waited counters keep increasing. That's strange. > The really interesting thing is that over more than an hour with > virtually no traffic, should not some of the threads started > shutting down? Read Filip's post about using an to remove unnsed threads: the standard -based thread pooling will never remove threads, even though it looks like they will based upon the configuration of the . s are much better for resource management. I'm still concerned that you are unable to get a request through to the connector. Can you double-check that you haven't grabbed the wrong section of the thread dump? - -chris *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The question of automatic restart Tomcat
On 4/13/2010 7:18 AM, Mirgorodskiy Eugene wrote: Good afternoon. I apologise if this theme described in documentation Tomcat, I badly understand English language. Whether you could not answer me is in tomcat 6.0.X Service which automatically would start Tomcat, at end of its work as a result of an error or failure in software work. If such service I will is it is very grateful if you send me the reference to the documentation on adjustment of this service, or simply tell as it is called. Copy Good afternoon. I apologize if this topic is described in the documentation Tomcat, I do not understand English. Could you answer me is there in tomcat 6.0.X service that would automatically starts Tomcat, at the conclusion of his work as a result of errors or malfunction of the software. If this service is going to be very grateful if you send me a link to the documentation on configuring this service, or just tell it s called. In windows, you can set services to automatically restart if they fail. That is done from the services manager in Administrative Tools. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Hung threads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 4/13/2010 12:46 PM, Jeffrey Janner wrote: > "http-172.16.27.1-443-Poller-7" daemon prio=6 > tid=0x649cnVVpEWVZadmQxSnJTbEpXDQpWVnBFV1ZaYWRtUXhTbkpUYkVwWERRcFdWbkJGVjFaYVlXUnRVWGhU > YmtwVVlrVndXRVJSY0ZkV2JrSkdWakZhWVZsWFVuUlZXR2hVDQpZbXR3VlZsclZuZFhSVkpTWTBa > a1YySnJTa2RXYWtaaFdWWnNXRlZ1VWxaWFIyaFZEUXBaYlhSM1ZsWnNjbFp1WkZoU1ZrcFRXVEJh > DQphMVl5U25KVGEyUlhZV3RhYUZkV1duTlhSbFoxVld4YVdGSXlhRlpFVVhCYVlsaFNNMVpzV25O > amJGcDFXa1pvVTFacmNGUlhWRUpoDQpEUXBoTVZsNVUyNUtWR0V5VWxoWlYzUmhZVVprVjFkdVRs > aFNiRm94VmxkNFlWZEdTWGxoUmxwRlZWaENZVmxzYUZOTk1WcHpWMjVPDQphbUpHY0RGWGExcHZW > VEZhY21OR1VsaFdSVXBvRFFwRVVYQm9UVlpzTlZVeU5VdFdSMFY1Vld4b1dsWXpVbWhaVlZwclZq > RmtkVlJzDQphRk5pUm05NFZteGtORmxXWkVkVFdHeG9VbXh3UmxaV2FFTlpWbXh6WVVaT1RrMVdj > SHBXTWpWUERRcGhiVXBIWTBSR1dHRXhjSFpXDQpWRVpoWTIxT1IxVnNhRmRTVlhCdlJGRndSVlZZ > UW05VVZscHpUbFpWZVU1VmRGZFNNRlkxVmxkNGIxZHNXWHBWYldoYVZsWndjbFpxDQpSbXRrVmxK > ekRRcGhSazVwVW0wNU5GWnRlR3RPUm14WFdrVmtWRmRIZUc5VmJYaDNVbXhhVjJGRlRscFdiWGg2 Now that certainly looks weird. Can you check again and re-post the poller thread's status? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEotQACgkQ9CaO5/Lv0PDEFgCZAb/KLuHKT1Z2EDldrOQ59tCg RoEAoJF53thc11WHpXI7ipDmoXumT5Si =PsHo -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Hung threads
You're right, that was weird. Not sure what did that. It wasn't that way in the original file. And it wasn't that way before I hit send. Here's the rest of the dump, picking up from just before "encoding": "RMI Scheduler(0)" daemon prio=6 tid=0x64885400 nid=0xaa8c waiting on condition [0x6707f000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x0b738a30> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963) at java.util.concurrent.DelayQueue.take(DelayQueue.java:164) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-7" daemon prio=6 tid=0x649c5800 nid=0xb7a8 in Object.wait() [0x65fbf000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b96a938> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1127) - locked <0x0b96a938> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-6" daemon prio=6 tid=0x649f5c00 nid=0xaef4 in Object.wait() [0x65f7f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b8bafd8> (a org.apache.tomcat.util.net.AprEndpoint$WorkerStack) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint.getWorkerThread(AprEndpoint.java:924) - locked <0x0b8bafd8> (a org.apache.tomcat.util.net.AprEndpoint$WorkerStack) at org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1165) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-5" daemon prio=6 tid=0x64758400 nid=0xb5dc in Object.wait() [0x65f3f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b96a998> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1127) - locked <0x0b96a998> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-4" daemon prio=6 tid=0x637f0400 nid=0xb6fc in Object.wait() [0x65eff000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b96a9c8> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1127) - locked <0x0b96a9c8> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-3" daemon prio=6 tid=0x64902400 nid=0xb27c in Object.wait() [0x65ebf000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b96a9f8> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1127) - locked <0x0b96a9f8> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-2" daemon prio=6 tid=0x63848400 nid=0xb364 in Object.wait() [0x65e7f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b96aa28> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1127) - locked <0x0b96aa28> (a org.apache.tomcat.util.net.AprEndpoint$Poller) at java.lang.Thread.run(Thread.java:619) "http-172.16.27.1-443-Poller-1" daemon prio=6 tid=0x64505400 nid=0xb674 in Object.wait() [0x65e3f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x0b96aa58> (a org.apache.tomcat.util.net.AprEndpoint$Po
Re: The question of automatic restart Tomcat
We use automatic restarts on OutOfMemory errors and it works fantastically. I
don't do it the way described here, though. I use the JVM's
-XX:OnOutOfMemoryError option. I add the following to CATALINA_OPTS:
-XX:OnOutOfMemoryError=/usr/sbin/restart_tcserver
...which restarts tcServer whenever an OOME occurs. Unfortunately, it doesn't
produce a stacktrace (it calls your script instead). But that's okay in my
case. I just want to make sure the server gets restarted.
We had one of these a while back, so I know it works fine (the restart script
also sends me an email--including "top" output--letting me know what happened).
Thanks!
Jon Brisbin
Portal Webmaster
NPC International, Inc.
On Apr 13, 2010, at 11:37 AM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Eugene,
>
> On 4/13/2010 7:18 AM, Mirgorodskiy Eugene wrote:
>> I apologise if this theme described in documentation Tomcat, I badly
>> understand English language.
>>
>> Whether you could not answer me is in tomcat 6.0.X Service which
>> automatically would start Tomcat, at end of its work as a result of
>> an error or failure in software work.
>
> Tomcat does not provide this service. There may be such services
> available elsewhere, but I am unaware of them.
>
> You may be able to create your own, something like this:
>
> #!/bin/sh
>
> CATALINA_HOME=/opt/tomcat6
> CHECK_INTERVAL=30s
> RESTART_INTERVAL=10s
>
> while true ; do
> # Start TC in background
> "${CATALINA_HOME}/bin/catalina.sh" start
>
> # Repeatedly check stdout for errors
> while true ; do
>sleep ${CHECK_INTERVAL}
>grep OutOfMemoryError "${CATALINA_HOME}/logs/catalina.out"
>
>result = $?
>if [ "0" == "${result}" ] ; then
> break
>fi
> done
>
> # Stop TC
> "${CATALINA_HOME}/bin/catalina.sh" stop
> sleep ${RESTART_INTERVAL}
> done
>
> This will run Tomcat forever and restart it if any OutOfMemoryError
> messages are emitted to logs/catalina.out.
>
> You can certainly customize this to meet whatever other needs you may
> have. You can even have your webapp dump something into stdout (or some
> other file) and check that, too.
>
> Hope that helps,
> - -chris
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkvEndIACgkQ9CaO5/Lv0PDORQCfcTUbMHXMqiNFLPvRl7Spfnzg
> erAAoI1r5JnHFLVpmg0PereR4yBBzTAU
> =/1/r
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Hung threads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff, Okay, you're running into the limits of my knowledge of the APR connector's internals. On 4/13/2010 1:24 PM, Jeffrey Janner wrote: > "http-172.16.27.1-443-Acceptor-0" daemon prio=6 tid=0x6425c400 nid=0xb6c4 in > Object.wait() [0x65d7f000] >java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0b8bafd8> (a > org.apache.tomcat.util.net.AprEndpoint$WorkerStack) > at java.lang.Object.wait(Object.java:485) > at > org.apache.tomcat.util.net.AprEndpoint.getWorkerThread(AprEndpoint.java:924) > - locked <0x0b8bafd8> (a > org.apache.tomcat.util.net.AprEndpoint$WorkerStack) > at > org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:997) > at java.lang.Thread.run(Thread.java:619) This is the "acceptor" thread which basically accepts all the incoming requests and assigns them to worker threads: it's just a traffic cop. This thread looks like it's stuck waiting for an available worker thread (AprEndpoint.getWorkerThread) so it looks like something is definitely wrong, here. Unfortunately for you, you'll need someone like Filip who knows everything about these Connectors to comment. > maxThreads="150" minSpareThreads="5" maxSpareThreads="75" >enableLookups="false" acceptCount="100" It looks like a thread called "http-172.16.27.1-443-150" exists, which suggests that all maxThreads have been allocated, though they really do all look idle to me. Hmm. Yeah, wait for Filip. :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEsBgACgkQ9CaO5/Lv0PCV9wCgtniW8WPI9nFm86jHxt1zPc5i kOMAnR6loJp236+HzeFER9ULkYM6TW8W =jxfF -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
connection pool issues with mod_proxy_ajp when tomcat is remote
howdy! we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache 2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28 and we've run into a troubling bug/configuration/networking problem with apache 2.0 and mod_proxy, things are very well behaved. apache has a connection pool of tomcat threads, and when apache kills a child process the corresponding tomcat thread is closed. with apache 2.2 and mod_proxy_ajp, when apache kills a child process, the sometimes the tomcat thread is left hanging in the keep alive state. tomcat waits 120 seconds before terminating the hanging thread. this seems to happen more often under higher traffic, and more often when tomcat is not running on the same server as apache. under traffic, this results in a large number of tomcat threads that have lost their connection to apache and are waiting to timeout, eventually leaving no free threads for legitimate requests. can anyone suggest what could be causing this, or how to troubleshoot? i've tried using the keepalive=on parameter to ProxyPass with no luck. here are some relevant configuration details: with both versions of apache we're using the worker MPM tomcat server.xml: apache 2.0.52/mod_jk 1.2.19 workers.properties worker.default.port=8009 worker.default.type=ajp13 worker.default.connect_timeout=12 worker.default.connection_pool_timeout=120 worker.default.prepost_timeout=12 worker.default.reply_timeout=180 worker.default.retries=1 apache 2.2.3/mod_proxy_ajp ProxyPass / ajp://example.org:8009/ timeout=1800 keepalive=on thanks in advance for any help, and if there's another mailing list for mod_proxy_ajp questions that would be a better recipient please let me know! -- russell uman firebus d-_-b - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The question of automatic restart Tomcat
On Tue, Apr 13, 2010 at 7:46 PM, Jon Brisbin wrote: > We use automatic restarts on OutOfMemory errors and it works fantastically. I > don't do it the way described here, though. I use the JVM's > -XX:OnOutOfMemoryError option. I add the following to CATALINA_OPTS: > > -XX:OnOutOfMemoryError=/usr/sbin/restart_tcserver > I'm not aware of that option within my standard sun jdk 1.6.x - what Java-version are you running offering this really useful feature? Cheers Gregor -- just because you're paranoid, don't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 @ http://pgp.mit.edu:11371/ skype:rc46fi - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The question of automatic restart Tomcat
Gregor, --- On Tue, 4/13/10 at 1:19 PM, Gregor Schneider wrote: > > > > -XX:OnOutOfMemoryError=/usr/sbin/restart_tcserver > > > I'm not aware of that option within my standard sun jdk > 1.6.x - what > Java-version are you running offering this really useful > feature? > I wasn't aware of it either. >From http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp -XX:OnOutOfMemoryError=";" Run user-defined commands when an OutOfMemoryError is first thrown. (Introduced in 1.4.2 update 12, 6) - Bob - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The question of automatic restart Tomcat
This looks to be a feature of Java HotSpot, and available since v1.4: http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp On Tue, Apr 13, 2010 at 4:19 PM, Gregor Schneider wrote: > On Tue, Apr 13, 2010 at 7:46 PM, Jon Brisbin > wrote: > > We use automatic restarts on OutOfMemory errors and it works > fantastically. I don't do it the way described here, though. I use the JVM's > -XX:OnOutOfMemoryError option. I add the following to CATALINA_OPTS: > > > > -XX:OnOutOfMemoryError=/usr/sbin/restart_tcserver > > > I'm not aware of that option within my standard sun jdk 1.6.x - what > Java-version are you running offering this really useful feature? > > Cheers > > Gregor > -- "Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be" --Christopher Marlowe, 'Doctor Faustus' (v, 121-24)
Re: The question of automatic restart Tomcat
comments below... On Apr 13, 2010, at 3:40 PM, Bob Hall wrote: > Gregor, > > --- On Tue, 4/13/10 at 1:19 PM, Gregor Schneider > wrote: > >>> >>> -XX:OnOutOfMemoryError=/usr/sbin/restart_tcserver >>> >> I'm not aware of that option within my standard sun jdk >> 1.6.x - what >> Java-version are you running offering this really useful >> feature? >> > > I wasn't aware of it either. > > From http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp > > -XX:OnOutOfMemoryError=";" > > Run user-defined commands when an OutOfMemoryError is first thrown. > (Introduced in 1.4.2 update 12, 6) There's also: -XX:OnError=";" Run user-defined commands on fatal error. (Introduced in 1.4.2 update 9.) Jon Brisbin Portal Webmaster NPC International, Inc. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Installing Tomcat as daeon on Mac 10.6 (Snow Leopard)
Hi, I've installed Tomcat 6.0.26 on my Mac 10.6.3 system. I'm trying to run it as a daemon on system startup and I was following the instructions here -- http://www.malisphoto.com/tips/tomcatonosx.html#Anchor-JSVC. But the site says to untar the "~/Downloads/tomcat-plist.tar.gz" file and I can't find that anywhere. Does anyone know where I can find it or what file I can install in my /Library/LaunchDaemons/ to get Tomcat to launch on system startup? Thanks, - Dave -- View this message in context: http://old.nabble.com/Installing-Tomcat-as-daeon-on-Mac-10.6-%28Snow-Leopard%29-tp28235524p28235524.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Installing Tomcat as daeon on Mac 10.6 (Snow Leopard)
On Tue, Apr 13, 2010 at 1:58 PM, laredotornado wrote: > I've installed Tomcat 6.0.26 on my Mac 10.6.3 system. I'm trying to run it > as a daemon on system startup and I was following the instructions here -- > http://www.malisphoto.com/tips/tomcatonosx.html#Anchor-JSVC. But the site > says to untar the "~/Downloads/tomcat-plist.tar.gz" file and I can't find > that anywhere. Does anyone know where I can find it Those instructions include a link to that file; click it, download, and by default it will be in your Downloads directory, i.e. ~/Downloads. HTH, -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: web page rendering is slow
On 13/04/2010 16:41, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 4/13/2010 10:45 AM, Pid wrote: On 13/04/2010 14:36, Christopher Schultz wrote: Karthik, On 4/13/2010 5:32 AM, Karthik Nanjangude wrote: Embed them in an iframe. The design of this Web application is in Tiles / Struts format. When we did load testing ..we did not encounter any problems. If your load testing did not demonstrate any problems, yet you are encountering problems in production, that suggests that your load tests were not properly reproducing real-world scenarios. The Tags are in embedded in function adv1()format Can you turn these into constructs? These will not prevent the browser from rendering the page. I thought that even a src referenced script stopped the page? I was thinking of this: http://www.stevesouders.com/blog/2009/04/09/dont-use-import/ But there's also this: http://www.stevesouders.com/blog/2009/04/27/loading-scripts-without-blocking/ OK. That's interesting - and counter to my experience of a script served by a well-known (but not google) ad company. We had to jump through some hoops to ensure that the script didn't block - but maybe the script was calling document.write, I don't remember and it was a couple of years ago. p - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvEkJ4ACgkQ9CaO5/Lv0PB0IACgiVesyN9A2noqKAmmGfRLyHFD ysEAn2tOikNdk5VRezxFVJdoJlihV3xo =uN67 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: connection pool issues with mod_proxy_ajp when tomcat is remote
On 13/04/2010 20:53, Russell Uman wrote: howdy! we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache 2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28 mod_proxy_ajp was fairly new in 2.2.3, there are significant improvements in it since then. Upgrading is essential if you want to use it in production. Otherwise, go back to mod_jk - but do try to get the latest version. and we've run into a troubling bug/configuration/networking problem with apache 2.0 and mod_proxy, things are very well behaved. apache has a connection pool of tomcat threads, and when apache kills a child process the corresponding tomcat thread is closed. with apache 2.2 and mod_proxy_ajp, when apache kills a child process, the sometimes the tomcat thread is left hanging in the keep alive state. tomcat waits 120 seconds before terminating the hanging thread. this seems to happen more often under higher traffic, and more often when tomcat is not running on the same server as apache. under traffic, this results in a large number of tomcat threads that have lost their connection to apache and are waiting to timeout, eventually leaving no free threads for legitimate requests. can anyone suggest what could be causing this, or how to troubleshoot? i've tried using the keepalive=on parameter to ProxyPass with no luck. here are some relevant configuration details: with both versions of apache we're using the worker MPM tomcat server.xml: apache 2.0.52/mod_jk 1.2.19 workers.properties worker.default.port=8009 worker.default.type=ajp13 worker.default.connect_timeout=12 worker.default.connection_pool_timeout=120 worker.default.prepost_timeout=12 worker.default.reply_timeout=180 worker.default.retries=1 apache 2.2.3/mod_proxy_ajp ProxyPass / ajp://example.org:8009/ timeout=1800 keepalive=on thanks in advance for any help, and if there's another mailing list for mod_proxy_ajp questions that would be a better recipient please let me know! Nope, hereabouts is good enough. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: connection pool issues with mod_proxy_ajp when tomcat is remote
we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache 2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28 mod_proxy_ajp was fairly new in 2.2.3, there are significant improvements in it since then. Upgrading is essential if you want to use it in production. Otherwise, go back to mod_jk - but do try to get the latest version. thanks! i'm testing now with mod_jk and apache 2.2.3 and things seem to be more cooperative. -- russell uman firebus d-_-b - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: connection pool issues with mod_proxy_ajp when tomcat is remote
On 13/04/2010 23:25, Russell Uman wrote: we're trying to move from apache 2.0.52 with mod_jk 1.2.19 to apache 2.2.3 with mod_proxy_ajp in front of tomcat 5.5.28 mod_proxy_ajp was fairly new in 2.2.3, there are significant improvements in it since then. Upgrading is essential if you want to use it in production. Otherwise, go back to mod_jk - but do try to get the latest version. thanks! i'm testing now with mod_jk and apache 2.2.3 and things seem to be more cooperative. 2.2.3 is quite old, 28 Jul 2006 according to the archive, 2.2.15 is the current release - you should definitely use the latest version and if not that a very recent one. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: connection pool issues with mod_proxy_ajp when tomcat is remote
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russell, On 4/13/2010 3:53 PM, Russell Uman wrote: > tomcat server.xml: > enableLookups="false" redirectPort="8443" protocol="AJP/1.3" > minSpareThreads="5" maxThreads="300" > connectionTimeout="12" URIEncoding="UTF-8" /> > > apache 2.0.52/mod_jk 1.2.19 workers.properties > worker.default.port=8009 > worker.default.type=ajp13 > worker.default.connect_timeout=12 > worker.default.connection_pool_timeout=120 > worker.default.prepost_timeout=12 > worker.default.reply_timeout=180 > worker.default.retries=1 > > apache 2.2.3/mod_proxy_ajp > ProxyPass / ajp://example.org:8009/ timeout=1800 keepalive=on 120 seconds is a long time to wait for an HTTP request to show up. Is that really what you wanted? Also, 1800 seconds (aka 30 minutes) is a long time for a response. Are you sure these are reasonable values for your application? You have set prepost_timeout, but haven't set a ping_mode. Are you seeing pings being sent? 120 seconds is a long time to wait for an AJP connection to be made (or to reply to a ping). Again, are these values sane? Glad to see that mod_jk is working well for you. Pid is right: 2.2.3 was a lng time ago in terms of mod_proxy_ajp. It's unfortunate that package managers (RedHat, CentOS, Debian, etc.) move relatively slowly when it comes to incorporating features such as these. It's understandable, as most admins want stability over everything else. Using mod_jk will give you the best experience if you are stuck with a package-managed version of httpd, but are free to install hand-rolled modules such as mod_jk. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvFJ1kACgkQ9CaO5/Lv0PB7vQCeOZa3xHx7UlsyhZkrl92UspSq VZwAn2pxWrRVhn1r/8BoS0XE/MtEZefK =Uujk -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Q: how to obtain notification when a WebApp is unloaded/reloaded?
Hi, I have a simple question I was unable to find an answer to even after 2 hours of reading documentation, APIs, and (partly) Tomcat source code. In my web application, I'm using the 'reloadable='true'' attribute to Context to reload the application automatically when a .class or jar files changes. To avoid a quickly accumulating memory leak, I need to shut down a service thread my application has started when the web application is reloaded. What API function can be used to notify my application that it is about to be shut down, so that the thread in question can exit? First, is there a standard API that would work also in other J2EE containers besides Tomcat? Second, is there a custom API in Tomcat? Third, if there is no API that a web application could use by itself, is it possible to achieve my goal by writing a custom "thread manager" that is loaded outside the specific web application? If so, are there examples of how to add such a class to the configuration? I'm really interested in a solution that would be contained inside the web application (i.e., first or second above) and that would not require changes to the server configuration, so that it would work in hosted environments where I do not control the Tomcat configuration. I'm using the latest 6.0 release (6.0.20). Thanks. - Godmar
Re: Q: how to obtain notification when a WebApp is unloaded/reloaded?
Godmar, --- On Tue, 4/13/10 at 9:22 PM, Godmar Back wrote: > > What API function can be used to notify my application that > it is about to > be shut down, so that the thread in question can exit? > > First, is there a standard API that would work also in > other J2EE containers > besides Tomcat? > Have you tried implementing a ServletContextListener? http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/ServletContextListener.html - Bob PS Tomcat is not a J2EE container. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Read timed out in tomcat 4.1.31
Dear All,
I am getting a strange issue with an application deployed under tomcat
4(4.1.31) that when I am trying to upload a file through browser along with the
form data to the tomcat, file stream reader getting read timed out exception.
In fileupload application I am using following code snippet.
MultipartParser parser = new MultipartParser((HttpServletRequest) request, 1805
* 1024);
Part aPart;
while ((aPart = parser.readNextPart()) != null) {
if (aPart.isFile() == false) {
//read form data
} else if (aPart.isFile() == true) {
//read file
InputStream is = fPart.getInputStream();
bis = new BufferedInputStream(is);
byte[] buffer = new byte[1024 * 1024];
ByteArrayOutputStream baostream = new ByteArrayOutputStream();
int bytesRead = 0;
while ((bytesRead = bis.read(buffer)) != -1) { --> I am getting
read timed out exception here
}
}
}
}
One more thing what is observed that tomcat is taking 1025m virtual memory :(.
When I upload a file which is smaller in size It's getting succeeded.
Any idea ?
Regards,
Ningappa Koneri
This e-mail and all material transmitted with it are for the use of the
intended recipient(s) ONLY and contains confidential and/or privileged
information. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies and the original message. Any
unauthorized review, use, disclosure, dissemination, forwarding, printing or
copying of this email or any action taken pursuant to the contents of the
present e-mail is strictly prohibited and is unlawful.
The recipient acknowledges that Comviva Technologies Limited or its management
or directors, are unable to exercise control or ensure the integrity over /of
the contents of the information contained in e-mail. Any views expressed herein
are those of the individual sender only and no binding nature of the contents
shall be implied or assumed unless the sender does so expressly with due
authority of Comviva Technologies Limited. E-mail and any contents transmitted
with it are prone to viruses and related defects despite all efforts to avoid
such by Comviva Technologies Limited.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
