November 30, 2017 at 9:44 pm #544288
v: macos high sierra 10.13.1 17B1003
v: myeclipse 2017 ci8
main debug:12345678910111213141516171819202122232425262728# JMH version: 1.19# VM version: JDK 1.8.0_112, VM 25.112-b16# VM invoker: /Applications/Genuitec/MyEclipse 2017 CI/MyEclipse 2017 CI.app/Contents/Profile/binary/com.sun.java.jdk8.macosx.x86_64_1.8.0.v112/jre/bin/java# VM options: -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:52221 -Xms512M -Dfile.encoding=UTF-8# Warmup: 20 iterations, 1 s each# Measurement: 20 iterations, 1 s each# Timeout: 10 min per iteration# Threads: 1 thread, will synchronize iterations# Benchmark mode: Throughput, ops/time# Benchmark: me.hao0.benchmark.JMHSample_01_HelloWorld.wellHelloThere# Run progress: 0.00% complete, ETA 00:00:40# Fork: 1 of 1ERROR: transport error 202: connect failed: Connection refusedERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]<forked VM failed with exit code 2><stdout last='20 lines'></stdout><stderr last='20 lines'>ERROR: transport error 202: connect failed: Connection refusedERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]</stderr># Run complete. Total time: 00:00:00Benchmark Mode Cnt Score Error Units
December 4, 2017 at 2:05 am #544438December 4, 2017 at 2:12 am #544439
- This topic was modified 1 year, 1 month ago by g_man1990.
Sorry that you are seeing this issue.
Can you please check if any of the suggestions discussed in these threads help?
If you are still seeing issues, then please share with us the exact steps you followed to debug the application to help us replicate the problem at our end.
Please note that we released 2017 CI 9 last week. If you haven’t yet updated, then please go to Help > Check for Updates and update to CI 9.
Apologies for inconvenience caused.
MyEclipse SupportDecember 5, 2017 at 2:13 am #544491
December 7, 2017 at 2:03 am #544642
- This reply was modified 1 year, 1 month ago by g_man1990.
It looks as though the JMH benchmarks are not easy to debug:
It appears that the benchmark code is trying to launch a process similar to the java debugger (presumably so that it can obtain the information it needs). If you place a breakpoint at the
new Runner(opt).run()line in the java program, you will be able to debug and step through the code until the benchmark tries to run that process. But this will conflict with the debug process already launched.
So, this isn’t a MyEclipse issue and you will have to seek assistance in other forums (like StackOverflow).
Sorry for the inconvenience.