Re: [Wrapper-user] more on problems with filters- restart never works

[Leif M. <le...@ta...>]

Jennifer,
    Does this solve the problems you were having with OutOfMemory 
messages as
well?  Were those all happening on startup?

Cheers,
Leif

Jennifer Kolar wrote:

> That did it. I didn't remember the Stop in the wrappersimpleapp...
> Cool.
> perfect.
> Thanks
>
> On Mar 9, 2004, at 4:37 PM, Leif Mortenson wrote:
>
>> Jennifer,
>>    I have been looking into this some more.  I added some more debug  
>> output to the
>> WrapperManager class to make it easier to debug this sort of 
>> problem.   You can try
>> it from CVS if you like.  (SourceForge's public CVS is 24 hrs behind  
>> the dev archive)
>>
>>    Looking over the debug log output that you sent me again, I 
>> noticed  the following
>> line:
>>
>> INFO   | jvm 7    | 2004/02/26 19:33:00 | Thread,  
>> WrapperSimpleAppMain, handling the shutdown process.
>>
>>    This tells me that the WrapperSimpleApp helper class's main 
>> thread  called
>> WrapperManager.stop.  This will happen if your class's main method  
>> throws an
>> uncaught exception.  Does that sound what might be happening?
>>
>>    If this is the case then I would expect to have seen the 
>> following  output in your log.
>> The log you posted was edited so you may have removed it.  Could you  
>> please confirm
>> one way or the other?
>>
>> INFO   | jvm 7    | 2004/02/26 19:32:59 | WrapperSimpleApp:  
>> Encountered an error running main: (Your exception)
>>
>>    If you are trying to invoke a restart on the above exception, it  
>> will not work because
>> the call to WrapperManager.stop will override the restart request 
>> and  stop the Wrapper
>> along with its JVM.
>>
>> Cheers,
>> Leif
>