【问题标题】:Errors when Using Grinder on JIRA 6.1.1 instances在 JIRA 6.1.1 实例上使用 Grinder 时出错
【发布时间】:2013-11-07 19:48:43
【问题描述】:

在 JIRA 实例上配置 Grinder 时出现以下错误,按照 https://confluence.atlassian.com/display/ATLAS/JIRA+Performance+Testing+with+Grinder#JIRAPerformanceTestingwithGrinder-Prerequisites 的所有说明进行操作

错误: $ cat project_manager_8/error_xxxx004.fm.XXXXX.com-0.log

11/7/13 7:44:35 PM (process xxxx004.fm.XXXXX.com-0): Error running worker process (Java exception initialising test script
        File "/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./env.py", line 35, in request
        File "/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./dashboard.py", line 9, in __init__
        File "/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./interactions.py", line 35, in ?
        File "./agent_project_manager.py", line 4, in ?)
Java exception initialising test script
        File "/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./env.py", line 35, in request
        File "/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./dashboard.py", line 9, in __init__
        File "/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./interactions.py", line 35, in ?
        File "./agent_project_manager.py", line 4, in ?
Caused by: net.grinder.script.NotWrappableTypeException: Failed to wrap http://jira-fm-dev.devtools.XXXXX.com:8080/

        at net.grinder.engine.process.instrumenter.MasterInstrumenter.createInstrumentedProxy(MasterInstrumenter.java:99)
        at net.grinder.engine.process.TestData.createProxy(TestData.java:93)
        at net.grinder.script.Test.wrap(Test.java:100)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at org.python.core.PyReflectedFunction.__call__(Unknown Source)
        at org.python.core.PyMethod.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at org.python.core.PyInstance.invoke(Unknown Source)
        at env$py.request$6(/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./env.py:35)
        at env$py.call_function(/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./env.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(Unknown Source)
        at dashboard$py.__init__$2(/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./dashboard.py:9)
        at dashboard$py.call_function(/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./dashboard.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(Unknown Source)
        at org.python.core.PyInstance.__init__(Unknown Source)
        at org.python.core.PyClass.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at interactions$py.f$0(/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./interactions.py:35)
        at interactions$py.call_function(/opt/atlassian-jira-performance-tests/target/classes/test_scripts/./interactions.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyCode.call(Unknown Source)
        at org.python.core.imp.createFromCode(Unknown Source)
        at org.python.core.imp.createFromPyClass(Unknown Source)
        at org.python.core.imp.loadFromSource(Unknown Source)
        at org.python.core.imp.find_module(Unknown Source)
        at org.python.core.imp.import_next(Unknown Source)
        at org.python.core.imp.import_name(Unknown Source)
        at org.python.core.imp.importName(Unknown Source)
        at org.python.core.ImportFunction.load(Unknown Source)
        at org.python.core.ImportFunction.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at org.python.core.__builtin__.__import__(Unknown Source)
        at org.python.core.imp.importAll(Unknown Source)
        at org.python.pycode._pyx0.f$0(./agent_project_manager.py:4)
        at org.python.pycode._pyx0.call_function(./agent_project_manager.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyCode.call(Unknown Source)
        at org.python.core.Py.runCode(Unknown Source)
        at org.python.core.__builtin__.execfile_flags(Unknown Source)
        at org.python.util.PythonInterpreter.execfile(Unknown Source)
        at net.grinder.engine.process.jython.JythonScriptEngine.initialise(JythonScriptEngine.java:83)
        at net.grinder.engine.process.GrinderProcess.run(GrinderProcess.java:259)
        at net.grinder.engine.process.WorkerProcessEntryPoint.run(WorkerProcessEntryPoint.java:87)
        at net.grinder.engine.process.WorkerProcessEntryPoint.main(WorkerProcessEntryPoint.java:59)

【问题讨论】:

  • 你能包含失败的python代码吗? NotWrappableTypeException 让我认为磨床脚本本身已损坏,并且您正试图将错误的东西变成测试。您使用的 Grinder 版本也会有所帮助。当您在 jira 之外运行脚本时,您的脚本能否正常运行?
  • 感谢 Travis 的回复...不幸的是,我正在使用来自 bitbucket.org/atlassian/jira-performance-tests/src 的原样,它也不包含任何版本名称。
  • 这没什么好说的。如果他们是正在破坏的 Grinder 脚本的作者,我建议直接联系 Jira/Atlassian 人员。

标签: jira performance-testing grinder


【解决方案1】:

您可以尝试在您的grinder.properties 文件中将grinder.dcrinstrumentation 设置为false。 不确定其他影响,但在此之后我能够让我的工作。

标记。

【讨论】:

    【解决方案2】:

    Atlassian 的性能测试 git 存储库中的最后一次签入是在 2013 年 1 月,您的问题是从 2013 年 11 月开始的。

    Atlassian 最近似乎没有更新他们的性能测试脚本。

    但是在使用 Grinder 进行测试的页面上, https://confluence.atlassian.com/display/ENTERPRISE/JIRA+Performance+Testing+with+Grinder 来自 Atlassian 的某个人说他们正在重新编写 JMeter 脚本。

    如果您想查看他们拥有的旧 JMeter 脚本: https://confluence.atlassian.com/display/JIRA/Performance+Testing+Scripts 提到两个文件名,jmeter-test-setup.jmx 和 jmeter-test-fixedload.jmx 谷歌搜索这些 + Github 会导致一个 github 页面,其中包含一个 2013 版本的测试,由名为 Emidio Stani 的人(IT 专业人士)编写,但是在(2014 年底)当前的 JIRA 上运行不佳。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2013-07-31
      • 1970-01-01
      • 2019-06-14
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2012-08-01
      相关资源
      最近更新 更多