RQM Command Line Adapter can't connect
Hi,
I have a weird problem with RQM 3.0.1 and tying to run the command line adapter on Windows 7 (64b). In RQM Connector console, I don't see my machine either.
Basically, I run it and it seems to be happy but a few seconds after (probably 5, my sleep time), it says it failed to save configuration file and then continuously says the store config is out of date.
I've deleted the Config.ini and confirmed that it gets created properly, with the correct values (that I can tell) and I can then run just start.bat, but I get the same results.
Here's sample output. As you can tell, I start running with all arguments and then run start.bat again without any arguments, so the Config.ini file is there, even though it says it's not.
C:\RQM_Command_Line_Adapter>start.bat -repository https://rqm.q1labs.inc:9443/qm
-user rft -password *** -adapter win7ie9 -projectArea Security+Intelligence
+Products+%28Quality+Management%29 -adapterName win7ie9 -sleepTime 5
Launching Command Line Adapter...
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
Adapter is reconnecting. Using saved configuration information from Config.ini
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
Successfully created an HTTP client
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
The adapter is now connected
Failed to save configuration file for the command line adapter
Created Command Line Adapter
Stored configuration is out of sync. Adapter is re-registering.
Stored configuration is out of sync. Adapter is re-registering.
Stored configuration is out of sync. Adapter is re-registering.
C:\RQM_Command_Line_Adapter>start.bat
Launching Command Line Adapter...
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
Adapter is reconnecting. Using saved configuration information from Config.ini
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
Successfully created an HTTP client
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
The adapter is now connected
Failed to save configuration file for the command line adapter
Created Command Line Adapter
Stored configuration is out of sync. Adapter is re-registering.
Stored configuration is out of sync. Adapter is re-registering.
Terminate batch job (Y/N)? y
C:\RQM_Command_Line_Adapter>
I have a weird problem with RQM 3.0.1 and tying to run the command line adapter on Windows 7 (64b). In RQM Connector console, I don't see my machine either.
Basically, I run it and it seems to be happy but a few seconds after (probably 5, my sleep time), it says it failed to save configuration file and then continuously says the store config is out of date.
I've deleted the Config.ini and confirmed that it gets created properly, with the correct values (that I can tell) and I can then run just start.bat, but I get the same results.
Here's sample output. As you can tell, I start running with all arguments and then run start.bat again without any arguments, so the Config.ini file is there, even though it says it's not.
C:\RQM_Command_Line_Adapter>start.bat -repository https://rqm.q1labs.inc:9443/qm
-user rft -password *** -adapter win7ie9 -projectArea Security+Intelligence
+Products+%28Quality+Management%29 -adapterName win7ie9 -sleepTime 5
Launching Command Line Adapter...
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
Adapter is reconnecting. Using saved configuration information from Config.ini
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
Successfully created an HTTP client
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
The adapter is now connected
Failed to save configuration file for the command line adapter
Created Command Line Adapter
Stored configuration is out of sync. Adapter is re-registering.
Stored configuration is out of sync. Adapter is re-registering.
Stored configuration is out of sync. Adapter is re-registering.
C:\RQM_Command_Line_Adapter>start.bat
Launching Command Line Adapter...
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
Adapter is reconnecting. Using saved configuration information from Config.ini
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
Successfully created an HTTP client
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
The adapter is now connected
Failed to save configuration file for the command line adapter
Created Command Line Adapter
Stored configuration is out of sync. Adapter is re-registering.
Stored configuration is out of sync. Adapter is re-registering.
Terminate batch job (Y/N)? y
C:\RQM_Command_Line_Adapter>
4 answers
Hi @jsg,
If you're not already, try running the adapter from Command Prompt window with elevated privileges.
To do this, use the "Run as Administrator" context menu option to invoke Command Prompt, as shown below.
http://dl.dropbox.com/u/14088579/forum%20post%20screenshots/snap1962.jpg
Cheers,
Patrick
If you're not already, try running the adapter from Command Prompt window with elevated privileges.
To do this, use the "Run as Administrator" context menu option to invoke Command Prompt, as shown below.
Cheers,
Patrick
Not sure what was done to solve the problem, but I did these things
1- Changed the user's license to RQM Quality Professoinal
2- Enabled debug logs in command line adapter
3- Re-ran the start.bat
4- It all worked
5- Disabled debug logs
6- Re-ran the start.bat and all was still good.
Not sure if there's something that got reset by debug mode or if it has to do with the license change.
This is how to enable debug mode:
1. Go to the RQM Command Line Adapter directory
2. Open "log4j.properties" with a text editor
3. At the bottom, set the two following lines to DEBUG:
log4j.logger.com.ibm.rqm.adapter.library=DEBUG
log4j.logger.com.ibm.rqm.adapter.commandline=DEBUG
4. Save and close the file
5. Delete the log file "CommandLineAdapter.log"
6. Try connecting again
1- Changed the user's license to RQM Quality Professoinal
2- Enabled debug logs in command line adapter
3- Re-ran the start.bat
4- It all worked
5- Disabled debug logs
6- Re-ran the start.bat and all was still good.
Not sure if there's something that got reset by debug mode or if it has to do with the license change.
This is how to enable debug mode:
1. Go to the RQM Command Line Adapter directory
2. Open "log4j.properties" with a text editor
3. At the bottom, set the two following lines to DEBUG:
log4j.logger.com.ibm.rqm.adapter.library=DEBUG
log4j.logger.com.ibm.rqm.adapter.commandline=DEBUG
4. Save and close the file
5. Delete the log file "CommandLineAdapter.log"
6. Try connecting again
Hi ,
Use should have Rational Quality Manager - Quality Professional or Rational Quality Manager - Connector
Thanks,
Deepa
---------------------
RQM Development
Use should have Rational Quality Manager - Quality Professional or Rational Quality Manager - Connector
Thanks,
Deepa
---------------------
RQM Development
Not sure what was done to solve the problem, but I did these things
1- Changed the user's license to RQM Quality Professoinal
2- Enabled debug logs in command line adapter
3- Re-ran the start.bat
4- It all worked
5- Disabled debug logs
6- Re-ran the start.bat and all was still good.
Not sure if there's something that got reset by debug mode or if it has to do with the license change.
This is how to enable debug mode:
1. Go to the RQM Command Line Adapter directory
2. Open "log4j.properties" with a text editor
3. At the bottom, set the two following lines to DEBUG:
log4j.logger.com.ibm.rqm.adapter.library=DEBUG
log4j.logger.com.ibm.rqm.adapter.commandline=DEBUG
4. Save and close the file
5. Delete the log file "CommandLineAdapter.log"
6. Try connecting again