Process leaked file descriptors some times with Clearcase plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Process leaked file descriptors some times with Clearcase plugin

Erik Ramfelt
Im having some strange problems with my CC SCM plugin. Sometimes when
a build starts and have been going for 5 minute I dont see any output
at all in the console. All I see is the the page (with text
surrounding the console output) and the circle ticking.

Ive checked the log and found the "Process leaked file descriptors"
error in the log. What can I do as a SCM developer to fix this? It
doesnt happen for all builds only for some of them.

Should I use the workaround (as described in the wiki) when starting
the command line?


As Ive got no access to the CC server so I can install a trigger I
have to rely on polling. But Ive noticed that the command for
retrieving the repository history will stall if there is another
instance of the command running. Is there anything I should do in the
SCM to only limit one polling at a time?

(So close but yet so far away)
//Erik

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Process leaked file descriptors some times with Clearcase plugin

Kohsuke Kawaguchi
Administrator
Erik Ramfelt wrote:
> Im having some strange problems with my CC SCM plugin. Sometimes when
> a build starts and have been going for 5 minute I dont see any output
> at all in the console. All I see is the the page (with text
> surrounding the console output) and the circle ticking.
>
> Ive checked the log and found the "Process leaked file descriptors"
> error in the log. What can I do as a SCM developer to fix this? It
> doesnt happen for all builds only for some of them.

I don't know much about how clearcase works, but this problem can only
happen if 'cleartool' launches nested processes that run longer than
'cleartool' itself. That seems highly unusual for a SCM tool. Is this
the case with clearcase? If so, what is that long-running process that
it is running?


> Should I use the workaround (as described in the wiki) when starting
> the command line?

I don't think it's practical for a plugin to do that. If clearcase
indeed does fork a process into background with descriptor leak, I guess
we need to think about if there can be any work around.

> As Ive got no access to the CC server so I can install a trigger I
> have to rely on polling. But Ive noticed that the command for
> retrieving the repository history will stall if there is another
> instance of the command running. Is there anything I should do in the
> SCM to only limit one polling at a time?

I don't think there's anything you can do to improve the situation. If
the user wants to poll multiple jobs in clearcase and yet clearcase is
only allowing one polling at a time. The requests need to be serialized.
  Today apparently it's done by clearcase CLI itself. I guess your
question is whether there's any way to move that serialization into your
SCM, but I don't see how that helps.

I guess the best would be to see if there's a cheaper way to do a polling.


> (So close but yet so far away)
> //Erik
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment