Thanks for your replies. It would appear that the problem is indeed caused by a bug in the JVM - specifically in 1.6.0u17. This is now working fine on all servers running 1.6.0u22. Not sure of the specific bug it's hitting, but this might be something good to know for any problems anyone else has of a similar nature.
Thanks again, Jimmi > From: Toni Menzel <[email protected]> > Subject: Re: PAXExam - A fatal error has been detected by the Java > Runtime Environment > To: General OPS4J <[email protected]> > Message-ID: > <cagnabnjbfjnnwmhzvl4vtk+zo8qkw8dxp+rla+cvmzjxvdz...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Are you using native code (JNI) ? Though we cannot do much about the > crashes. But i guess framework should also crash when not using Exam. Can > you confirm that ? Or is there any potential difference ? For example, Exam > may use another JDK for the framework under test compared to what you are > using when running standalone. > Just a few thoughts.. > > Toni > > On Tue, Nov 1, 2011 at 8:04 PM, Karl Pietrzak <[email protected]> wrote: > > > On Tue, Nov 1, 2011 at 7:01 AM, Jimmi Dyson > > <[email protected]>wrote: > > > >> Hi there, > >> > >> I've been really impressed with how easy PAX Exam has been to use to > >> create integration tests for OSGi bundles, but I've hit upon a bug that I > >> can't seem to figure out. It could be a bug in the JVM, but I'd really > >> appreciate your input to see if it's a known problem with any workaround. > >> > >> We experienced the same issue using PAX Exam 1 so I thought I'd try out > >> PAX Exam 2 (which I must say is definitley a step in the right direction), > >> but the issue still occurs. This very well could be environmental so any > >> pointers would be appreciated. > >> > >> On my dev laptop, 64 bit JDK 1.6.0_26, everything works fine. When this > >> gets built on a Jenkins slave, using 32 bit JDK 1.6.0_17-b04, we get the > >> following failure: > >> > > > > Do you have to use 1.6.0_17? It has some pretty large security issues > > (e.g., http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3865). > > > > _______________________________________________ > > general mailing list > > [email protected] > > http://lists.ops4j.org/mailman/listinfo/general > > > > > > > -- > Toni Menzel > Independent Software Developer > Professional Profile: http://okidokiteam.com > [email protected] > http://www.ops4j.org - New Energy for OSS Communities - Open > Participation Software. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.ops4j.org/pipermail/general/attachments/20111103/f4e52380/attachment.html> </pre><hr/><p style="margin: 0px; font-family:verdana; font-size:xx-small">NOTICE: This message contains privileged and confidential information intended only for the addressee. If you have received this message in error you must not disseminate, copy or take action on it; please notify [email protected] Opinions expressed in this message are those of the sender and do not necessarily represent those of Specsavers. Although this e-mail and any attachments are believed to be virus free, e-mail communications are not 100% secure and Specsavers makes no warranty that this message is secure or virus free. All references to Specsavers means Specsavers Optical Superstores Limited, a company limited by shares and registered in England under number 1721624 of Forum 6, Parkway, Solent Business Park, Whiteley, Fareham, Hampshire, PO15 7PA. Nothing in this transmission shall or shall be deemed to constitute an offer or acceptance of an offer or otherwise have the effect of forming a contract by electronic communication. Your name and address may be stored to facilitate communication. </p> <hr/>. _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
