Thanks Christoph, like i mentioned before we don't want to carry more
bridges into logging. I'm not against moving towards log4j2 and i already
changed my entire code base to use log4j2 as a part of struts2 upgrade but
the problem here is application server support, we are using latest version
Wildfly available (10.0.0 GA) so our options are at the extreme.

Thanks Lukasz for pointing out that blog link, which i have already tried
and that doesn't work give the desired log output as i mentioned before all
logs from application is getting written into file as well as console as
INFO [stdout]


On Tue, Jul 19, 2016 at 3:31 PM, Lukasz Lenart <lukaszlen...@apache.org>
wrote:

> 2016-07-19 10:55 GMT+02:00 Sreekanth S. Nair <
> sreekanth.n...@egovernments.org>:
> > Hi Christoph,
> >                        Thanks for your detailed explanation, even though
> > its a huge change for application to move from both slf4j and log4j1 to
> > Log4j2, lets assume we moved all to Log4j2 but if the underlying
> > application server eg: Jboss or wildfly have its own wrapper
> implementation
> > for their logging with log4j1, which will print application generated log
> > using stdout (This is what we have noticed after struts2 upgrade). Lets
> > assume we turned off logging subsystem from Jboss and used Log4js
> >  log4j2.xml which gives less flexibility (changing threshold on the fly)
> > wrt logging in different environment when we compare to jboss one.
> >
> > These all are our concern, we really doubt upgrading struts2, if log is
> > directing to stdout. Please let us know if anyone have any thought
> > regarding this or anyone successfully upgraded without stdout logging in
> > Wildfly or Jboss 6.
>
> As far I know/understand JBoss is using repackaged version of SLF4J
> and it should be manner of configuration to allow both logging
> frameworks to cooperate
> http://blog.c2b2.co.uk/2014/09/alternative-logging-frameworks-for.html
>
>
> Regards
> --
> Ɓukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>

Reply via email to