-
15. Re: ManagedConnectionFactory.setLogger
"iit" wrote:
You don't want understand, right?
No, I understand perfectly. You're MCF does lots of work when it is configured
with a log writer (even if the stream is effectively > dev/null).
Rather than "fix" your MCF to log more scalably/performantly,
you want us to be able to not configure a log writer but we don't have that configuration.
You don't want to spend the time providing a patch to make this possible
and you don't want to wait for somebody else to do it,
so instead you claim the lack of this configuration is a bug.
You probably want it to be CRITICAL as well so it goes in the next release? :-)
I think that's a pretty fair summary of where we disagree. -
16. Re: ManagedConnectionFactory.setLogger
Rather than "fix" your MCF to log more scalably/performantly,
So we should optimize our debug output because JBoss is so dumb to set a logger which implicitly turns debug/trace on?you want us to be able to not configure a log writer but we don't have that configuration.
Right, you don't have it and I don't care even if you would come over here and make the fix.
Bye, bye. -
17. Re: ManagedConnectionFactory.setLogger
Adrian had already given you the details , I have raised a JIRA which will cater to the requirement the way you want it .
Rathar than complaining and wasting time here you could have raised a JIRA for it :(
http://jira.jboss.com/jira/browse/JBAS-5174
In case you change your mind do vote JIRA .