It's all about the answers!

Ask a question

RQMCopyUtility - what is wrong with this command line


Karen Steele (1.1k1130105) | asked Jul 20 '20, 8:04 a.m.
We realize this is an unsupported utility, I have used it many times in earlier versions of the tools but this one just refuses to accept the command line.

We are on 6.0.4 - the copy utility is 6.0.4 ... I have full permission to the server against which I'm trying to do the copy to but it fails with a very short log with a ssl handshake error

Any help is appreciated, we have to be able to get this data off one server and moved to another.

This is the command line we are running :


Running the above returned this in the log file

17 Jul 2020 08:25:14,319-0300 [main]  INFO com.ibm.rqm.ct.CopyUtil: Attempting to create SSL_TLS context
17 Jul 2020 08:25:14,589-0300 [main] ERROR com.ibm.rqm.ct.CopyUtil: SSL_TLS SSLContext not available
17 Jul 2020 08:25:14,589-0300 [main]  INFO com.ibm.rqm.ct.CopyUtil: Unable to create SSL_TLS context, trying SSLv3
17 Jul 2020 08:25:18,015-0300 [main] ERROR com.ibm.rqm.ct.CopyUtil: Error logging in to source: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
    at sun.security.ssl.AppOutputStream.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    at java.io.BufferedOutputStream.flush(Unknown Source)
    at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975)
    at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
    at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
    at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
    at com.ibm.rqm.ct.client.internal.JFSHttpsClient.login(JFSHttpsClient.java:98)
    at com.ibm.rqm.ct.Application.run(CopyUtil.java:152)
    at com.ibm.rqm.ct.CopyUtil.main(CopyUtil.java:43)
17 Jul 2020 08:25:18,015-0300 [main]  INFO com.ibm.rqm.ct.CopyUtil: Disconnecting from the source IBM Rational Quality Manager server.
17 Jul 2020 08:25:18,115-0300 [main] ERROR com.ibm.rqm.ct.CopyUtil: Log out error (response code) - 0
Status Code:
Response Body:
17 Jul 2020 08:25:18,115-0300 [main]  INFO com.ibm.rqm.ct.CopyUtil: RQM Copy Utility failed to disconnect from the source server!
17 Jul 2020 08:25:18,115-0300 [main]  INFO com.ibm.rqm.ct.CopyUtil: Disconnecting from the destination IBM Rational Quality Manager server.
17 Jul 2020 08:25:18,247-0300 [main] ERROR com.ibm.rqm.ct.CopyUtil: Log out error (response code) - 0
Status Code:
Response Body:
17 Jul 2020 08:25:18,247-0300 [main]  INFO com.ibm.rqm.ct.CopyUtil: RQM Copy Utility failed to disconnect from the destination server!

One answer



permanent link
Fabian Lomeli (713) | answered Jul 20 '20, 3:00 p.m.
Hi Karen,
This might be related to configuration in your environment.  The code should be using a sequence of:
SSL_TLS
SSLv3
TLS
SSL

Trying first then second and so on...

You might want to enforce to use a particular algorithm through the "com.ibm.team.repository.transport.client.protocol".

If you want to provide it, make sure the -Dcom.ibm.team.repository.transport.client.protocol="<your-protocol>" argument.

There is a reference in the readme about how it should be used when TLS 1.2 is configured.
...
* Attempting to start the command line adapter when TLS 1.2 is used and the -Dcom.ibm.team.repository.transport.client.protocol="TLSv1.2" argument is not set will result in a connection handshake failure. If using TLS 1.2, ensure the -Dcom.ibm.team.repository.transport.client.protocol="TLSv1.2" argument is included in order to ensure a successful connection.

Your answer


Register or to post your answer.