FindBugs timeout error

[Jeff Jensen]

Hi,

We run FindBugs via Maven, and have had this error the past few days:

    [echo] Running the FindBugs task...
    [findbugs] Running FindBugs...
    [findbugs] [ERROR] Timeout: killed the sub-process

Can anyone tell me what causes this?

We have a large and growing codebase (over 4500 .java files).  I am
wondering if it kills itself after running a certain duration?

I did not find a timeout setting in FindBugs config.

Or perhaps this message is a red herring, perhaps masking an out of memory
or something else?

This first happened a couple of months ago, and I set the detail to high.
It solved the problem.

These are my properties:

maven.findbugs.enable=true
maven.findbugs.detail=high
maven.findbugs.workHard=true
maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.xml

Any advice?

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Dave Brosius-2]

I'm guessing it's a maven message, i don't know of any such timeout in
findbugs itself.


----- Original Message -----
From: "Jeff Jensen" <jeffjensen@...>
To: <findbugs-discuss@...>
Sent: Saturday, December 10, 2005 2:23 PM
Subject: [FB-Discuss] FindBugs timeout error

> Hi,
>
> We run FindBugs via Maven, and have had this error the past few days:
>
>    [echo] Running the FindBugs task...
>    [findbugs] Running FindBugs...
>    [findbugs] [ERROR] Timeout: killed the sub-process
>
> Can anyone tell me what causes this?
>
> We have a large and growing codebase (over 4500 .java files).  I am
> wondering if it kills itself after running a certain duration?
>
> I did not find a timeout setting in FindBugs config.
>
> Or perhaps this message is a red herring, perhaps masking an out of memory
> or something else?
>
> This first happened a couple of months ago, and I set the detail to high.
> It solved the problem.
>
> These are my properties:
>
> maven.findbugs.enable=true
> maven.findbugs.detail=high
> maven.findbugs.workHard=true
> maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.xml
>
> Any advice?
>
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@...
> http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
>

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Jeff Jensen]

Thanks for the reply.

Maven support says the same thing - "must be in findbugs"...
 

-----Original Message-----
From: Dave Brosius [mailto:dbrosius@...]
Sent: Saturday, December 10, 2005 5:26 PM
To: Jeff Jensen; findbugs-discuss@...
Subject: Re: [FB-Discuss] FindBugs timeout error

I'm guessing it's a maven message, i don't know of any such timeout in
findbugs itself.


----- Original Message -----
From: "Jeff Jensen" <jeffjensen@...>
To: <findbugs-discuss@...>
Sent: Saturday, December 10, 2005 2:23 PM
Subject: [FB-Discuss] FindBugs timeout error

> Hi,
>
> We run FindBugs via Maven, and have had this error the past few days:
>
>    [echo] Running the FindBugs task...
>    [findbugs] Running FindBugs...
>    [findbugs] [ERROR] Timeout: killed the sub-process
>
> Can anyone tell me what causes this?
>
> We have a large and growing codebase (over 4500 .java files).  I am
> wondering if it kills itself after running a certain duration?
>
> I did not find a timeout setting in FindBugs config.
>
> Or perhaps this message is a red herring, perhaps masking an out of memory
> or something else?
>
> This first happened a couple of months ago, and I set the detail to high.
> It solved the problem.
>
> These are my properties:
>
> maven.findbugs.enable=true
> maven.findbugs.detail=high
> maven.findbugs.workHard=true
> maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.xml
>
> Any advice?
>
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@...
> http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
>

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Jon Christiansen]

The findbugs ant task has the following property:

timeout

    Optional attribute. It specifies the amount of time, in
milliseconds, that the Java process executing FindBugs may run before
it is assumed to be hung and is terminated. The default is 600,000
milliseconds, which is ten minutes. Note that for very large programs,
FindBugs may require more than ten minutes to complete its analysis.

Maven is using the anttask to invoke findbugs, therefore is inheriting
this value.

More to come....  gotta dig into some source code to see if there is a
workaround, or if we need to ask the maven plugin crew to add another
property.

What baffles me is one of the main points of maven is to have you
break down your projects into more modular components..... you have
over 4500 files in just one buildable unit?

-JC

On 12/10/05, Jeff Jensen <jeffjensen@...> wrote:

> Hi,
>
> We run FindBugs via Maven, and have had this error the past few days:
>
>     [echo] Running the FindBugs task...
>     [findbugs] Running FindBugs...
>     [findbugs] [ERROR] Timeout: killed the sub-process
>
> Can anyone tell me what causes this?
>
> We have a large and growing codebase (over 4500 .java files).  I am
> wondering if it kills itself after running a certain duration?
>
> I did not find a timeout setting in FindBugs config.
>
> Or perhaps this message is a red herring, perhaps masking an out of memory
> or something else?
>
> This first happened a couple of months ago, and I set the detail to high.
> It solved the problem.
>
> These are my properties:
>
> maven.findbugs.enable=true
> maven.findbugs.detail=high
> maven.findbugs.workHard=true
> maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.xml
>
> Any advice?
>
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@...
> http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
>

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Jeff Jensen]

