Steve:

Update on this issue: After much hair-pulling, Shash and I have figured out partly why 
this happens. It has to do with the new Fortress configuration meta-data that's done 
automagically by Xdoclet, as we suspected. Due to strangeness with classloaders, that 
information is sometimes not digested correctly. As a partial fix, I've added *very* 
detailed dump information to KeelContainer in the event the problem occurs. So, if it 
happens to you again, have a look in catalina.out (or wherever your container dumps 
stderr) and you'll see a full trace of whatever the container got as far as meta 
information. Look for WARN or FATAL in there (as I'm doing a certain amount of 
validation as part of the dump) and make sure the names line up the way you think they 
should for the model that the stacktrace is complaining about. If it is a legit config 
error, this makes it easy to find at least. It's helped me catch a few subtle mistakes 
I made already.

Research continues, but this should help get you rolling again.

Regards,

Mike

On Sun, 05 Oct 2003 09:30:43 -0500
Stephen Davidson <[EMAIL PROTECTED]> wrote:

> Hi Michael.
> 
> It is NOT intermittent for me.  I blew away my entire build last night 
> (specifically, deleted the install & deploy directories in keel-build), ran a 
> completeinstall (which tied up my phone line for 2.5 hrs), and this thing 
> still came back.  Running you clean command, and it worked this time.
> 
> Anything you want me to look for next time I see it?  Maybe a bug should be opened 
> on this as well, with the current workaround attached?  That way, if anyone else 
> trips accross it, they may be able to post additional info, 
> as well as get unstuck.
> 
> Regards,
> Steve
> 
> Michael Nash JGlobal.com wrote:
> > Steve:
> > 
> > You've run into an intermittent issue that both Shash and I have been fighting 
> > with for a couple of days now. All I can suggest at the moment is an "ant 
> > -Ddeploy.name=yourdeplooy clean" and a new assemble-deploy. We're not entirely 
> > sure what is causing it, but we're chasing it down!
> > 
> > Mike
> > 
> > On Sat, 04 Oct 2003 20:14:13 -0500
> > Stephen Davidson <[EMAIL PROTECTED]> wrote:
> > 
> > 
> >>Greetings.
> >>
> >>At some point, I did a full rebuild sometime after I updated various projects.  So 
> >>I don't know when the update that killed me was downloaded.  But now I am getting 
> >>the attached error on startup.
> >>
> >>What package has been added to the minimal list?  Or have I done something strange 
> >>again?
> >>
> >>Thanks,
> >>Steve
> >>
> 
> -- 
> Java/J2EE Developer/Integrator
> Co-Chair, Dallas/FortWorth J2EE Sig
> 214-724-7741
> 
> 
> http://keelframework.org/documentation
> Keelgroup mailing list
> [EMAIL PROTECTED]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com


Michael Nash

JGlobal Ltd.
 http://www.jglobal.com

Bahamas Commerce and Trade
http://www.bahamascommerce.com

http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

Reply via email to