Tomcat auf MS Cluster?

Hello, we're planning to run Tomcat Apache 5.0.28 on a MS Server 2008 R2 64Bit Ent. Failover Cluster. Does anyone has productive experience on that? Does it work, How good does it work, .? Things to be aware of? (If required, Tomcat 6.* is possible but we'd prefer Tomcat 5.0.28 to start

Re: Tomcat auf MS Cluster?

On 06/10/2010 10:24, Stefan Rainer wrote: we're planning to run Tomcat Apache 5.0.28 on a MS Server 2008 R2 64Bit Ent. Failover Cluster. Does anyone has productive experience on that? Does it work, How good does it work, .? Sorry, no recent MS cluster experience here. I have some horror

Re: [OT] Serialization

Chris, Not always it seems adequate to write to the mailing list - so you marked my question with [OT] which was a further hint for me to write to you directly. Concerning serialization I answered already on 04.10.2010. The build in serialization tool of java has probably high performance

RE: Tomcat auf MS Cluster?

I agree with Mark, upgrade your Tomcat to a supported rev. If possible, go to the latest 6.0, otherwise, 5.5.x would be good, but it will become unsupported shortly when 7.0.x becomes official. I currently run production 5.5.29 in your environment, but using standalone servers, not clustered.

Re: Tomcat auf MS Cluster?

On 06/10/2010 15:16, Jeffrey Janner wrote: I agree with Mark, upgrade your Tomcat to a supported rev. If possible, go to the latest 6.0, otherwise, 5.5.x would be good, but it will become unsupported shortly when 7.0.x becomes official. Less supported maybe. The rough guide is: - 7.0.x -

RE: Tabbed browsers sharing session - work around.

We have a similar issue. Our users cannot login to our app using two separate user accounts concurrently. (Unless you use IE6 or login as a separate user in Chrome, Firefox and IE.) Nick -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: 05 October

Tomcat 6.0.29: Failed to initialize the SSLEngine

Hi, I'm trying to install Apache Tomcat 6.0.29 on a Debian GNU/Linux 5.0.4 32bit with kernel release 2.6.26-2-686 with APR and SSL. JDK 1.6.0_21 APR 1.2.9 OpenSSL 0.9.8 There seems to be a problem with the Tomcat Native library 1.1.20: 06.10.2010 15:02:51

NullPointerException when Tomcat calls org.apache.catalina.connector.Request.parseParameters

Hi, I'm using Tomcat 6.0.26 with Java 1.6. I'm getting a strange NullPointerException from a Tomcat class. My code is … if (request != null request.getParameter(FORM_SUBMIT_SITE_NAME + FormSubmit) != null) { and the stack trace is below. I have verified I'm not passing a

Re: NullPointerException when Tomcat calls org.apache.catalina.connector.Request.parseParameters

laredotornado wrote: Hi, I'm using Tomcat 6.0.26 with Java 1.6. I'm getting a strange NullPointerException from a Tomcat class. My code is … if (request != null request.getParameter(FORM_SUBMIT_SITE_NAME + FormSubmit) != null) { and the stack trace is below. I have

Disable class monitoring for reloading container classes

There's a backgroundProcessor method in tomcat that checks whether container classes need to be reloaded, and checks for session expirations. Is it possible to disable this method, like you can disable class reloading for the context with reloadable=false? I'm using tomcat 6.0.18 on an IBM i

Re: Disable class monitoring for reloading container classes

Jane Muse wrote: There's a backgroundProcessor method in tomcat that checks whether container classes need to be reloaded, and checks for session expirations. Is it possible to disable this method, like you can disable class reloading for the context with reloadable=false? I'm using tomcat

Re: NullPointerException when Tomcat calls org.apache.catalina.connector.Request.parseParameters

2010/10/6 laredotornado laredotorn...@gmail.com: Hi, I'm using Tomcat 6.0.26 with Java 1.6.  I'm getting a strange NullPointerException from a Tomcat class.  My code is …                if (request != null request.getParameter(FORM_SUBMIT_SITE_NAME + FormSubmit) != null) { and the

RE: Disable class monitoring for reloading container classes

André - you are correct. We actually modified autoDeploy attribute on the Host element to false, and not reloadable in the application context xml, and then it worked on IBM I V7R1. Your 3rd point below is probably the key to why it works on one version of the O/S and not the other. The version

Tomcat5.5 MySQL14.12 java.net.SocketException: Broken pipe

I am getting this during mysql connection (about once a week). I have read the thread on MySQL forum, which has a solution, but the link to the solution is broken and points back to the same page. Suggestions have been use autoconnect=true Another was that the server timeout was shorter than

Re: Tomcat5.5 MySQL14.12 java.net.SocketException: Broken pipe

To your mysql Resource definition below I would add validationQuery=SELECT 1 That should prevent your application from getting handed stale db connections from your pool. Take a look at the testOnBorrow and validationQuery definitions here http://commons.apache.org/dbcp/configuration.html Jason