Hi
> You're right, it doesn't, at least on Windows.
Just verified that:
r...@www:/opt/java/jdk1.6.0_21# ./bin/java -server -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
r...@www:/opt/java/jdk1
t; Von: Steffen Heil [mailto:li...@steffen-heil.de]
> Gesendet: Dienstag, 31. August 2010 01:46
> An: 'Tomcat Users List'
> Betreff: AW: OFFTOPIC: Java String problem - possible VM bug
>
> Hi
>
>
> > Which 6u21? Just to be confusing, Sun/Oracle has released tw
Hi
> From your original post
> "The exception is only thrown under 64bit Linux Server-VM, within tomcat.
It
> is neither thrown under 64bit Windows, nor on the very same Linux VM as
> standalone testcase, nor when a debugger is remotely attached.
> "
>
> Sounds like you're saying it only happens
Hi
> Which 6u21? Just to be confusing, Sun/Oracle has released two 6u21
levels:
> b06 and b07.
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
So I should update, right?
> http://marc.info/?l=tomcat-u
Hi
> What version tomcat?
I see this under 6.0.29 [and I think under 6.0.18 before, but I am not
sure], but as this is pure java code, not calling any tomcat code and not
probably affected by tomcat code, I don't think that matters. (That's why I
labeled that off-topic.)
However, if it even coul
