Quality Management job in DCC fails
We have recently installed the DCC module in our 5.0.2 environment but the only job that keeps failing is the "Quality Management" one. I've assigned the license "Data Collection Component - Internal" to the dcc user.
Any idea what's missing?
This is the 1st error in the job log:
Any idea what's missing?
This is the 1st error in the job log:
02/17/2015 22:35:57,207 [dcc_etl_RQM_ODS_RQMResourceGroup0_fetcher_0] ERROR Can not retrieve the resources after 10 retries.com.ibm.rational.datacollection.etl.authentication.AuthenticationException: CRRCD1500E An exception com.ibm.rational.datacollection.oauth.ConnectionException was caught in the class com.ibm.rational.datacollection.oauth.internal.jaf.OAuthConsumerClientHelper from calling the function performOAuthChallenge. at com.ibm.rational.datacollection.etl.authentication.DCCHttpClient.execute(DCCHttpClient.java:178) at com.ibm.rational.datacollection.etl.fetcher.DataFetcher.call(DataFetcher.java:249) at com.ibm.rational.datacollection.etl.fetcher.DataFetcher.call(DataFetcher.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:784)Caused by: com.ibm.rational.datacollection.oauth.ConnectionException: Forbidden at com.ibm.rational.datacollection.oauth.internal.jaf.OAuthConsumerClientHelper.performOAuthChallenge(OAuthConsumerClientHelper.java:228) at com.ibm.rational.datacollection.oauth.OAuthClientImpl.handleExecute(OAuthClientImpl.java:99) at com.ibm.rational.datacollection.oauth.ConnectionClientImpl.execute(ConnectionClientImpl.java:225) at com.ibm.rational.datacollection.etl.authentication.DCCHttpClient.execute(DCCHttpClient.java:136) ... 7 more
Accepted answer
Hi Jorge,
On the "Resource Group Configuration" page of DCC, what authentication type are you using for the Quality Management group? Is it "User Name and Password", or "OAuth-Jts"? Does the "Test Connection" work successfully? If you're using User Name and Password, make sure the user you've selected has a valid QM license. If you're using OAuth, the functional user associated with the consumer key must have a license.
On the "Resource Group Configuration" page of DCC, what authentication type are you using for the Quality Management group? Is it "User Name and Password", or "OAuth-Jts"? Does the "Test Connection" work successfully? If you're using User Name and Password, make sure the user you've selected has a valid QM license. If you're using OAuth, the functional user associated with the consumer key must have a license.
Comments
Thanks for the quick response.
I'm using "User Name and Password" and the problem was that the given user didn't had an RQM license (I was checking the dcc_user).
It's weird because the Test Connection worked successfully before.
Thanks once again!
The "Test Connection" unfortunately doesn't check that the user has the correct licenses. It only checks that the user name/password (or consumer key/secret) are correct. In the stack trace from the log, it says "ConnectionException: Forbidden" - that is usually a good clue that there is some kind of license problem. If there was a problem with the user name and password, you would probably get an error like "unauthorized" instead.