Hi,
Thank you all for the pointers.
I was able to connect to the test by running:
./runtests --web tomee-plume -d
com/sun/ts/tests/appclient/deploy/ejblink/single/Client#testCMP11
I attached remotely first to port 5005 and then to 5003 (app client port).
This also works:
./runtests --web tomee-p
Hey Cesar
A few things get run during the tests, and they can be debugged by passing
the correct option(s) to the runtests script. You can get details if you do
runtests --help, but here's the options you want:
-de,--debug-embeddedEnable TCK embedded ejb debug options (port
5001)
-dh,
H i Cesar,
I don’t see the javatest.log?
Have you found the command line that starts the app client, including the debug
options? I don’t think “listen mode” was available when I was working on this,
I sure didn’t know about it!
The app client test harness is definitely involved, but I was wo
Hi David,
Thanks for the reply!
Responding in line:
Is the app client container starting?
Yes,
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!
I don't suspend at all, the following command j
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
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
