From the distant past, I recall it being tricky to debug the app client tests. Can you tell what is happening? Is the app client container starting? Does it suspend for the debugger attachment? If not, it probably runs to completion before you can attach-I definitely remember this happening to me! Does it suspend but not allow attachment? Is the test harness or appclient test harness (I don’t recall if these are separate) suspended waiting for attachment?
Hope this helps! David Jencks Sent from my iPhone > On Jan 28, 2019, at 2:31 PM, César Hernández Mendoza <[email protected]> > wrote: > > Hi, > > I created the following document to track my TCK related work. > https://docs.google.com/spreadsheets/d/1oYO0RN-rg4Z7TgSLJ2u4iK4hOFHOXA49ech2y0N3kVw/edit?usp=sharing > > As you can see I executed today the tests from the "appclient" category. > > One of the failing test is: > com/sun/ts/tests/appclient/deploy/ejblink/single/Client#testCMP11 > > The way I'm executing just that tests is with the following command: > ./runtests --web tomee-plume -c -sql active -da > com/sun/ts/tests/appclient/deploy/ejblink/single/Client#testCMP11 > > Notice that I'm adding: > -sql to enable (according to with runtests script code [1]) required > databases to be created. > -da to enable TCK appclient debug options (port 5003) > > Then on my IntelliJ, I opened Jakarta-tck project [3] and set up a remote > debug configuration for Listen to Remote JVM at port: 5003 > > Unfortunately, I'm not able to make this to work and degub the failing test. > > > [1] https://github.com/apache/tomee-tck/blob/master/runtests#L30 > [2] https://github.com/apache/tomee-tck/blob/master/runtests#L38 > [3] https://jenkins.eclipse.org/jakartaee-tck/ > > -- > Atentamente: > César Hernández Mendoza.
