It's all about the answers!

Ask a question

Registering sample adapter RQMAutomationSample results in "500: Internal Server Error"

Mikhail Pomeranets (1325) | asked Sep 04 '15, 12:04 p.m.
 I am attempting to run a sample RQM automation adapter, which is referenced from the "offical" RQM documentation. Here is the link to the sample:

Running the sample adapter results in "500: Internal Server Error". 
I am able to run the Command-Line adapter (which comes with RQM) successfully on the same machine. 
Can anybody help, please? What might be the difference between the command-line and the sample, and why is the "official" sample creating an "internal server error"? 

I cannot sniff the difference with wireshark since the connection is over https.

The adapter seems to login successfully; it is just the registration that fails.

Here is the entire log produced by the sample:

Sep 4, 2015 11:53:46 AM org.eclipse.lyo.client.oslc.samples.automation.RQMAutomationSample configureAdapter
INFO: Loading cached adapter properties from file:/C:/Users/mvpomera/dev/RQM/SampleAdapter/org.eclipse.lyo.client/
Sep 4, 2015 11:53:47 AM org.eclipse.lyo.client.oslc.samples.automation.RQMAutomationSample configureAdapter
INFO: Logging into service provider at
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See for further details.
Sep 4, 2015 11:53:48 AM org.eclipse.lyo.client.oslc.samples.automation.RQMAutomationSample configureAdapter
INFO: Registering with service provider
Exception in thread "main" org.eclipse.lyo.client.oslc.samples.automation.AutomationException: Failed to register the adapter at 500: Internal Server Error
at org.eclipse.lyo.client.oslc.samples.automation.AutomationAdapter.register(
at org.eclipse.lyo.client.oslc.samples.automation.RQMAutomationSample.configureAdapter(
at org.eclipse.lyo.client.oslc.samples.automation.RQMAutomationSample.begin(
at org.eclipse.lyo.client.oslc.samples.automation.RQMAutomationSample.main(

Paul Slauenwhite commented Sep 08 '15, 10:34 a.m.

Please check the RQM logs for the source of the 500 error response.

Mikhail Pomeranets commented Sep 08 '15, 10:43 a.m.

 Sure, I may have to do that eventually, but it is not easy to arrange in the corporate environment: it is a production server and I would have to request all sorts of permissions from IT to check the logs on that server. I was just hoping that somebody had seen the same problem before (I am playing with the unmodified "official" sample, after all) and would be able to point me in the right direction without the server logs...

Mikhail Pomeranets commented Sep 09 '15, 8:46 a.m.

 Paul, installing a trial version is a good idea; I did not know it was available. I have already requested the permissions for access to the production server's logs, though, so I hope I will get the answers shortly.

2 answers

permanent link
Paul Slauenwhite (8.4k12) | answered Sep 09 '15, 7:29 a.m.
It's difficult to determine the issue without the cause of the 500 error response. 

I would suggest installing a trial version of CLM (express setup is very simple) on your personal computer for testing instead of using a production environment.

permanent link
Massimo Caprinali (1636) | answered Feb 21 '17, 5:51 p.m.

I had the same problem. I resolved adding the Custom Test Automation Script Types in RQM Project Area with id org.eclipse.lyo.clients.oslc.sample

Your answer

Register or to post 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.