It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,880
×7,474
×4,715

question asked: Nov 18 '13, 11:04 p.m.
question was seen: 5,836 times
last updated: Nov 20 '13, 1:41 a.m.

Related questions

"Work Items " Data Collection Jobs Failing - RTC 4.0

0
vishnudharan manivannan (118●37●42) | asked Nov 18 '13, 11:04 p.m.

Hello All,

'I recently noticed that the data collection jobs for the work items in CCM application is alone failing.

Note : SCM , Build and Common are succeeding.

 

 I checked the ETL logs  from the location Opt/IBM/JazzTeamServer/server/logs and here is that information from ccm-etl.log

2013-11-15 11:46:51,675 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: ***Finished Build WorkItemState at 11/15/13 11:46 AM. The build was successful***
2013-11-15 11:46:51,675 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: ***Started Build WorkItemType at 11/15/13 11:46 AM***
2013-11-15 11:46:51,922 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Records Selected: 2076
2013-11-15 11:46:51,922 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Records Inserted: 35
2013-11-15 11:46:51,922 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Records Updated: 2041
2013-11-15 11:46:51,922 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Inserting: Less than 1ms
2013-11-15 11:46:51,923 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Updating: Less than 1ms
2013-11-15 11:46:51,923 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Looking Up: Less than 1ms
2013-11-15 11:46:51,923 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Fetching Data: 17 seconds
2013-11-15 11:46:51,923 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Running: Less than 1ms
2013-11-15 11:46:51,923 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: ***Finished Build WorkItemType at 11/15/13 11:46 AM. The build was successful***
2013-11-15 11:46:51,923 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: ***Started Build WorkItemResolution at 11/15/13 11:46 AM***
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Records Selected: 4540
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Records Inserted: 52
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Records Updated: 4488
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Inserting: Less than 1ms
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Updating: 2 seconds
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Looking Up: 3 seconds
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Fetching Data: 17 seconds
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Time Running: Less than 1ms
2013-11-15 11:46:52,226 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: ***Finished Build WorkItemResolution at 11/15/13 11:46 AM. The build was successful***
2013-11-15 11:46:52,227 [      http-bio-9443-exec-88232] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: ***Started Build WorkItemEnumeration at 11/15/13 11:46 AM***
2013-11-15 11:47:16,305 [      http-bio-9443-exec-88232] ERROR e.workitem.internal.WorkItemsRemoteSnapshotService  - com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1417E: The HTTP status '500' and the message is 'Internal Server Error'.
java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1417E: The HTTP status '500' and the message is 'Internal Server Error

Kindly let me know what needs to be done to correct this.

Thanks in advance!

Varun

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
N Z (362●1●21●27) | answered Nov 19 '13, 12:22 a.m.
 Of no help to you, but we are also having jobs failing (4.0.3). We have a PMR open of this, currently, it's still not resolved.
0
permanent link
Don Yang (7.7k●21●114●139) | answered Nov 19 '13, 1:53 a.m.
Hi, Varun

There are some basic check points for any failed ETL jobs. In your case, since only work item job failed, the quick check point is to go to ccm/admin > reports > data collection jobs and see if you have set the correct user and password for work item job, re-enter the correct user and password(you can test with the user and password by login with it to the admin page and you should be able to login).

If this does not help , which means user and password are correct, the best option is to open a PMR because all other jobs work and it means etl user and permission and license should be right configured. From the error CRRRE1417E: The HTTP status '500' and the message is 'Internal Server Error' and the previous trace, it is likely that some workitem(s) is(are) corrupted. Open a PMR and the support would suggest to turn on debug mode for etl jobs and collect further info from etl and etl driver logs. From the logs, they would try to find out which workitem(s) could contribute to the failure and then you can look into that specific workitem(s) and find out what is wrong and so on.

Don
Comments
vishnudharan manivannan commented Nov 20 '13, 1:41 a.m.

Thanks Don for your response. As mentioned the user credentials for the ETL user are configured correctly and they are working as expected. Which means some workitems might be corrupted (not sure thought). I will open a PMR for the same.

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.