I've created a Jira issue to track this problem at: <http://hackydev.ics.hawaii.edu:8080/browse/HACK-776>
It would be good if those involved in this issue (Cam, Aaron, Hongbing, others?) would please add themselves as "watchers" to this issue. That way, you will get emails when the issue is commented and can participate in the discussion and resolution of this issue. It's assigned to Cedric for the time being. Cheers, Philip ----- Original Message ----- From: Aaron Akihisa Kagawa <[EMAIL PROTECTED]> Date: Tuesday, August 29, 2006 11:11 am Subject: Re: [HACKYSTAT-DEV-L] hackystat build problems (fwd) To: Philip Johnson <[EMAIL PROTECTED]> Cc: [email protected] > Hey Philip, > > I'm pretty sure that Hongbing is getting this error too. And there > was an email from Cam a while ago too. > > Here are my answers to your questions. > (a) Nope. > (b) Yes, the problems reappeared when I did get a clean tomcat (the > latest version) and got the latest Java version. But, I've gotten > this error before. > (c) Windows. I actually looked at my local environment. There isn't > anything there that is special. I even deleted a few things from my > enviroment to get it to be very clean, probably no different than > anyone elses computer. > > So, I thought it was very weird that this occured as soon as I > upgraded my tomcat from 5.5.9 to what ever the latest version is. I > actually think that I was using a later version of tomcat a while > ago and was experiencing these problems but somehow found out that > 5.5.9 didn't cause the problems. However, I upgraded to the latest > because there was a change to PageWriter that was incommpatible > with 5.5.9 (i think it was a JSP compilation issue). > > Anyway, when Hongbing comes back we'll dive into this a little > more. > > thanks, Aaron > > ----- Original Message ----- > From: Philip Johnson <[EMAIL PROTECTED]> > Date: Tuesday, August 29, 2006 9:16 am > Subject: Re: [HACKYSTAT-DEV-L] hackystat build problems (fwd) > To: [email protected] > > > Hi Aaron, > > > > I can confirm that I am not getting this error locally, nor are > we > > experiencing it in the > > daily build. I have the following thoughts: > > > > (a) are you intermixing installations of binary distributions > with > > source builds on the > > same Tomcat? It's possible for Tomcat to become confused in this > > situation. > > (b) have you tried re-unzipping Tomcat to get a clean > environment? > > I am wondering about > > the state of the work/ directory and so forth. > > > > (c) is this occurring on a Windows or non-Windows OS? If it's > > Windows, then it seems > > likely it's some sort of irritating local environment > configuration > > problem, since we > > can't reproduce it here. If it's non-Windows, then please send > us > > more details so we can > > try to reproduce it. > > > > Cheers, > > Philip > > > > --On Sunday, August 27, 2006 8:30 PM -1000 Aaron Kagawa > > <[EMAIL PROTECTED]> wrote: > > > > > FYI - I gets this error every time I build now. I can't seem > to > > figure it out. > > > > > > thanks, Aaron > > > > > > At 08:21 AM 8/25/2006, you wrote: > > >> From Hongbing: > > >> > > >> Yes, I still have this error. On Linux I have to explicitly all > > >> deploySoap task otherwise the server will not receive data. > > >> > > >> I saw a couple of emails on this issue. I have a theory that > might> >> prevent this error forever. With some investigations and > > >> review of our build files I found that we might deploy soap > before> >> Hackystat web application is sucessfully deployed to > > >> Tomcat, which takes some time because we have a lot stuff in > > >> hackystat\<WEB-INF>. In Hackystat ANT task > > >> hackyCore_Build.hotDeployHackystat, we simply do this: > > >> > > >> <loadfile property="install.results " srcFile="install- > > results.tmp" /> > > >> <echo level="info" message="Install results: > > ${install.results}"/>>> <delete file="install-results.tmp" /> > > >> <makeEcho message="Completed > > >> hackyCore_Build.hotDeployHackystat" > > >> prefix="hackyCore_Build.hotDeployHackystat"/> > > >> > > >> The thing is that we may deploy our application sucessfully. The > > >> missing part is that we do not assure that /hackystat > > application is > > >> listable, which means Tomcat is still loading Hackystat but we > > think>> it is finished. > > >> > > >> My theory is that the exception happens when Tomcat is busy > loading> >> Hackystat application. To ensure that /hackystat is > correctly> >> listed, we can add one more get task to query > /hackystat or > > >> hackystat manager either after task hotDeployHackystat or > before > > task>> deploySoap. > > >> > > >> BTW: fork does not do anything good except that it will start > a new > > >> JVM instance, which may have a delay for /hackystat getting > > >> ready for soap deployment. > > >> > > >> I am leaving here soon and do not have much time to work on this > > >> issue. You can play around with ANT to add this check. It is > > >> a tomcat issue not SOAP issue according to my understanding. > > >> > > >> Thanks, > > >> Hongbing > > >> > > >> > > >> At 01:04 AM 8/25/2006, you wrote: > > >>> Okay.. this problem has reappeared. What's irritating about this > > >>> error is that it only occurs sometimes, but sometimes in > bunches.> >>> > > >>> I'm using the following software versions. > > >
