Re: Re: Cruisecontrol locks up

Okay. Here's the info:

Using Cruise Control at /home/dev/stuff/cruisecontrol-2.1.4/main
/home/dev/stuff/cruisecontrol-2.1.4/main
/usr/IBMJava2-141/bin/java -Xmx384M -cp  
/home/dev/stuff/cruisecontrol-2.1.4/main/bin:/usr/IBMJava2-141/lib/ 
tools.jar:/home/dev/stuff/cruisecontrol-2.1.4/main/dist/ 
cruisecontrol.jar:/home/dev/stuff/cruisecontrol-2.1.4/main/lib/ 
log4j.jar:/home/dev/stuff/cruisecontrol-2.1.4/main/lib/jdom.jar:/home/ 
dev/stuff/cruisecontrol-2.1.4/main/lib/ant.jar:/home/dev/stuff/ 
cruisecontrol-2.1.4/main/lib/xerces.jar:/home/dev/stuff/cruisecontrol 
-2.1.4/main/lib/mail.jar:/home/dev/stuff/cruisecontrol-2.1.4/main/lib/ 
optional.jar:/home/dev/stuff/cruisecontrol-2.1.4/main/lib/junit.jar:/ 
home/dev/stuff/cruisecontrol-2.1.4/main/lib/activation.jar:/home/dev/ 
stuff/cruisecontrol-2.1.4/main/lib/jdepend.jar:/home/dev/stuff/ 
cruisecontrol-2.1.4/main/lib:. CruiseControl -port 7999

The last little bit in stdout:

[cc]Dec-12 10:49:31 belIncrementer- Incrementing label: build.80 ->  
build.81
[cc]Dec-12 10:49:31 Project       - Project marineproj:  merging  
accumulated log files
[cc]Dec-12 10:49:34 Project       - Project marineproj:  Writing log  
file [/home/dev/n4/logs/marine/log20031212102639Lbuild.80.xml]
[cc]Dec-12 10:49:37 Project       - Project marineproj:  Serializing  
project to [marineproj.ser]
[cc]Dec-12 10:49:37 Project       - Project marineproj:  publishing  
build results
[cc]Dec-12 10:49:38 EmailPublisher- reportSuccess is set to 'fixes',  
not sending emails for repeated successful builds.
[cc]Dec-12 10:49:38 Project       - Project marineproj:  idle
[cc]Dec-12 10:49:38 Project       - Project marineproj:  build finished

Looking at the cruisecontrol.log is a bit interesting.  
cruisecontrol.log is dated 10:29, which is when the build began.  
cruisecontrol.log.1 is dated 10:49, which is when the build finished.  
It seems odd that cruisecontrol.log.1 is newer. Here are the last few  
lines of each:

cruisecontrol.log

2003-12-12 10:29:50,948 [main     ] DEBUG BeanUtils        -    
copyProperty(com.puppycrawl.tools.checkstyle.checks.TypeNameCheck@5905c3 
a7, tabWidth, 3)
2003-12-12 10:29:50,948 [main     ] DEBUG BeanUtils        -     target  
propName=tabWidth, type=int, index=-1, key=null
2003-12-12 10:29:50,948 [main     ] DEBUG BeanUtils        -          
USING CONVERTER  
org.apache.commons.beanutils.converters.IntegerConverter@4177038f
2003-12-12 10:29:50,948 [main     ] DEBUG BeanUtils        -    
copyProperty(com.puppycrawl.tools.checkstyle.checks.TypeNameCheck@5905c3 
a7, classLoader, org.apache.tools.ant.AntClassLoader@1eb2c382)
2003-12-12 10:29:50,948 [main     ] DEBUG BeanUtils        -     target  
propName=classLoader, type=class java.lang.ClassLoader, index=-1,  
key=null
2003-12-12 10:29:50,949 [main     ] DEBUG BeanUtils        -    
copyProperty(com.puppycrawl.tools.checkstyle.checks.TypeNameCheck@5905c3 
a7, messages,  
com.puppycrawl.tools.checkstyle.api.LocalizedMessages@6b2b4393)
2003-12-12 10:29:50,949 [main     ] DEBUG BeanUtils        -     target  
propName=messages, type=class  
com.puppycrawl.tools.checkstyle.api.LocalizedMessages, index=-1,  
key=null

cruisecontrol.log.1

