You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Ben Stover <bx...@yahoo.co.uk> on 2009/09/04 12:41:11 UTC
Re: Error when opening TestPlan with v2.3.4 which was created with v2.3.2 - Testplan "Update" possible ?
Hmm, why should I add some JMS jars (which ?) to the new installation as you suggested ?
I never added some JMS jars to the old v2.3.2 installation.
So I expect that I do not have to add them in a new version v2.3.4 as well.
Or does JMeter really forces users in newer versions to add explicitely these jars ?
That would be a step backwards in user-friendlyness
Ben
On Fri, 4 Sep 2009 11:11:56 +0100, sebb wrote:
>On 04/09/2009, Ben Stover <bx...@yahoo.co.uk> wrote:
>> I created a Testplan with v2.3.2. Later I installed v2.3.4.
>>
>> When I start now v2.3.4 and try to open the old, existing Testplan then JMeter v2.3.4 tells me in an error popup:
>>
>> Error in TestPlan - see log file.
>>
>> And log file tells me (see bottom of this email).
>>
>> Whats wrong?
>>
>> Is there a workaround for this problem? How can I "upgrade" a TestPlan to a newer version ?
>>
>> Ben
>>
>> ---- Debugging information ----
>> message : javax/jms/Message
>> cause-exception : java.lang.NoClassDefFoundError
>> cause-message : javax/jms/Message
>Sigh. Did you add the JMS jars to the new installation?
>> first-jmeter-class : org.apache.jmeter.save.converters.TestElementConverter.unmarshal(TestElementConverter.java:104)
>> class : org.apache.jmeter.save.ScriptWrapper
>> required-type : org.apache.jmeter.protocol.jms.sampler.JMSSampler
>> path : /jmeterTestPlan/hashTree/hashTree/hashTree/JMSSampler
>> line number : 126
>> -------------------------------
>> 2009/09/04 09:06:12 WARN - jmeter.gui.action.Load: Unexpected error java.lang.Exception: Error in TestPlan - see log file
>> at org.apache.jmeter.gui.action.Load.insertLoadedTree(Load.java:153)
>> at org.apache.jmeter.gui.action.Load.loadProjectFile(Load.java:108)
>> at org.apache.jmeter.gui.action.LoadRecentProject.doAction(LoadRecentProject.java:65)
>> at org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:80)
>> at org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:42)
>> at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:59)
>> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
>> at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
>> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
>> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>> at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>>
>>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Error when opening TestPlan with v2.3.4 which was created with
v2.3.2 - Testplan "Update" possible ?
Posted by sebb <se...@gmail.com>.
On 04/09/2009, Ben Stover <bx...@yahoo.co.uk> wrote:
> Hmm, why should I add some JMS jars (which ?) to the new installation as you suggested ?
>
> I never added some JMS jars to the old v2.3.2 installation.
> So I expect that I do not have to add them in a new version v2.3.4 as well.
>
> Or does JMeter really forces users in newer versions to add explicitely these jars ?
> That would be a step backwards in user-friendlyness
The JMS jar is being referenced from a JMS Sampler in the test plan;
JMeter has never included a JMS implementation as part of the standard
download.
I don't know why it works for you in 2.3.2 if you say you did not add
the JMS jars to the JMeter installation. Are you using the same Java
installation? If not, maybe one of them has the JMS jars.
If you raise a Buzilla issue, you can attach a simple JMX that shows
the problem - i.e. works in 2.3.2 and does not work in 2.3.4. Also
please attach the jmeter.log files for both runs.
> Ben
>
>
> On Fri, 4 Sep 2009 11:11:56 +0100, sebb wrote:
>
>
> >On 04/09/2009, Ben Stover <bx...@yahoo.co.uk> wrote:
> >> I created a Testplan with v2.3.2. Later I installed v2.3.4.
> >>
> >> When I start now v2.3.4 and try to open the old, existing Testplan then JMeter v2.3.4 tells me in an error popup:
> >>
> >> Error in TestPlan - see log file.
> >>
> >> And log file tells me (see bottom of this email).
> >>
> >> Whats wrong?
> >>
> >> Is there a workaround for this problem? How can I "upgrade" a TestPlan to a newer version ?
> >>
> >> Ben
> >>
> >> ---- Debugging information ----
> >> message : javax/jms/Message
> >> cause-exception : java.lang.NoClassDefFoundError
> >> cause-message : javax/jms/Message
>
> >Sigh. Did you add the JMS jars to the new installation?
>
> >> first-jmeter-class : org.apache.jmeter.save.converters.TestElementConverter.unmarshal(TestElementConverter.java:104)
> >> class : org.apache.jmeter.save.ScriptWrapper
> >> required-type : org.apache.jmeter.protocol.jms.sampler.JMSSampler
> >> path : /jmeterTestPlan/hashTree/hashTree/hashTree/JMSSampler
> >> line number : 126
> >> -------------------------------
> >> 2009/09/04 09:06:12 WARN - jmeter.gui.action.Load: Unexpected error java.lang.Exception: Error in TestPlan - see log file
> >> at org.apache.jmeter.gui.action.Load.insertLoadedTree(Load.java:153)
> >> at org.apache.jmeter.gui.action.Load.loadProjectFile(Load.java:108)
> >> at org.apache.jmeter.gui.action.LoadRecentProject.doAction(LoadRecentProject.java:65)
> >> at org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:80)
> >> at org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:42)
> >> at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:59)
> >> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
> >> at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
> >> at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
> >> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
> >> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
> >> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
> >> at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
>
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org