Re: force embedded tomcat 7 to listen on ALL adresses

2012-07-21 Thread Alexander Shutyaev
Hi Mark, The problem is that I have a dynamic app where webapps come and go, so I can't call addWebapp() before calling start(). The best I can do is a delayed start() - in my method that calls addWebapp() I can make a check - and if this is the first time - call start() after addWebapp(). Will th

Re: force embedded tomcat 7 to listen on ALL adresses

2012-07-21 Thread Mark Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/07/2012 19:31, Alexander Shutyaev wrote: > Hi Christopher, > > I've found a solution to my problem although I believe it's more > accurate to say I guessed it :) Maybe you'll be able to explain it > to me. Here is the complete code: > > Tomca

Re: Location of Tomcat 7 jvm defualt settings...

2012-07-21 Thread Tony Anecito
Lots of time I apply best practices that I learn over time or are recommended by experts (Like Mark Thomas). You do that first as early in the development life cycle as possible. Funny I guess how these best practices come from developers, vendors (like Sun and now Oracle) and DBA's ect. If you

Re: Location of Tomcat 7 jvm defualt settings...

2012-07-21 Thread David kerber
On 7/21/2012 11:09 AM, chris derham wrote: ... 1. Create a automated test script to simulate some load 2. You increase the load until the bring the webapp to its knees - either>80% CPU or responses taking>1/2 sec to return 3. Critical step - you tell your bosses the maximum leve

Re: Location of Tomcat 7 jvm defualt settings...

2012-07-21 Thread chris derham
On Fri, Jul 20, 2012 at 6:31 PM, Tony Anecito wrote: > Thanks for the quick reply Mark. > Yes I saw your comments in one of your presentations about profilier and I > am a fan of visualvm and have profiled Tomcat in the past but when down to > 1-2msec not sure how much the profilier can pick up.

Re: java.sql.SQLException: No more data to read from socket

2012-07-21 Thread Felix Schumacher
Am Samstag, den 21.07.2012, 08:44 +0800 schrieb vijay mathew: > For the last 2 failures, this issue appeared on Monday and DB gets restarted > every Saturday. So I assume that this issue has to do something with the DB > restart for the last 2 failures. > > However 1 months back, the same issue