Hi Stephan
Thanks for posted this, you have saved a lot of time for me,
unfortunately for me though I can't go back to JVM 1.5
Stephan Schwab wrote:
Unfortunately yesterday we had to switch back to JVM 1.5, as the same
symptoms have shown up again. Seems that there is still a problem and JVM
Unfortunately yesterday we had to switch back to JVM 1.5, as the same
symptoms have shown up again. Seems that there is still a problem and JVM
1.6. update 2 is not the solution.
--
View this message in context:
http://www.nabble.com/T5-on-JDK-1.6-or-newer-tf4324659.html#a12582298
Sent from the
On 9/5/07, Stephan Schwab [EMAIL PROTECTED] wrote:
Although this is really not a good way to investigate a bug (lack of time), I
still want to report that our application has been running fine since
upgrading to JVM 6 update 2. So it seems that it was the JVM bug Howard
mentioned before and
Although this is really not a good way to investigate a bug (lack of time), I
still want to report that our application has been running fine since
upgrading to JVM 6 update 2. So it seems that it was the JVM bug Howard
mentioned before and it is indeed fixed. If it shows up again, I'll post
We moved our production app Savila from JDK 1.6 back to 1.5. That's now more
than a week ago. Since we did no further hangs have shown up.
Unfortunately I have not been able to investigate any further due to time
constraints (the client project). But I'm planning on following the
suggestions
On 25/08/2007, at 3:01 AM, Stephan Schwab wrote:
We've been experiencing strange behaviour of our now growing
application
Savila and as well with another project we are working on. Both use
Tapestry
5.0.5. Our development machines run with Mac OS X and we use JDK
1.5 that
comes with it.
Hrm... I've been running a reasonably robust production app on T5.05 and
JDK 1.6 and haven't seen any hangs. I develop on Jetty but deploy to
SJSAS, which runs Catalina (Tomcat's servlet container). Production is
Linux and development is Windows. I also have 92 integration tests and
unit tests
An earlier posting on this list highlighted a bug in concurrency on
some version of JDK 1.6. Please check into that, the symptoms sound
similar to what you see.
On 8/24/07, Stephan Schwab [EMAIL PROTECTED] wrote:
We've been experiencing strange behaviour of our now growing application
Savila
: T5 on JDK 1.6 or newer
An earlier posting on this list highlighted a bug in concurrency on
some version of JDK 1.6. Please check into that, the symptoms sound
similar to what you see.
On 8/24/07, Stephan Schwab [EMAIL PROTECTED] wrote:
We've been experiencing strange behaviour of our
