You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2020/07/16 13:19:13 UTC

[Bug 64608] New: .JMX file working fine in GUI but getting error while execute from command line

https://bz.apache.org/bugzilla/show_bug.cgi?id=64608

            Bug ID: 64608
           Summary: .JMX file working fine in GUI but getting error while
                    execute from command line
           Product: JMeter
           Version: 5.2.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: atul.chauhan@dynamicelements.no
  Target Milestone: JMETER_5.3.1

.jmx file working fine while trying to execute from GUI but when i try from
command like getting error as below.

Error in NonGUIDriver org.apache.jorphan.util.JMeterStopTestException:
ModuleController:Module Controller has no selected Controller (did you rename
some element in the path to target controller?), test was shutdown as a
consequence

i have checked all thing but found nothing wrong in script.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 64608] .JMX file working fine in GUI but getting error while execute from command line

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=64608

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om
         Resolution|---                         |WORKSFORME

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Message means that the Module Controller does not reference any valid
controller.
Search for it, and fix the problem.

If issue persists, you can reopen the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.