I've fixed the Xstream crash - and found the cause of the Java 1.5
problem (see other e-mail).
Thanks for reporting the problem.
S.
On 14/10/05, sebb [EMAIL PROTECTED] wrote:
Turns out I was using a Java Sampler without any Result Data - this
causes a crash in XStream when saving as 2.1
Turns out I was using a Java Sampler without any Result Data - this
causes a crash in XStream when saving as 2.1 format. Obviously a bug,
but not related to this.
S.
On 12/10/05, sebb [EMAIL PROTECTED] wrote:
Looks like this needs further investigation - I'm getting some odd
results with Java
I ran an some more tests and the problem is caused by the combination
of jars that I use. A fresh download of jmeter does not have this
problem.
On 10/12/05, Bogdan Calmac [EMAIL PROTECTED] wrote:
I have a very simple test plan which looks like this:
TestPlan
ThreadGroup
HttpRequest
Finally, te reason was that I deleted xalan, xerces and xml-apis
assuming that they are included in Java 1.5. Are the versions that
come with jmeter newer than those in Java 1.5? Or does jmeter strictly
depend on the bundled jars?
On 10/12/05, Bogdan Calmac [EMAIL PROTECTED] wrote:
I ran an some
Without the 3 jars, the XML results generated by JMeter (from any
listener) under Java 1.5 has
?xml version=1.0 encoding=UTF-8?
before all sampleResult tags.
Without looking at the code, I would guess there is some issue with
the code generating the XML, because this problem only happens when
Looks like this needs further investigation - I'm getting some odd
results with Java 1.5 both with and without the jars.
S.
On 12/10/05, Bogdan Calmac [EMAIL PROTECTED] wrote:
Without the 3 jars, the XML results generated by JMeter (from any
listener) under Java 1.5 has
?xml version=1.0
6 matches
Mail list logo
