Ok, I will write up my findings in some days. I still want to look into my
original plan first to split up the consolidated server.log into separate
files, based (e.g.) on Thread Context. It's only then that having replaced JUL
with Log4j2 in GlassFish creates a big benefit. But I have to work o
Yes, please write this up :-)
Gary
On Mar 1, 2016 9:54 AM, "Ralph Goers" wrote:
> Actually, if you could either write a blog post on this or some other
> write up I think this would something other users would find very
> interesting. If you don’t have a blog then you should be able to add it t
Actually, if you could either write a blog post on this or some other write up
I think this would something other users would find very interesting. If you
don’t have a blog then you should be able to add it to our wiki.
Ralph
> On Mar 1, 2016, at 9:21 AM, Joachim Kanbach wrote:
>
> I think
I think I've found a solution to this that solves all of my problems: I defined
a RollingFileAppender in each application's separate log4j2.xml configuration
file, all of which point to the same file (server.log) like the log4j2.xml used
by GlassFish. I found from the source code that in this se
I just saw some information in the Log4j documentation that makes me believe
that my solution b) would actually work, particularly if I use a separate
configuration for each application that uses a RollingFileAppender writing to
the same file:
"While RolloverFileAppenders from different Configu
Hi all,
I'm trying to achieve the following setup:
1) Replace the JUL logging used by all Java EE implementations in GlassFish 4.1
with Log4j2
2) Deploy multiple web applications to GlassFish and have both the server log
and all application log(s) be written to the same file (server.log)
The r
