RQMUrlUtility.jar error
CLM 6.0.2
Running the command:
java -jar /var/chef/cache/RQM/RQMUrlUtility.jar -command GET -user liora -password liora -filepath /var/chef/cache/plan.xml -url https://<clm server>:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE+Banking+%28Quality+Management%29/testplan/urn:com.ibm.rqm:testplan:1
Output:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <<<<<----- [ RQMUrlUtility ] ---->>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Default cookie policy RFC_2109 is used. RQMUrlUtility: Connected to https://<clm server>:9443 using project "JKE+Banking+%28Quality+Management%29" Attempting to create SSL_TLS context Exception in thread "main" java.lang.InternalError at sun.security.ec.SunEC.initialize(Native Method) at sun.security.ec.SunEC.access$000(SunEC.java:49) at sun.security.ec.SunEC$1.run(SunEC.java:61) at sun.security.ec.SunEC$1.run(SunEC.java:58) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ec.SunEC.<clinit>(SunEC.java:58) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at java.lang.Class.newInstance(Class.java:383) at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221) at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206) at java.security.AccessController.doPrivileged(Native Method) at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206) at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187) at sun.security.jca.ProviderList.getProvider(ProviderList.java:233) at sun.security.jca.ProviderList.getService(ProviderList.java:331) at sun.security.jca.GetInstance.getInstance(GetInstance.java:157) at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) at com.ibm.rqm.url.client.SSLContextUtil.createSSLContext(Unknown Source) at com.ibm.rqm.url.client.SSLContextUtil.createSSLContext(Unknown Source) at com.ibm.rqm.url.client.TrustingSSLProtocolSocketFactory.<init>(Unknown Source) at com.ibm.rqm.url.client.TrustingSSLProtocolSocketFactory.getInstance(Unknown Source) at com.ibm.rqm.url.client.RQMUrlUtlyJRSHttpsClient.registerTrustingSSL(Unknown Source) at com.ibm.rqm.url.client.RQMUrlUtlyLogin.login(Unknown Source)
at com.ibm.rqm.url.UrlUtility.main(Unknown Source) |
Accepted answer
It looks suspiciously the same as this OpenJDK 1.8 bug opened against Red Hat.
https://bugzilla.redhat.com/show_bug.cgi?id=1332867 https://bugzilla.redhat.com/show_bug.cgi?id=1332456 If you have any IBM products installed on the same machine, try with the bundled IBM Java (by specifying the absolute path to the java executable). Liora Milbaum selected this answer as the correct answer
Comments
Liora Milbaum
commented Sep 15 '16, 6:12 a.m.
Donald, thanks for the input. Switching to a different java version was the trick. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Hi Liora,