AW: Variables in server.xml leads to error when stopping Tomcat

Hello Torsten, hello Chris > You need to put "-Dport.shutdown=12345" to the JAVA_OPTS because the > stop process needs that port. Thanks for the answer, this worked for me. > Henning, the reason you get the error message and Tomcat /still/ stops is > because the shutd

Variables in server.xml leads to error when stopping Tomcat

ina:type=Server: portWithOffset = 12345; Do you have any idea, why this error message happens and how we can get rid of it, when using variables in server.xml for the shutdown port. Regards Henning INTERNAL - To unsu

NPE in ResultSetImpl.next() using tomcat jdbc pool

uring this time, the thread was seemingly stuck on SocketInputStream.socketRead0 (see below for stack trace), even though I set the sockettimeout when creating the db pool. Best regards Henning Rohlfs @Override public List getUUIDsByTable( final String table) throws TableNotFoun

Re: Fw: Applet Servlet communication in Tomcat 7

On Sat, Oct 9, 2010 at 7:43 PM, Ram karthik wrote: > basic: Applet made visible > basic: Starting applet > network:  Connecting https://localhost/utilApp/ servlet/Ut ilAppsServ > let?mode=0 > & fileName= filea.ARA with proxy=DIRECT > network: Connecting https://localhost/utilApp/ servlet/Ut ilApp

Re: Tomcat Consultant

http://www.springsource.com/support/professional-services SpringSource claims to be able to do this kind of thing. They were the first google result for "tomcat consultant." Did you not search for that or did you disregard it? On Fri, Sep 24, 2010 at 10:25 AM, tdelesio wrote: > > My fortune 500

Re: Tomcat JULI resets JDK logging?

nager will however simply reset all logging. Thanks, Henning Am Mittwoch, den 10.02.2010, 14:07 -0500 schrieb Christopher Schultz: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Henning, > > On 2/10/2010 4:47 AM, Henning wrote: > > Yes I did [use a separate ClassLoader]

Re: Tomcat JULI resets JDK logging?

u are involved with JULI, you might be able to provide a good solution. I thought testing whether the current LogManager is indeed JULI's before calling reset could be a remedy. But as I don't know JULI by heart, there might be other problems in that. Thanks, Henning On Tue, 2010-02-09

Tomcat JULI resets JDK logging?

So, I am wondering whether a) there is a way to configure JULI to not touch other loggers/handlers? or b) any other solution to my problem? Thanks, Henning Ps.: private static void removeContext(MyCatalina c, StandardContext sc) {

Re: Embedding tomcat and bug in org.apache.catalina.startup.Catalina

ok, done. Thanks, henning Am Mittwoch, den 03.02.2010, 13:08 +0300 schrieb Konstantin Kolinko: > public class MyCatalina extends Catalina { > >public Server getServer() { > >ret

Embedding tomcat and bug in org.apache.catalina.startup.Catalina

se or whether there is a better way of using server.xml while embedding tomcat but without using the Catalina class. Thanks, Henning Sample code: // // MyCatalina c = new MyCatalina(); File cf = new File("conf/server.xml"); c.setConfig(cf.getAbsolutePath()); c.setUseShutdownHook(fals

Turn off logging of Exceptions

logged by org.apache.catalina.core.StandardWrapperValve. Is it possible to suppress this? I played a little bit with java.util.logging configuration, but i always ended with the need to configure it _outside_ of tomcat. Is it possible to do it from within the web application? Regards, Henning -- Neu: GMX Doppel-FLAT mi