RAD 7.5 和磨床
我想知道是否有人尝试过将 Grinder 与 RAD 7.5 集成。
问题：当尝试从 Grinder TCP 代理运行我录制的 jpython 脚本时，我在 RAD 7.5 详细信息中收到以下错误
：
- RAD 7.5
- Grinder：3.6
我尝试创建一个基本脚本，但在 RAD 中发生了同样的事情。我想知道有人遇到过这种情况吗？或者如果您有幸在 RAD 7.5 内设置了 Grinder。
错误消息：
线程“main”java.lang.UnsupportedOperationException 中出现异常：无法获取功能，正在执行重新转换环境的处置
at sun.instrument.InstrumentationImpl.isRetransformClassesSupported0(Native Method)
at sun.instrument.InstrumentationImpl.isRetransformClassesSupported(InstrumentationImpl.java:112)
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 net.grinder.engine.process.dcr.DCRContextImplementation.create(DCRContextImplementation.java:74)
at net.grinder.engine.process.GrinderProcess.run(GrinderProcess.java:309)
at net.grinder.engine.process.WorkerProcessEntryPoint.run(WorkerProcessEntryPoint.java:86)
at net.grinder.engine.process.WorkerProcessEntryPoint.main(WorkerProcessEntryPoint.java:58)
2011 年 12 月 16 日下午 2:15:11（进程 WMTN200411-0） : 运行工作进程时出错（Jython 解释器状态未初始化。您需要调用 PySystemState.initialize 或 PythonInterpreter.initialize。）
I am wondering if anyone has tried to integrate Grinder with RAD 7.5.
Issue: When trying to run my recorded jpython script from the Grinder TCP Proxy I get the following error in RAD 7.5
Details:
- RAD 7.5
- Grinder: 3.6
I tried creating a basic script and the same thing happened in RAD. I was wondering if anyone had this happen? Or if you had any luck setting up Grinder within RAD 7.5.
Error Message:
Exception in thread "main" java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment
at sun.instrument.InstrumentationImpl.isRetransformClassesSupported0(Native Method)
at sun.instrument.InstrumentationImpl.isRetransformClassesSupported(InstrumentationImpl.java:112)
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 net.grinder.engine.process.dcr.DCRContextImplementation.create(DCRContextImplementation.java:74)
at net.grinder.engine.process.GrinderProcess.run(GrinderProcess.java:309)
at net.grinder.engine.process.WorkerProcessEntryPoint.run(WorkerProcessEntryPoint.java:86)
at net.grinder.engine.process.WorkerProcessEntryPoint.main(WorkerProcessEntryPoint.java:58)
16/12/11 2:15:11 PM (process WMTN200411-0):
Error running worker process (Jython interpreter state not initialized. You need to call PySystemState.initialize or PythonInterpreter.initialize.)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在对此进行了更多研究之后，这似乎是与 Grinder 和 RAD java 编译器相关的问题。通过 Grinder 代理在外部运行相同的脚本，我能够使其运行。
我希望本周有一些时间使用grinder源调试这个问题。
After doing some more research into this , it seems to be a problem related to Grinder and the RAD java compiler. Running the same scripts external though the Grinder agent I was able to make it run.
I hope to have some time this week and debug the issue using the grinder source.