[ grinder-Bugs-3517489 ] unable to record scripts with 3.9 beta
SourceForge.net <[email protected]> Fri, 13 Apr 2012 15:09:19 -0700
| Newsgroups | gmane.comp.java.grinder.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #3517489, was opened at 2012-04-13 06:43 Message generated for change (Comment added) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3517489&group_id=18598 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: TCPProxy Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: greghmerrill () Assigned to: Philip Aston (philipa) Summary: unable to record scripts with 3.9 beta Initial Comment: I can't generate scripts with the 3.9 beta. When I stop the proxy, I get the following exception: 10:09:09.878 [main] ERROR: Not supported: javax.xml.transform.stax.StAXSource@1979eb 10:09:09.878 [main] ERROR: com.sun.org.apache.xml.internal.dtm.DTMException: Not supported: javax.xml.transform.stax.StAXSource@1979eb 10:09:09.878 [main] INFO : Engine exited Seems like there is some new dependency added in the context of XSLT processing? I am running JDK 1.6.0_17 java -cp grinder.jar net.grinder.TCPProxy -http jython -console ---------------------------------------------------------------------- >Comment By: greghmerrill () Date: 2012-04-13 15:09 Message: I didn't realize it earlier, but I had some endorsed jars setup for my JDK. So that's why I saw the issue but you didn't. Once removed, I no longer see this issue. So this is not a Grinder problem per se. Closing this bug. ---------------------------------------------------------------------- Comment By: Philip Aston (philipa) Date: 2012-04-13 08:02 Message: This is a side-effect of the fix for 3512095. It appears the XSLT engine in your JVM doesn't support a StAXSource. I'd assumed that any 1.6 JVM would be fine. Can you double check your JVM version (java -version). FWIW, all the following work fine for me: java version "1.6.0_23" OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre11-0ubuntu1.11.10.2) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b51) Java HotSpot(TM) Server VM (build 17.0-b17, mixed mode) java version "1.6.0" Java(TM) SE Runtime Environment (build 1.6.0-b105) BEA JRockit(R) (build R27.2.0-131-78843-1.6.0-20070320-1511-linux-ia32, compiled mode) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3517489&group_id=18598 ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2