RE: [Openamf-developer] DynaBean problem

[Adrian R. <akr...@pa...>]

How do I turn on debug for one class?  (DefaultGateway)










I think were doing too much logging at the debug level.  I had a problem the
other day tunring on all the logging whitch caused Log4J to  run out of
memory.  We need to remove some of the log.debug's or change them to
log.trace's.

Try turning on the DEBUG level just for DefaultGateway, so we can see more
of
the error info.

On Saturday 06 September 2003 10:25 am, Adrian Roston wrote:
> Turning on debug info seems to crash tomcat.  But here's what it says
> before crash:
>
>
> [DEBUG] OpenAMFConfig - -Looking for: java.lang.reflect.Constructor
> [DEBUG] AMFSerializer - -customClassName :null
> [DEBUG] AMFSerializer - -declaringClass = class java.lang.String
> [DEBUG] AMFSerializer - -Writting Object
> [DEBUG] OpenAMFConfig - -Looking for: java.lang.Class
> [DEBUG] AMFSerializer - -customClassName :null
> [DEBUG] AMFSerializer - -interface = false
> [DEBUG] AMFSerializer - -modifiers = 17
> [DEBUG] AMFSerializer - -declaringClass = null
> [DEBUG] AMFSerializer - -signers = null
> [DEBUG] AMFSerializer - -constructors =
> [Ljava.lang.reflect.Constructor;@2937cd
> [DEBUG] AMFSerializer - -Writting Object
> [DEBUG] OpenAMFConfig - -Looking for: java.lang.reflect.Constructor
> [DEBUG] AMFSerializer - -customClassName :null
> [DEBUG] AMFSerializer - -declaringClass = class java.lang.String
> [DEBUG] AMFSerializer - -Writting Object
> [DEBUG] OpenAMFConfig - -Looking for: java.lang.Class
> [DEBUG] AMFSerializer - -customClassName :null
> [DEBUG] AMFSerializer - -interface = false
> [DEBUG] AMFSerializer - -modifiers = 17
> [DEBUG] AMFSerializer - -declaringClass = null
> [DEBUG] AMFSerializer - -signers = null
> [DEBUG] AMFSerializer - -constructors =
> [Ljava.lang.reflect.Constructor;@e899c
> [DEBUG] AMFSerializer - -Writting Object
>
> I'm using one of the release candidates, probably from a couple weeks ago?
>
>
> --Adrian