I figured as much I'm trying to build something right now to show case this oddity. ________________________________________ From: Mark Thomas <ma...@apache.org> Sent: Friday, October 03, 2014 1:50 PM To: Tomcat Users List Subject: Re: Tomcat JVM Crash
On 03/10/2014 19:38, Chad Maniccia wrote: > Hi Mark, > > Thanks for replying. I actually reported this bug to Oracle before contacting > this group. They contacted me once but then never replied again. I'd > appreciate it if you could bring it to their attention again. > > https://bugs.openjdk.java.net/browse/JDK-8058284 Happy to do that once you have a repeatable test case. Frankly, without one, I doubt this is going to get much attention. Mark > > This bug is kind of elusive as a form that is crashing today might not crash > tomorrow, I suspect it is because headers, cookies, session keys etc have > changed. I'll see if I can reproduce it by creating a testing form. > > Can anyone tell me why this line causes the site to not crash? > > -XX:CompileCommand=exclude,com/sun/crypto/provider/*.* > > P.S. > Igal thanks for your support. > ________________________________________ > From: Mark Thomas <ma...@apache.org> > Sent: Friday, October 03, 2014 1:14 PM > To: Tomcat Users List > Subject: Re: Tomcat JVM Crash > > On 03/10/2014 17:11, Igal @ getRailo.org wrote: >>> Whose problem is this: Google, Apache Tomcat, GoDaddy(SSL), or Oracle? >>> regardless of whose fault this is, Tomcat should be patched so that it >>> doesn't crash. > > The general position of the Tomcat developers is that we do *not* patch > Tomcat to work around bugs in third party code. > > There have been exceptions in the past but - since this JVM bug as a > workaround available - I very much doubt that Tomcat will be patched to > avoid this (even if such a patch was possible which looks unlikely). > >> can you produce a reduced test case so that the good people at Tomcat >> can reproduce it on their end and patch it? > > A reproducible test case is definitely a good thing but it needs to go > to Oracle, not to the Tomcat devs. > > Note we do have some contacts with Oracle we can use to ensure a bug > report gets in front of the right people. > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
