You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Simon Laws <si...@googlemail.com> on 2010/01/05 09:51:21 UTC
Re: Build failed in Hudson: Tuscany-2x #369
This is a new one on me. Am just double checking that I'm not getting
a similar effect locally. Anyone else seeing this?
Simon
Re: Build failed in Hudson: Tuscany-2x #369
Posted by ant elder <an...@gmail.com>.
On Tue, Jan 5, 2010 at 12:02 PM, Simon Laws <si...@googlemail.com> wrote:
> After fixing up some other maven issues I've just got a clean 2.x
> build on my Linux (Redhat) machine. This is with the Sun JDK 1.6 and
> Maven 2.1.0. So it doesn't seem to be anything intrinsically wrong
> with the build. Where do you look to find out what environment this
> build ran on in Hudson?
>
> Simon
>
You need a Hudson userid and then login here:
http://hudson.zones.apache.org/hudson/job/Tuscany-2x/, you can see the
current setup in either a build console log or by clicking on
"configure". Currently its running on Ubuntu using Sun JDK 1.6 using
the latest Maven release ( i think that means 2.2.1).
...ant
Re: Build failed in Hudson: Tuscany-2x #369
Posted by Simon Laws <si...@googlemail.com>.
After fixing up some other maven issues I've just got a clean 2.x
build on my Linux (Redhat) machine. This is with the Sun JDK 1.6 and
Maven 2.1.0. So it doesn't seem to be anything intrinsically wrong
with the build. Where do you look to find out what environment this
build ran on in Hudson?
Simon
Re: Build failed in Hudson: Tuscany-2x #369
Posted by Simon Laws <si...@googlemail.com>.
Now I'm back to getting a clean build I do see lots of handles being
help open (got up to 2500 at one point). It seems that Jetty holds
onto some things. For example,
File C:\Documents and Settings\slaws\Local
Settings\Temp\Jetty_0_0_0_0_8085_helloworld.js.client.war__helloworld.js.client__s3b53o\webapp\WEB-INF\lib\XmlSchema-1.4.2.jar
and
File C:\Documents and Settings\slaws\Local
Settings\Temp\Jetty_0_0_0_0_8085_helloworld-bpel.war__helloworld-bpel__-1g06s\webapp\WEB-INF\classes\jpadb\seg0\c691.dat
As far as I can tell these are both held open through to the end of
the full build.
Simon
Re: Build failed in Hudson: Tuscany-2x #369
Posted by Raymond Feng <en...@gmail.com>.
Hi,
I tried to monitor the file handles opened by the maven build on Windows
using a set of utilities from [1]. Here are some observations:
a) The build keeps around 58 jars open from
modules\<module>\target\<module.jar>
b) Java files are opened and closed as the compilation goes
c) OSGi related tests open bundle files in the cache
d) BPEL related tests open .data files for the derby database (>100 files)
I don't see accumulation of file handles though. Maybe d) or c) will create
a peak of opened files.
[1] http://technet.microsoft.com/en-us/sysinternals/default.aspx
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <si...@googlemail.com>
Sent: Wednesday, January 06, 2010 3:09 AM
To: <de...@tuscany.apache.org>; <an...@apache.org>
Subject: Re: Build failed in Hudson: Tuscany-2x #369
> The handle count did start to creep up as the build progresses.
> However my build failed due to local changes so I have to fix those
> first.
>
> Note. I'm not absolutely sure that the number I'm looking at is
> directly related to the problem we are seeing just yet so don't assume
> that I have a grip on this just yet.
>
> Simon
Re: Build failed in Hudson: Tuscany-2x #369
Posted by Simon Laws <si...@googlemail.com>.
The handle count did start to creep up as the build progresses.
However my build failed due to local changes so I have to fix those
first.
Note. I'm not absolutely sure that the number I'm looking at is
directly related to the problem we are seeing just yet so don't assume
that I have a grip on this just yet.
Simon
Re: Build failed in Hudson: Tuscany-2x #369
Posted by Simon Laws <si...@googlemail.com>.
Yep, good description of the kind of thing it could be here [1]. A
couple of things. What's changed recently? Also is it just the one
test or is it the result of running all the tests. As you say, tricky
to tell.I can comment out the failing module and see if that gets a
clean build on Hudson. Not sure that tells us much though.
I'm just watching the open handle count on my Windows box as the build
progresses and the top level Java process running the main Maven build
hovers around the 500 mark. Doesn't seem to be increasing but it
hasn't finished yet. I'll shout if I find anything interesting.
Simon
[1] http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/
Re: Build failed in Hudson: Tuscany-2x #369
Posted by ant elder <an...@gmail.com>.
On Tue, Jan 5, 2010 at 8:51 AM, Simon Laws <si...@googlemail.com> wrote:
> This is a new one on me. Am just double checking that I'm not getting
> a similar effect locally. Anyone else seeing this?
>
> Simon
>
The hudson build is failing with this (IOException: error=24, Too many
open files) every time now so i guess its not just some transient
condition. From a quick google it sounds like we may have some tuscany
code or testcase that isn't doing a close, which could be a little
tricky to track down.
...ant