Well, check you Sysdeo Plugin settingts. See if they point to a
different server.xml file. From the stack trace it appears the
server.xml is broken. Usually this file is found in
tomcat/conf/server.xml but Sysdeo plugin might have changed it.
Could this be caused by Tomcat using a
Hi
I've been undertaking a major tomcat upgrade, moving from
Tomcat 4.1.31 running on Win NT with IIS 1.2 to Tomcat 5.5.20
running on Win 2003 Server with IIS 6.0. I'm just about
there, but I've got a problem with a servlet that runs fine
under the old setup but exhibits strange
I think you're going to have to be a bit less vague if you
want any real
responses. A description of the actual symptoms, exact error
messages,
log entries, etc., would help. Strange behaviour doesn't
give anyone
much to go on.
Sorry, Im still grappling with the new Tomcat. There are
Besides, HashMap is not thread-safe, have you tried it with a
thread-safe implementaion (i.e. Map m =
Collections.synchronizedMap(new HashMap(...));)
Yep, that fixed it. Interestingly, the original servlet using the hashmap
continues to work fine with Tomcat 4.1.31. I can only surmise
Hi
I've been undertaking a major tomcat upgrade, moving from Tomcat 4.1.31 running
on Win NT with IIS 1.2 to Tomcat 5.5.20 running on Win 2003 Server with IIS
6.0. I'm just about there, but I've got a problem with a servlet that runs fine
under the old setup but exhibits strange behaviour
problems. It does take a bit of study to
understand what you
are seeing. Here is an article I use that covers both Windows
and *nix:
http://java.sun.com/developer/technicalArticles/Programming/St
acktrace/index
.html
HTH - Richard
-Original Message-
From: Varley, Roger
I have classes which deal with tables individually.
In each class, it has the following lines to get connection pooling
and then commit a single table.
Context envCtx = (Context) ctx.lookup(java:comp/env);
DataSource ds = (DataSource) envCtx.lookup(jdbc/myERP);
conn = ds.getConnection();
