ERROR: com.ibm.team.filesystem.client code=0

Code 0 generally means the error was unexpected and does not fit into any
known class of problems that can be handled. (Otherwise a more specific
code enumeration should have been set).

The 'children' listing isn't refering to child processes. It is just the
structure of the status as
statuses often get wrapped by other statuses as they are passed around
until it is logged.

Just from your error message it isn't clear as to what caused it. Is there
a stack trace associated with this error in your log? Can you tell us more
about what you are trying to do when this error occurs?


On Thu, 18 Jun 2009 20:37:55 -0400, manonfire
<manonfire16> wrote:

Hi,

Can anybody from the RTC point what code 0 error stands for

com.ibm.team.filesystem.client.FileSystemClientException: Status
ERROR: com.ibm.team.filesystem.client code=0 Errors occured while
shutting down null children=

Can the rtc team enlighten as to what causes the error and what child
processes are being killed for client in filesystem to get ready for
a build.

Mafaz

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

As Andrew points out, the children are other status messages - which are essentially multiple 'cause' fields (if you take java's Throwable class as an example). Dig into their content, and you'll likely find out why the exception was thrown.

e

This looks similar to
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/60038

Michael

Andrew Hoo wrote:

Code 0 generally means the error was unexpected and does not fit into
any known class of problems that can be handled. (Otherwise a more
specific code enumeration should have been set).

The 'children' listing isn't refering to child processes. It is just the
structure of the status as
statuses often get wrapped by other statuses as they are passed around
until it is logged.

Just from your error message it isn't clear as to what caused it. Is
there a stack trace associated with this error in your log? Can you tell
us more about what you are trying to do when this error occurs?


On Thu, 18 Jun 2009 20:37:55 -0400, manonfire
manonfire16@gmail-dot-com.no-spam.invalid> wrote:

Hi,

Can anybody from the RTC point what code 0 error stands for

com.ibm.team.filesystem.client.FileSystemClientException: Status
ERROR: com.ibm.team.filesystem.client code=0 Errors occured while
shutting down null children=

Can the rtc team enlighten as to what causes the error and what child
processes are being killed for client in filesystem to get ready for
a build.

Mafaz

Thankyou for helping out guys.
Michael, that links help some what but issues doesn't seem to have been resolved.thanks though as it gives more insight.
EChughes, How do u propose i dig deep into these causes as I can't access the internal application code or api's for RTC?Can you tell where to look for them or what startegy you adopted?Thanks.
Andrew, here's some more information.It was the start of the build when RTC threw out this error.Why do statuses have to be wrapped, shouldn't be status error be thrown out as soon as it happens.Btw, i had enough disk space so no issues with that, if that comes up as a thought.
Should build occur?
Yes: Always build a user initiated request.
Invoking pre-build participant "com.ibm.team.build.jazzscm"
Accepting changes into workspace
Deleting fetch destination ... before fetching ...
Fetching files to fetch destination .....
com.ibm.team.filesystem.client.FileSystemClientException: Status ERROR: com.ibm.team.filesystem.client code=0 Errors occured while shutting down null children=
at com.ibm.team.filesystem.client.internal.SharingManager.shutDown(SharingManager.java:299)
at com.ibm.team.filesystem.client.internal.SharingManager.conditionalShutDown(SharingManager.java:314)
at com.ibm.team.filesystem.client.FileSystemCore.shutDown(FileSystemCore.java:81)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:162)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:574)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:430)
at java.lang.Thread.run(Thread.java:810)

EChughes, How do u propose i dig deep into these causes as I can't access the internal application code or api's for RTC?Can you tell where to look for them or what startegy you adopted?Thanks.

I thought you encountered this during development. The usual way for developers to get that information is to set a breakpoint and dig into the problem.

If you aren't in a development environment, I can't make a useful suggestion. Sorry.

e

Restarting the build engine fixed the issue.I hopes this helps people with the same problem.Thanks for helping out.

Thanks manonfire. It saved my time.

Restarting the build engine fixed the issue.I hopes this helps people with the same problem.Thanks for helping out.