It's all about the answers!

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

×42,883
×6,033
×4,320
×343

question asked: Jun 19 '14, 9:42 p.m.
question was seen: 6,547 times
last updated: Jul 21 '14, 6:24 p.m.

Related questions

Has anyone seen this crash of data collection CCM WI job ?

0
long TRUONG (365●4●123●147) | asked Jun 19 '14, 9:42 p.m.
retagged Jun 20 '14, 9:41 a.m. by Laura W. Hinson (161●2●6)
 Our CCM WI data collection job crashed yesterday after 7 days and 22 hrs (slow, you say. Yes! that was a subject on an existing PMR just reopened) with below warnings and ERROR messages, anybody any ideas before this goes for another PMR. We are on RTC 4.0.3 without any usage of Source Control and Build up to now.

Status Data Collection Job    Start Time:              End Time            Time Taken
Failed Work Items 10 Jun 2014 18:05 18 Jun 2014 16:40 7 days, 22 hours

umpteen of warnings: "2014-06-18 16:11:22,869 [http-bio-443-exec-9575 @@ 16:11 gyagopa /ccm/service/com.ibm.team.workitem.common.internal.rest.IQueryRestService/histogram]  WARN bm.team.repository.common.transport.ServerHttpUtil  - CRJAZ2199W Internal error occurred while trying to to send exception information to client - response in committed state."

Followed by ERRORs:
Line 809: 2014-06-18 16:17:41,586 [http-bio-443-exec-9576 @@ 16:12 ghjgibs /ccm/service/com.ibm.team.repository.common.internal.IFeedService/ccm/service/com.ibm.team.repository.common.internal.IFeedService] ERROR .team.repository.service.feed.internal.FeedService  - CRJAZ0838I CRJAZ0843I TeamRepositoryException in FeedService GET. - Exception message: "!QueryFetchRows.errorInNExt!
Line 3902: 2014-06-18 16:32:45,829 [http-bio-443-exec-9477 @@ 16:27 ghjgibs /ccm/service/com.ibm.team.repository.common.internal.IFeedService/ccm/service/com.ibm.team.repository.common.internal.IFeedService] ERROR .team.repository.service.feed.internal.FeedService  - CRJAZ0838I CRJAZ0843I TeamRepositoryException in FeedService GET. - Exception message: "!QueryFetchRows.errorInNExt!

Line 5548: 2014-06-18 16:39:57,576 [http-bio-443-exec-9651 @@ 16:39 svc_rtc /ccm/rpt/repository/workitem] ERROR com.ibm.team.reports                                - _GwpLwPP6EeONOPjsqyIwBw
Line 5549: com.ibm.team.repository.common.QueryExpiredException: _GwpLwPP6EeONOPjsqyIwBw

Line 5610: 2014-06-18 16:40:01,990 [http-bio-443-exec-9458 @@ 16:40 svc_rtc /ccm/rpt/repository/workitem] ERROR com.ibm.team.reports                                - _GwpLwPP6EeONOPjsqyIwBw
Line 5611: com.ibm.team.repository.common.QueryExpiredException: _GwpLwPP6EeONOPjsqyIwBw

Line 5672: 2014-06-18 16:40:04,557 [http-bio-443-exec-9700 @@ 16:40 svc_rtc /ccm/rpt/repository/workitem] ERROR com.ibm.team.reports                                - _GwpLwPP6EeONOPjsqyIwBw
Line 5673: com.ibm.team.repository.common.QueryExpiredException: _GwpLwPP6EeONOPjsqyIwBw

Line 5734: 2014-06-18 16:40:04,940 [http-bio-443-exec-9623 @@ 16:40 svc_rtc /ccm/rpt/repository/workitem] ERROR com.ibm.team.reports                                - _GwpLwPP6EeONOPjsqyIwBw
Line 5735: com.ibm.team.repository.common.QueryExpiredException: _GwpLwPP6EeONOPjsqyIwBw
   
        Line 5796: ...
...

Have googled for com.ibm.team.repository.common.QueryExpiredException and found:
https://jazz.net/library/article/920
but this does not fit in any circumstances described in the article.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Stephanie Bagot (2.1k●1●5●13) | answered Jul 15 '14, 2:07 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I would recommend pursuing a PMR on this as well as the slow ETL run time.
Comments
long TRUONG commented Jul 15 '14, 4:39 p.m.

 Thx Stephanie. We do have a long running [PMR 53034,49R,000], which is still open, for the slowness of the WI collection job. SWAT will advise us if we should submit a separate PMR for this failed WI job (if this looks familiar, you have seen it on another post you answered https://jazz.net/forum/questions/157598/is-there-a-way-to-run-the-wi-data-collection-job-independent-of-ie-offline-to-the-jts).Since that failed job, we have yet to have a successful WI job, due to server host or app server crashes & scheduled maintenance, which were followed by a WI job which ran for 9 days 15 hrs then disappeared (no report of success or failure) with the last log entry "2014-07-09 14:37:13,141 [ccm: AsynchronousTaskRunner-0 @@ 19:34] DEBUG e.workitem.internal.WorkItemsRemoteSnapshotService  - ETL: Finished Build WorkItemHisComplexCustomAttr at 7/9/14 2:37 PM. The build was unsuccessful"

long TRUONG commented Jul 21 '14, 6:24 p.m.

We are now pursuing another [PMR 19720,49R,000], as we now have another long running ETL (WI job) crashes after 10 days running, without any trace in the status report.

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.