New MBean causes JBoss to log excessively

cmasson Mar 8, 2002 12:06 PM

Hi

My MBean runs successfully in JBoss. However, since I've added it, JBoss seems to spew out an enormous amount of additional information to the console.

Here is an extract of the original log showing a JBoss MBean being initialized:

[JNDIView] Initializing
[JNDIView] Initialized

Here is the extract once I've added my own Mbean - suddenly much more is logged (my MBean was initialized earlier).

[JNDIView] Initializing
[Default] 4757 [JBossMain] INFO org.jboss.naming.JNDIView - Initializing
[JNDIView] Initialized
[Default] 4757 [JBossMain] INFO org.jboss.naming.JNDIView - Initialized

Any help would be appreciated.
Thanks
Cornel.

1. Re: New MBean causes JBoss to log excessively

cmasson Mar 8, 2002 12:17 PM (in response to cmasson)

Some more info:

My MBean does NOTHING in its constructor, nor in init() nor start(). Yet I've noticed output from some MBean methods in the log on startup.

Does JBoss actually trigger ALL public methods on startup?
Actions
2. Re: New MBean causes JBoss to log excessively

adrian.brock Mar 8, 2002 12:24 PM (in response to cmasson)

ServiceMBeanSupport implements all methods with
no method bodies.

Regards,
Adrian
Actions
3. Re: New MBean causes JBoss to log excessively

cmasson Mar 11, 2002 6:02 AM (in response to cmasson)

The log4j appender for the console is set to a theshold of INFO, yet i'm seeing a lot of 'DEBUG' statements in there - does anyone have an idea how to switch off those debug statements?
Actions
4. Re: New MBean causes JBoss to log excessively

adrian.brock Mar 11, 2002 6:24 AM (in response to cmasson)

Don't cross post, you waste people's time.

Regards,
Adrian
Actions
5. Re: New MBean causes JBoss to log excessively

cmasson Mar 11, 2002 2:48 PM (in response to cmasson)

I solved the problem.

I realised that JBoss actually triggers the getter method of all attributes of the MBean at a very early stage of startup (not sure why???). Some of my getter methods lazy initialiazed resources such as TopLink and database connections. That obviously caused an error somewhere which caused JBoss to go into a verbose logging mode.

I have now changed the MBean getters to check whether the Bean has actually been started.
Actions

Go to original post