[jboss-user] [JCA/JBoss] - Re: ManagedConnectionFactory.setLogger

[iit]

"adrian at jboss.org" wrote : 
  | i.e. There will be no logging unless the appserver associates an output stream
  | with MCF. If or how it does it is entirely down to it.
  | 
  | Since JBoss uses log4j and always associates a writer you can control
  | it using the log4j config.
  | 
  | Since JBoss is Open Source you change those rules, if you don't like it.
  | It's called a feature.
  | 
  | I fail to see how you can argue with a straight face that overridding a policy decision
  | can possibly be a bug?

You don't want understand, right? 

To recap (from the javadoc): If you set a log writer, logging and tracing is ON! It doesn't matter if that is a null stream or not, because the MCF  creates a huge debug/trace output. 

To use a RA with debug/trace enabled in a high-load scenario in production is not appropriate. In our case it's not usable. 

That is a bug. 

But anyway, bug or not, it doesn't work and that's what matters.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123568#4123568

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123568