Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Work items export data truncated when parent link column inc

We're trying to export work item information including parent/child
status. We created a query in the web client which allows the addition
of "Parent" as a data column.

Doing an Export function in the Eclipse client specifying that query and
csv format results in a file being created. But when we look at the
data in Excel, we see that the data is truncated part way through.
After some experimentation we realized that the csv file is always
exactly a multiple of 8K. Almost always the file size is 24K, but we've
also seen it be 8K.

This doesn't happen with the Parent column not part of the display results.

I see that each time the truncated data file is created there are two
errors in the server system log. Here are the first few lines of each
trace (full traces available)

Throwable
java.lang.IllegalStateException
at
org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:405)
at
com.ibm.team.workitem.service.internal.query.ResultSetSerializer.serializeItem(ResultSetSerializer.java:86)
at
com.ibm.team.gateway.service.internal.AbstractRestService.serializeItem(AbstractRestService.java:323)
at
com.ibm.team.gateway.service.internal.ItemRestService.doReadResponse(ItemRestService.java:191)
at
com.ibm.team.gateway.service.internal.ItemRestService.perform_GET(ItemRestService.java:105)
at
com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:81)

Location

com.ibm.team.foundation.common.util.FoundationLog.unexpectedError(FoundationLog.java:140)
ERROR - Query _efu64ERwEd6Aad2iW8wEcQ expired
Tuesday, May 19, 2009 7:28 AM
Query _efu64ERwEd6Aad2iW8wEcQ expired.

Throwable

com.ibm.team.repository.common.QueryExpiredException: Query
_efu64ERwEd6Aad2iW8wEcQ expired.
at
com.ibm.team.repository.service.internal.QueryService.doFetchPage(QueryService.java:559)
at
com.ibm.team.repository.service.internal.QueryService.fetchPage(QueryService.java:241)
at sun.reflect.GeneratedMethodAccessor245.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)

Location
com.ibm.team.foundation.common.util.FoundationLog.unexpectedError(FoundationLog.java:140)

The server is V1.0.1.

Thanks!

0 votes



2 answers

Permanent link
We're trying to export work item information including parent/child
status. We created a query in the web client which allows the addition
of "Parent" as a data column.

Doing an Export function in the Eclipse client specifying that query and
csv format results in a file being created. But when we look at the
data in Excel, we see that the data is truncated part way through. After
some experimentation we realized that the csv file is always exactly a
multiple of 8K. Almost always the file size is 24K, but we've also seen
it be 8K.

This doesn't happen with the Parent column not part of the display
results.

You are running into
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/62878

I would recommend to upgrade from 1.0.1 to 1.0.1.1 where the problem is
fixed.

--
Regards,
Patrick
Jazz Work Item Team

0 votes


Permanent link
Patrick Streule wrote:
We're trying to export work item information including parent/child
status. We created a query in the web client which allows the
addition of "Parent" as a data column.

Doing an Export function in the Eclipse client specifying that query
and csv format results in a file being created. But when we look at
the data in Excel, we see that the data is truncated part way through.
After some experimentation we realized that the csv file is always
exactly a multiple of 8K. Almost always the file size is 24K, but
we've also seen it be 8K.

This doesn't happen with the Parent column not part of the display
results.

You are running into
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/62878


I would recommend to upgrade from 1.0.1 to 1.0.1.1 where the problem is
fixed.


Thanks, Patrick. We were wondering if that was the issue, but we hadn't
seen any mention of this truncation problem before.

We'll upgrade our server to 1.0.1.1.

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: May 19 '09, 3:42 p.m.

Question was seen: 5,104 times

Last updated: May 19 '09, 3:42 p.m.

Confirmation Cancel Confirm