maurizio.cimadamore at oracle.com
Wed May 5 09:40:12 UTC 2021
This is a "known" limitation. I note that this is not mentioned in the
README, but should.
Basically we can only debug the _first_ test action (e.g. @compile or
@run). If a test contains multiple actions, the debugger session
attaches to the first, and then we get a failure (like you did). For
now, the only workaround is to manually "comment" out the tags that are
not required, so that only one test action remains.
I do not have enough knowledge of IntelliJ internals (e.g. debugging
API) to understand how to redirect the debugger from one process to
another; if others do, we'd be more than happy to fix this long standing
On 05/05/2021 01:22, Bradford Wetmore wrote:
> Following the instructions on README.md in the source and submitting
> the report here.
> I have two very similar tests: one is debuggable, the other returns with:
> ERROR: transport error 202: connect failed: Connection refused
> ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
> initialized [open/src/jdk.jdwp.agent/share/native/libjdwp/debugInit.c:734]
> It can "run" the test just fine, just not "debug" it.
> After a lot of trial/error, I found the plugin doesn't like @compile,
> but is ok with @build.
> diff --git a/test/jdk/javax/net/ssl/ALPN/SSLEngineAlpnTest.java
> index adeb1a7dfc4..cc221d5b582 100644
> --- a/test/jdk/javax/net/ssl/ALPN/SSLEngineAlpnTest.java
> +++ b/test/jdk/javax/net/ssl/ALPN/SSLEngineAlpnTest.java
> @@ -28,7 +28,7 @@
> * @test
> * @bug 8051498 8145849 8170282
> * @summary JEP 244: TLS Application-Layer Protocol Negotiation Extension
> - * @compile MyX509ExtendedKeyManager.java
> + * @build MyX509ExtendedKeyManager
> * @run main/othervm SSLEngineAlpnTest h2 UNUSED h2 h2
> * @run main/othervm SSLEngineAlpnTest h2 UNUSED h2,http/1.1 h2
> Let me know if you have any questions.
More information about the ide-support-dev