JASPIC Standalone TCK and Webservices12, WebServices13 Full Profile Platform TCK failures with NPE #23412
Comments
|
Same stack on this previous error #23147 |
|
@smillidge any idea which change from #23147 helped resolve the previous error? Does your comment |
|
no I will investigate a bit to see if I can debug. Essentially I think the error is that it basically can't retrieve a WSDL. Last time the error was transport related this time, don't know yet. |
|
Most of the webservices12 and webservices13 testsuite failure see at CI run https://ci.eclipse.org/jakartaee-tck/job/9.1/job/eftl-jakartaeetck-run-910/30/testReport/ are related to ^ issue. |
gurunrao
changed the title
gurunrao
changed the title
|
@hs536 I'm a bit stuck for time on this one. Can you solve it? |
|
I have no idea why this error occurred in JDK11, but I'll take a look. |
|
Note that a warning was shown before the NPE: |
|
I'm trying to run jaspic tck in my local environment for debugging, but I can't see this error. |
|
The following additional lines to + ###############################################################################
+ # @client.cert.test.jdk.tls.client.protocols JDK 11 in TLSv1.3 does not support
+ # Post-Handshake Authentication, so TLSv1.2 must be used
+ # for client-cert authentication to work.
+ ###############################################################################
+ client.cert.test.jdk.tls.client.protocols=TLSv1.2refs) https://github.com/eclipse-ee4j/jakartaee-tck/pull/637/files |
|
Do we want to add that to the domain.xml for GlassFish? |
|
No, I think this option is only necessary to minimize the TCK fixes for JDK11. |
|
My guess is that the cause of this problem is CNFE when initializing webservice. java.lang.reflect.Constructor cons = svcClass.getConstructor
(new Class[]{java.net.URL.class,
javax.xml.namespace.QName.class});
try {
obj =
cons.newInstance(wsdlFile, desc.getServiceName()); ★★ CNFE
} catch (Exception e) {
/* ★★NPE is occurring ahead.I'm continuing to investigate why CNFE occurred. |
|
@lukasj has just updated Metro will that make a difference? |
|
Yes, in 3.0.0-b01 the |
|
@smillidge @lukasj |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JASPIC TCK Test run logs and details of failures can be seen here - results.txt.
Also glassfish server logs can be seen here - server.log.
Steps for reproducing issue by running JASPIC TCK, can be found with wiki - https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-Building-&-Running-Jakarta-EE-Standalone-TCKs
JASPIC TCK bundle can be downloaded from https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/staged-910/jakarta-authentication-tck-2.0.0.zip
Archive with logs and results can be found at https://ci.eclipse.org/jakartaee-tck/job/9.1/job/eftl-standalonetck-build-run-910/28/artifact/authentication-tck-results.tar.gz
Exception stack-trace is as follows:
The text was updated successfully, but these errors were encountered: