It's all about the answers!

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

×42,882
×12,008

question asked: Mar 07 '14, 2:05 p.m.
question was seen: 4,832 times
last updated: Mar 12 '14, 6:13 a.m.

Related questions

RTC 4.0.6 - ccm log - why am I seeing a "premature end of file"?

0
Donald Poulin (224●9●119●107) | asked Mar 07 '14, 2:05 p.m.
I noticed these errors in the ccm log of the RTC 4.0.5 server. I just completed and upgrade to  RTC 4.0.6 and am still seeing the same errors. The server host is windows 7 with Tomcat and a Derby database. Here are the errors:

2014-03-07 08:48:52,998 [ccm: AsynchronousTaskRunner-1 @@ 08:48] ERROR com.ibm.team.build                                  - CRRTC3011E: The contributions to a build, _cphyko88EeOzcan2tllhxA, could not be pruned by the pruning extension, com.ibm.team.enterprise.packaging.service.buildResultDeleteParticipant, because an error occurred.
com.ibm.team.repository.common.TeamRepositoryException: Premature end of file.
    at com.ibm.team.enterprise.internal.packaging.common.jfs.PackageJFSParser.toJFSResource(PackageJFSParser.java:43)
    at com.ibm.team.enterprise.internal.packaging.service.jfs.PackageJFSService.markedForDeletion(PackageJFSService.java:140)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at com.sun.proxy.$Proxy1104.markedForDeletion(Unknown Source)
    at com.ibm.team.enterprise.packaging.service.MarkPackageDeletedParticipant.doDelete(MarkPackageDeletedParticipant.java:42)
    at com.ibm.team.enterprise.packaging.service.MarkPackageDeletedParticipant.delete(MarkPackageDeletedParticipant.java:31)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at com.sun.proxy.$Proxy1317.delete(Unknown Source)


2014-03-07 08:48:53,061 [ccm: AsynchronousTaskRunner-1 @@ 08:48] ERROR com.ibm.team.build                                  - CRRTC3011E: The contributions to a build, _AIj3Ao89EeOzcan2tllhxA, could not be pruned by the pruning extension, com.ibm.team.enterprise.packaging.service.buildResultDeleteParticipant, because an error occurred.
com.ibm.team.repository.common.TeamRepositoryException: Premature end of file.
    at com.ibm.team.enterprise.internal.packaging.common.jfs.PackageJFSParser.toJFSResource(PackageJFSParser.java:43)
    at com.ibm.team.enterprise.internal.packaging.service.jfs.PackageJFSService.markedForDeletion(PackageJFSService.java:140)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at com.sun.proxy.$Proxy1104.markedForDeletion(Unknown Source)
    at com.ibm.team.enterprise.packaging.service.MarkPackageDeletedParticipant.doDelete(MarkPackageDeletedParticipant.java:42)
    at com.ibm.team.enterprise.packaging.service.MarkPackageDeletedParticipant.delete(MarkPackageDeletedParticipant.java:31)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at com.sun.proxy.$Proxy1317.delete(Unknown Source)
    at com.ibm.team.build.internal.service.delete.BuildResultContributionsPruner$2$1.run(BuildResultContributionsPruner.java:253)
    at com.ibm.team.build.internal.service.delete.BuildResultContributionsPruner$2$1.run(BuildResultContributionsPruner.java:1)
    at com.ibm.team.repository.service.internal.PrimitiveTransactionService$3.run(PrimitiveTransactionService.java:163)
    at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$Transaction.run(RepositoryDatabase.java:496)
    at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:320)
    at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:448)
    at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
    at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
    at com.sun.proxy.$Proxy631.withCurrentConnection(Unknown Source)
    at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:316)
    at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runInTransaction(RepositoryDatabase.java:271)
    at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runInTransaction(PrimitiveTransactionService.java:96)
    at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runInTransaction(PrimitiveTransactionService.java:91)
    at sun.reflect.GeneratedMethodAccessor329.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Hung Lam (291●19●15) | answered Mar 09 '14, 3:09 p.m.
JAZZ DEVELOPER
 Is it possible the package has been manually deleted but the build result still exists?
0
permanent link
Hung Lam (291●19●15) | answered Mar 10 '14, 4:06 p.m.
JAZZ DEVELOPER
 Do you see any real problems with your packaging or deployment builds, or you just notice these in the ccm.log. Also is it possible to get the complete ccm.log. 
Comments
Donald Poulin commented Mar 12 '14, 6:13 a.m.

I did have a mismatch between package build results and the package on omvs. I have now cleaned things up and will check to see if the errors continue. I had not been working with packages for a while but happened to notice the errors in the ccm log.

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.