2003-12-12 10:49:34,320 [BuildQueueThread] DEBUG Project          -  
Project marineproj:  Writing log file  
[/home/dev/n4/logs/marine/log20031212102639Lbuild.80.xml]
2003-12-12 10:49:37,874 [BuildQueueThread] DEBUG Project          -  
Project marineproj:  Serializing project to [marineproj.ser]
2003-12-12 10:49:37,874 [BuildQueueThread] INFO  Project          -  
Project marineproj:  publishing build results
2003-12-12 10:49:38,017 [BuildQueueThread] DEBUG EmailPublisher   -  
reportSuccess is set to 'fixes', not sending emails for repeated  
successful builds.
2003-12-12 10:49:38,085 [BuildQueueThread] INFO  Project          -  
Project marineproj:  idle
2003-12-12 10:49:38,085 [BuildQueueThread] DEBUG Project          -  
Project marineproj:  build finished

Using ps, I can confirm that the ant process is complete.

Okay, now let's see if I can do anything with JMX. I try and force a  
build of another project. The entry appears in cruisecontrol.log.1 as:

[cc]Dec-12 12:19:25 jectController- tripsproj Controller: forcing build

but nothing seems to happen. If I try and do a stop/start of the whole  
manager, the most interesting thing in the log is:

2003-12-12 12:24:45,333 [BuildQueueThread] DEBUG BuildQueue       -  
BuildQueue.run() interrupted. Stopping?java.lang.InterruptedException:  
JVMLK007: operation interrupted
    at java.lang.Object.wait(Native Method)    at  
java.lang.Object.wait(Object.java:438)
    at net.sourceforge.cruisecontrol.BuildQueue.run(BuildQueue.java:87)  
   at java.lang.Thread.run(Thread.java:568)
2003-12-12 12:24:45,336 [BuildQueueThread] INFO  BuildQueue       -  
BuildQueue thread is no longer alive
2003-12-12 12:24:51,579 [BuildQueueThread] INFO  BuildQueue       -  
BuildQueue started

Things seem to be working correctly now. the last line in  
cruisecontrol.log.1 is the java ant command. Strangely, it looks like  
cruisecontrol.log is now in charge again, the times are 12:27 for  
cruisecontrol.log.1 and 12:31 for cruisecontrol.log. It seems like they  
have different purposes, I guess, so perhaps this isn't so strange.

It looks like cruisecontrol.log.1 was reaching its maximum size. Don't  
know if this could be part of the issue.

Anyway, hopefully the above information is useful enough to either  
pinpoint the problem or at least suggest further tests.

Again, the stats:

RH9, IBM JDK 1.4.1. CC 2.1.4 with some minimal changes (only  
cruisecontrol.sh).

I added jdepend.jar to the CLASSPATH as you can see above. The entry  
for $CCDIR/bin is for log4j.properties only.

Hope that helps.

--Tim

On Dec 9, 2003, at 11:03 AM, Jeffrey Fredrick wrote:

> yup:  http://c2.com/w4/cc/wiki.cgi?TurnOnDebug
>
> then look for the cruisecontrol.log file as it will have info about  
> which
> thread sends which message.  the one named "Project <projectname>  
> thread" is
> the scheduling thread for the project.
>
> Jtf
>
> -----Original Message-----
> From: cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx
> [mailto:cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of  
> Tim
> McNerney
> Sent: Tuesday, December 09, 2003 10:52 AM
> To: Jeffrey Fredrick
> Cc: cruisecontrol-user@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [Cruisecontrol-user] Re: Cruisecontrol locks up
>
>
> It has been a while since I spent any time looking at the hangs. I'll
> do so for the next day or so and send in my findings.
>
> I seem to recall it is a bit confusing to tell because you can't just
> take the last line in the output of a multi-project configuration as
> certain things will move into the queue before they are run. I seem to
> recall that the build always appears to be complete, but I don't
> remember checking on the state of the build process, which I'll do.
>
> Is there a good way to turn up logging/debug so that I can report more
> useful information?
>
> --Tim
>
> On Dec 9, 2003, at 10:07 AM, Jeffrey Fredrick wrote:
>
> > Any idea of where it hangs up?  During the build, while merging logs,
> > publishing, idle?
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for  
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys  
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Cruisecontrol-user mailing list  
> Cruisecontrol-user@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click