I have seen the the article with QM problem in this forum. I checked the user and the licenses. I also tried the job with my JazzAdmin account and full access lincenses. Also failed.
I get 2 different errors
https://jazz.zurich.com/rm/publish/resources/*?size=100&ownLinks=true&ptext=true&fields=ds%3AdataSource%2Fds%3Aartifact%2F%28location%2Fproject%2Fabout%7Ccollaboration%2F%28attributes%2FobjectType%2F%28customAttribute%2F%28%40itemId%7C%40isEnumeration%7C%40datatype%7C%40name%7C%40isMultiValued%7C%40valueTS%7C%40literalName%7C%40value%7C%40literalId%29%7C%40name%7C%40itemId%29%7Ccreator%2Falternative%7Cmodified%7Ccreated%29%7Ctraceability%2Flinks%2F%28ValidatedBy%2Frelation%7CImplementedBy%2Frelation%7CLink%2F%28content%2Fformat%7CisChildLink%7CisParentLink%7Crelation%7Ctitle%29%7CAffectedBy%2Frelation%7CTrackedBy%2Frelation%7CExternal%2F%28relation%7ClinkType%7Cidentifier%29%29%7CmoduleContext%2FcontextBinding%2Fabout%7Cabout%7Cformat%7Cidentifier%7Ctitle%7Cdeleted%7CprimaryText%29&modifiedsince=1899-12-31T00%3A00%3A00.000%2B0100
09/10/2015 10:41:32,134 [dcc_etl_RRC_ODS_RRCResourceGroup0_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.OAuthClientImpl from calling the function handleExecute.
at com.ibm.rational.datacollection.etl.authentication.OAuthETLHttpClient.send(OAuthETLHttpClient.java:191)
at com.ibm.rational.datacollection.etl.fetcher.DataFetcher.call(DataFetcher.java:241)
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:790)
Caused by: com.ibm.rational.datacollection.oauth.ConnectionException: java.net.SocketTimeoutException: Read timed out
at com.ibm.rational.datacollection.oauth.OAuthClientImpl.handleExecute(OAuthClientImpl.java:101)
at com.ibm.rational.datacollection.oauth.ConnectionClientImpl.execute(ConnectionClientImpl.java:219)
at com.ibm.rational.datacollection.etl.authentication.OAuthETLHttpClient.send(OAuthETLHttpClient.java:149)
and the second one
09/10/2015 10:41:32,276 [dcc_etl_RRC_ODS_RRCResourceGroup0_resource_0] ERROR CRRCD4301E The RRCRequirement_R : /publish/resources/*?size=100&ownLinks=true&ptext=true : /ds:dataSource/ds:artifact resource could not be retrieved.
java.util.concurrent.ExecutionException: 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.OAuthClientImpl from calling the function handleExecute.
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:233)
at java.util.concurrent.FutureTask.get(FutureTask.java:94)
at com.ibm.rational.datacollection.etl.tasks.ETLSubTask.call(ETLSubTask.java:164)
at com.ibm.rational.datacollection.etl.tasks.ETLSubTask.call(ETLSubTask.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:790)
for the first error, I would try to open the URL in the message in a web browser.
If you have a user configured to connect to the DNG datasource in DCC make sure to login with those credentials.
If you get errors there, check also the DNG log.
Best Regards,
Francesco Chiossi
Torsten Welk selected this answer as the correct 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.