Unable to create SSL_TLS context, trying SSLv3 RQMUrlUtility: Cannot authenticate to server javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
I am trying to download artifact from RQM, when I try to execute below mentioned comand, I get " javax.net.ssl.SSLHandshakeException" error
java.exe -jar .\RQMUrlUtility.jar -command GET -user "myusername" -password Mypass -filepath d:\bulkTestCase.xml -url https://localhost:9443/qm/
Detailed error:
Unable to create SSL_TLS context, trying SSLv3 RQMUrlUtility: Cannot authenticate to server javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
Accepted answer
You don't mention if you're connecting to your own server or if it's a Saas instance.
Is it running on localhost as you indicated above or did you replace the URL when you posted?
Can you post what the actual URL is that you are using?
Comments
Hello Davyd,
First of all thank you for response.
Yes I did replaced URL while posting.I am not sure if i can post actual URL.
java.exe -jar RQMUrlUtility.jar -command GET -user "username" -password "Password" -filepath d:\bulkTestCase.xml -url https://de....companyname.net/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/projname/testsuitelog/urn:com.ibm.rqm:testsuitelog:285
Some thing like this.
OK I assumed that was the case - even this helps a lot.
- I assume projname is the actual name of one of your projects, and there are no spaces (it's URL Encoded?)
If your URL is valid, then it may be failing because it can't negotiate the SSL connection. Your server may be set up to only allow TLS1.2 - in that case try adding
-Dcom.ibm.team.repository.transport.client.protocol="TLSv1.2"
into your command line just after the jar file name
Hi Ketan,
You should try..
java -Dcom.ibm.team.repository.transport.client.protocol="TLSv1.2" -jar ...
Hello Bharath,
Thanks for response.
But if I do so I am getting below mentioned error :
Error: Could not find or load main class .ibm.team.repository.transport.client.protocol=TLSv1.2
Can you show us your exact command line, with the anonymised URL? That's a weird error to be getting and I just want to check your formatting
Also make sure you are using CMD and not Windows PowerShell
Hello Davyd,
Find below URL:
java -jar .\RQMUrlUtility.jar -Dcom.ibm.team.repository.transport.client.protocol="TLSv1.2" -command GET -user "username" -password password -filepath e://bulkTestCase.txt -url https://de....companyname.net/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/ProjectName/testsuite/urn:com.ibm.rqm:testsuite:12
can you also show the output? And can you confirm you are running this in the command window and NOT Windows Powershell
Hello Davyd and Bharath,
RQMUrlUtility is now working fine. Issue was with format.After rechecking with suggestion provided by both of you, Issue has been resolved
Your suggestions and answer helped me a lot.
Thank you!!
Hi Ketan,
For the benefit of us and others, could you please share what helped resolve the problem ? Thanks
showing 5 of 9
show 4 more comments
One other answer
Hi Ketan,
The URL seems incorrect in the command as compared to details in the below link:
If the error persists, you should also try using the same version of java in the command as RQM.
Let me know if it helps or if you need any assistance.
Regards,
Bharath
Comments
Hello Bharath,
thanks for your fast response. I have corrected URL, but problem still persist.
I have also checked and found that JAVA versions are same.
Please suggest if there is anything else that i can do.
Hello Ketan,
Are you using the same version of the RQMURLUtility as that of the RQM Server ?
If yes, you could try using the RQM Command Line utility(same version as RQM) to test connecting / logging in to RQM server and confirm it works.
Also,
a. Ensure the Project Area Alias is correct in the URL used to download the artifacts.
b. Access the URL provided in command in a browser to confirm it takes you to the artifact in RQM.
If the above doesn't work, try using fiddler or other network trace tools to find the issue.
Hope it helps!