Thanks Jon.  Hm, I am completely blind - I looked for something like that
and did not see it.  :-|

'fraid so on the components.  This is a huge app.  The largest is over 4500,
the custom framework is over 2500, a sister app just starting and a common
code jar are very small so far (hundreds).  The 4500 set is truly a cohesive
app.  As development continues, we may break it into some separate jars, but
we'd just end up aggregating them under one EAR for deployment.  There
hasn't been any need, motivation, or apparent benefit yet, but it will
appear sometime.  I would like to split into further components sooner than
later.  Bigger fish to fry at the moment though... :-)

Thanks a ton for looking into it!


-----Original Message-----
From: Jon Christiansen [mailto:jon.christiansen@...]
Sent: Saturday, December 10, 2005 11:15 PM
To: Jeff Jensen
Cc: findbugs-discuss@...
Subject: Re: [FB-Discuss] FindBugs timeout error

The findbugs ant task has the following property:

timeout

    Optional attribute. It specifies the amount of time, in milliseconds,
that the Java process executing FindBugs may run before it is assumed to be
hung and is terminated. The default is 600,000 milliseconds, which is ten
minutes. Note that for very large programs, FindBugs may require more than
ten minutes to complete its analysis.

Maven is using the anttask to invoke findbugs, therefore is inheriting this
value.

More to come....  gotta dig into some source code to see if there is a
workaround, or if we need to ask the maven plugin crew to add another
property.

What baffles me is one of the main points of maven is to have you break down
your projects into more modular components..... you have over 4500 files in
just one buildable unit?

-JC

On 12/10/05, Jeff Jensen <jeffjensen@...> wrote:

> Hi,
>
> We run FindBugs via Maven, and have had this error the past few days:
>
>     [echo] Running the FindBugs task...
>     [findbugs] Running FindBugs...
>     [findbugs] [ERROR] Timeout: killed the sub-process
>
> Can anyone tell me what causes this?
>
> We have a large and growing codebase (over 4500 .java files).  I am
> wondering if it kills itself after running a certain duration?
>
> I did not find a timeout setting in FindBugs config.
>
> Or perhaps this message is a red herring, perhaps masking an out of
> memory or something else?
>
> This first happened a couple of months ago, and I set the detail to high.
> It solved the problem.
>
> These are my properties:
>
> maven.findbugs.enable=true
> maven.findbugs.detail=high
> maven.findbugs.workHard=true
> maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.x
> ml
>
> Any advice?
>
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@...
> http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
>

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[Garvin LeClaire]

I have done some of the updates for memory and resource usage in the Maven findbugs plugin and may be able to give information on my experience with the plugin.  I have a version that implements the timeout option which does work, but your original observation of the project size (<4500  files) really should be addressed.   You could use include files to break your analysis into group of packages there by cutting down the time.  This may also give you an idea of which package(s) are taking the bulk of the time.   It may also help you to understand the overall timeout number you may need.

I do have a version of the plugin with timeout enabled, but I would suggest getting a better understanding of your time requirement and investigating breaking your project into modules for Maven to build and analysis in smaller chunks.

There is an article at http://mavenbook.xwiki.com/xwiki/bin/view/Main/MavenAndJ2eeArticle

I found this article useful and used it for a project at http://sourceforge.net/projects/singularity  if you want to see another J2EE build implementation that is more complex.




Jon Christiansen wrote:

The findbugs ant task has the following property:

timeout

    Optional attribute. It specifies the amount of time, in
milliseconds, that the Java process executing FindBugs may run before
it is assumed to be hung and is terminated. The default is 600,000
milliseconds, which is ten minutes. Note that for very large programs,
FindBugs may require more than ten minutes to complete its analysis.

Maven is using the anttask to invoke findbugs, therefore is inheriting
this value.

More to come....  gotta dig into some source code to see if there is a
workaround, or if we need to ask the maven plugin crew to add another
property.

What baffles me is one of the main points of maven is to have you
break down your projects into more modular components..... you have
over 4500 files in just one buildable unit?

-JC

On 12/10/05, Jeff Jensen jeffjensen@... wrote:
  

Hi,

We run FindBugs via Maven, and have had this error the past few days:

    [echo] Running the FindBugs task...
    [findbugs] Running FindBugs...
    [findbugs] [ERROR] Timeout: killed the sub-process

Can anyone tell me what causes this?

We have a large and growing codebase (over 4500 .java files).  I am
wondering if it kills itself after running a certain duration?

I did not find a timeout setting in FindBugs config.

Or perhaps this message is a red herring, perhaps masking an out of memory
or something else?

