Strange, I don't seem to have gotten the original message on this thread. Running with asserts off does cause failures, but I don't totally understand the behavior that's being described. Daryl, if for some reason -ea doesn't fix it for you, let me know.
Rich Eddie O'Neil wrote: > Heh...I think I ran into this a couple of weeks ago myself. I >believe that those fail because asserts aren't enabled via the >javaOptions attribute passed to <start-server> in "start.with.shmem". >We'd just need to set this value on javaOptions: > > -ea:org.apache.beehive.netui... > >Give that a shot and see if it fixes the failures. > >Eddie > > > >On 9/29/05, Daryl Olander <[EMAIL PROTECTED]> wrote: > > >>I've been doing a bit of debugging while running the DRT server in NetUI. My >>usual practice is to start the server from the netui/test/webapps/drt >>directory through the 'ant start' command and then run the DRTs through the >>'ant drt.running' command. If I do this, everything passes fine. When I >>start the server using 'ant start.with.shmem', I get two failures in the >>DRTs, ActionChaining and OverloadedActions. I did a bit of debugging on >>this, and what appears to happen is that we are looking up and action for " >>action5b.do" which should be the method "action5b". For some reason, the >>action isn't found using reflection, but it is in the page flow. It must be >>in the class file because if I stop and start the server without a rebuild >>it all works. >> >>Anyone see this behavior before? Rich, do you have any idea what might be >>happening here and why starting the server with shmem would change the >>behavior? >> >> >> >> > > >
