Re: Re: Re: Re: Re: Re: Binding takes for ages on Jonas-server. No additional info to troubleshoot

Thanks a lot Guillaume,

Stefaan, I changed that monolog configuration and now we see a lot of
Easybeans debug messages in our logfile. I will show you tomorrow ...

Best Regards,

Paul Adriaenssens

> Please set back the monolog configuration to javaLog:
> log.config.classname
> org.objectweb.util.monolog.wrapper.javaLog.LoggerFactory
>
> Easybeans is printing its debug information on a logger backed by Java
> util
> Log.
>
> --G
>
> 2011/8/18 Stefaan Somers <[email protected]>
>
>> No luck either.
>>
>> I hereby include the content of the trace.properties :
>>
>>
>> #
>> ----------------------------------------------------------------------=
-
>> # This is a default configuration file for monolog.
>> #
>> # 2 handlers have been defined : tty (System.out) and logf (file)
>> #
>> # Patterns for each handler may include these possible values :
>> # %h    the thread name
>> # %O{1} the Class name (basename only)
>> # %M    the method name
>> # %L    the line number
>> # %d    the date
>> # %l    the level
>> # %m    the message itself
>> # %n    a new line
>> #
>> # A list of predefined loggers is given at the end of the file.
>> # Each logger inherits from its parent for properties not defined.
>> # The root logger is "root". It must always be defined.
>> #
>> # Each logger is associated with a level that can be one of :
>> # ERROR | WARN | INFO | DEBUG | FATAL | INHERIT
>> #
>> # -> More info on http://www.objectweb.org/monolog/doc.html
>> #
>> ----------------------------------------------------------------------=
-
>>
>> #
>> ----------------------------------------------------------------------=
-
>> # Define which wrapper to use (=3D javaLog)
>> #
>> ----------------------------------------------------------------------=
-
>> # For Log4j you need to add log4j.jar
>> log.config.classname
>> org.objectweb.util.monolog.wrapper.log4j.MonologLoggerFactory
>> # log.config.classname
>> org.objectweb.util.monolog.wrapper.javaLog.LoggerFactory
>>
>>
>> #----------
>> # PrivateCompany
>> #----------
>>
>> logger.net.democritus.level INFO
>> logger.com.privatecompany.level INFO
>> logger.net.palver.level INFO
>> logger.org.ow2.easybeans.level DEBUG
>>
>>
>>
>> On 18 August 2011 15:57, Guillaume Sauthier (OW2)
>> <[email protected]> wrote:
>> > the format is:
>> > logger.<name>.level <level>
>> >
>> > you missed the .level
>> >
>> > --G
>> >
>> >
>> > 2011/8/18 Stefaan Somers <[email protected]>
>> >>
>> >> Hi,
>> >>
>> >> I included the following line in trace.properties, but I see no
>> >> additional logging :
>> >> logger.org.ow2.easybeans DEBUG
>> >>
>> >> Greetings
>> >>
>> >> On 18 August 2011 13:26, Guillaume Sauthier (OW2)
>> >> <[email protected]> wrote:
>> >> > Maybe you can add traces for the org.ow2.easybeans logger ?
>> >> > So that we can see where time is consumed.
>> >> > --G
>> >> >
>> >> > 2011/8/18 Stefaan Somers <[email protected]>
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> we have an application with many EJB's. Is it normal that the
>> startup
>> >> >> takes more than 10 minutes. Are there any steps I can do, to
>> >> >> troubleshoot this performance-problem.
>> >> >>
>> >> >> 18/08/11 13:02:26 (I) JCLLoggerAdapter.info : Not binding factor=
y
>> to
>> >> >> JNDI, no JNDI name configured
>> >> >> 18/08/11 13:16:39 (I) JContainer3.start : Container
>> >> >>
>> >> >>
>> >> >>
>> 'D:\jonas-full-5.1.4\BASE\work\apps\jonas\pocAppEAR_2011.08.18-12.56.3=
1.ear\pocAppEJB.jar'
>> >> >> [104 SLSB, 0 SFSB, 0 MDB] started in 891.270 ms
>> >> >>
>> >> >>
>> >> >> Greetings,
>> >> >>
>> >> >> Stefaan Somers
>> >> >
>> >> >
>> >
>> >
>>
>