Can you please attach a thread dump?

Do the warnings contain relative paths?

Hi,

Sorry I was in the middle of updating this issue and the network went down. The only threadump I can attach is from my-jenkins:8080/threadDump and I haven't found any useful information there. Do you have a way to generate a reliable thread dump of the process?

The warnings are all in java source files. I am attaching the config for the instance that is stuck now.

sorry, wrong screenshot. Here's the right one.

For thread dumps see: https://wiki.jenkins-ci.org/display/JENKINS/Build+is+hanging

Do the warnings contain relative paths? Can you please show a single warning?

The compiler warnings. They all relates to Java source files. I don't know what you mean by relative path.

I need something like the following snippet from YOUR console log:

compile-warning:
    [mkdir] Created dir: C:\Desenvolvimento\Java\jfg\build\build\warning
    [javac] Compiling 34 source files to C:\Desenvolvimento\Java\jfg\build\build\warning
    [javac] ----------
    [javac] 1. WARNING in C:\Desenvolvimento\Java\jfg\src\jfg\AttributeException.java (at line 3)
    [javac] 	public class AttributeException extends RuntimeException
    [javac] 	             ^^^^^^^^^^^^^^^^^^
    [javac] The serializable class AttributeException does not declare a static final serialVersionUID field of type long
    [javac] ----------
    [javac] ----------
    [javac] 2. WARNING in C:\Desenvolvimento\Java\jfg\src\jfg\gui\swt\SWTTextBuilder.java (at line 85)
    [javac] 	protected void addValidation(Text text, Object type)
    [javac] 	                                  ^^^^
    [javac] The parameter text is never read

Then I need to know, if the path in a warning above is relative (contains no C: or / in the beginning) or absolute. If you would paste one of your actual warnings I will see it anyway...

And the thread dump is still missing

Sorry it took so long to get those info. Let me know if you need anything else.

Ok, thanks, seems that the problem is unrelated to JENKINS-10097. The process "hangs" while scanning for warnings using a regular expression matcher. How large is your console log? The eclipse parsers is a slow multi-line parser that reads the whole console log into a buffer. Would it be possible to pipe the warnings to an additional file?

BTW: I think you do not need to activate the Eclipse parser, since the warnings seems to be in the default javac format (due to the maven plugin).

350kb.

After 1h15, it is still on at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86)

Seems a lot for ~4000 lines

Can you please check if that happens with the plain Java parser, too? Or why are you using the Eclipse Parser? Are there warnings not covered?

it does work with only the Javac compiler as the problem is in the eclipse parser it seems. I can only use the Javac compiler and I get a proper list of warnings.

Thanks!

(Hint: maybe we should document somewhere that Maven-based jobs using the jdt compiler do not need to use the eclipse parser)

Well, actually the warnings are different if you build with maven and tycho (then you need the Eclipse parser...).

But I think it would be worth adding a note in the documentation at least.

Are you using a maven job or freestyle job to build your project? Currently there is no special support for maven jobs in my plug-in, maybe I should add that.

I create JENKINS-15933 as a followup for this issue.

Setting the resolution to won't fix since there is almost no way to improve the speed of the multi-line Eclipse parser.

I am using a maven-based job. According to JENINS-15933, eclipse would be detected automatically as far as I understand. That's probably not what I want.

By the way, I am not so sure that it's a performance problem, really. Still Parsing 4000 lines after 2 hours, something must definitely be wrong. Maybe I should left it running for the night to see how it goes.

Thanks.