-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger,
Varley, Roger wrote:
> I've finally sussed it. Because we're still in development, we've
> been fairly cavalier about how we've been calling the initial servlet
> (as localhost/servlet, hostname/servlet and by IP address/servlet)
> and some of
>
> 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 stran
Well, haven't looked at the code of either version (4.x, 5.x),
however, I figured that 5.x makes a bit more use of Java's
threading-features. Besides, unsynchronized hashmaps are a
#1-candidate for errors that are either strange, not reproducible and
in cases where you think you should file a bug-
>
> 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 Roger,
just a shot from the hip:
Maybe you want to overwrite the method public int hashcode() for the
objects being put into the hashmap - you should not rely on the
default implementation of java.lang.Object.hashcode().
Besides, HashMap is not thread-safe, have you tried it with a
thread-sa
> 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. Th
> From: Varley, Roger [mailto:[EMAIL PROTECTED]
> Subject: Strange behaviour after upgrade to 5.5.20
>
> 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 under the new setup.
I think
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 under