This first happened a couple of months ago, and I set the detail to high.
It solved the problem.

These are my properties:

maven.findbugs.enable=true
maven.findbugs.detail=high
maven.findbugs.workHard=true
maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.xml

Any advice?

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

    

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

  

_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss

[spiderman2]

Hi all - I'm running into the same problem using Ant 1.6.4 on Solaris. No problems however using Windows and Ant 1.6.5.

My timeout was set to 25 mins but still no luck on solaris.

Did you find a solution yet? I'm not using maven so the error message must be coming from Findbugs.

[findbugs] Timeout: killed the sub-process
 [findbugs]     at org.apache.tools.ant.taskdefs.Java.fork(Java.java:754)
 [findbugs]     at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:171)
 [findbugs]     at edu.umd.cs.findbugs.anttask.FindBugsTask.execFindbugs(FindBugsTask.java:780)
 [findbugs]     at edu.umd.cs.findbugs.anttask.FindBugsTask.execute(FindBugsTask.java:492)
 [findbugs]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 [findbugs]     at org.apache.tools.ant.Task.perform(Task.java:364)
 [findbugs]     at org.apache.tools.ant.Target.execute(Target.java:341)
 [findbugs]     at org.apache.tools.ant.Target.performTasks(Target.java:369)
 [findbugs]     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 [findbugs]     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 [findbugs]     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 [findbugs]     at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 [findbugs]     at org.apache.tools.ant.Main.runBuild(Main.java:668)
 [findbugs]     at org.apache.tools.ant.Main.startAnt(Main.java:187)
 [findbugs]     at org.apache.tools.ant.Main.start(Main.java:150)
 [findbugs]     at org.apache.tools.ant.Main.main(Main.java:240)
 [findbugs] Output saved to bugReport.html


Thanks,
Shawn



Hi,

We run FindBugs via Maven, and have had this error the past few days:

    [echo] Running the FindBugs task...
    [findbugs] Running FindBugs...
    [findbugs] [ERROR] Timeout: killed the sub-process

Can anyone tell me what causes this?

We have a large and growing codebase (over 4500 .java files).  I am
wondering if it kills itself after running a certain duration?

I did not find a timeout setting in FindBugs config.

Or perhaps this message is a red herring, perhaps masking an out of memory
or something else?

This first happened a couple of months ago, and I set the detail to high.
It solved the problem.

[Sachin Deshmukh]

I'm running into the same problem, running findbugs for large codebase and it timeout after 10 mins.
 
I'm not using maven so the error message must be coming from Findbugs.
 

findbugs:
 [findbugs] Executing findbugs from ant task
 [findbugs] Running FindBugs...
 [findbugs] Timeout: killed the sub-process
 [findbugs]     at org.apache.tools.ant.taskdefs.Java.fork(Java.java:754)
 [findbugs]     at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:171)
 
 [findbugs]     at edu.umd.cs.findbugs.anttask.AbstractFindBugsTask.execFindbugs
(AbstractFindBugsTask.java:334)
 [findbugs]     at edu.umd.cs.findbugs.anttask.AbstractFindBugsTask.execute(Abst
ractFindBugsTask.java:207)
 [findbugs]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:275)
 [findbugs]     at org.apache.tools.ant.Task.perform(Task.java:364)
 [findbugs]     at org.apache.tools.ant.Target.execute(Target.java:341)
 [findbugs]     at org.apache.tools.ant.Target.performTasks(Target.java:369)
 [findbugs]     at org.apache.tools.ant.Project.executeSortedTargets(Project.jav
a:1216)
 [findbugs]     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 
 [findbugs]     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(De
faultExecutor.java:40)
 [findbugs]     at org.apache.tools.ant.Project.executeTargets(Project.java:1068
)
 [findbugs]     at org.apache.tools.ant.Main.runBuild(Main.java:668)
 [findbugs]     at org.apache.tools.ant.Main.startAnt(Main.java:187)
 [findbugs]     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
 [findbugs]     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Jeff Jensen wrote:

Hi,

We run FindBugs via Maven, and have had this error the past few days:

    [echo] Running the FindBugs task...
    [findbugs] Running FindBugs...
    [findbugs] [ERROR] Timeout: killed the sub-process

Can anyone tell me what causes this?

We have a large and growing codebase (over 4500 .java files).  I am
wondering if it kills itself after running a certain duration?

I did not find a timeout setting in FindBugs config.

Or perhaps this message is a red herring, perhaps masking an out of memory
or something else?

This first happened a couple of months ago, and I set the detail to high.
It solved the problem.

These are my properties:

maven.findbugs.enable=true
maven.findbugs.detail=high
maven.findbugs.workHard=true
maven.findbugs.excludeFilter=src/conf/findbugs/findbugsexcludefilter.xml

Any advice?

_______________________________________________
Findbugs-discuss mailing list
[e-mail]
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss