Have you tried running under the debugger with a breakpoint at setFile()?
That should show you the call stack and whether you really got there
through that main. If it was then that main would show up in the list of
processes that are running, although you might not be able to tell how it
was
You are in the correct place. You might also search StackOverflow if you
haven’t already.
We would need some more information on how things are configured and what you
have tried.
I don’t believe any of the committers use WebSphere but we have had other
questions recently.
But identifying
I've followed my application's usage of the `setFile()` command up the
chain of invocations to try to figure out what it's doing so that I can
implement something different for Log4j v2.
Ultimately, the function is invoked by the `main()` method of a file
`SandcastleService.jar`, where it is used
I am new to this user list so my apologies if I am not sending my question
properly...
At any rate, we recently tried to migrate our java application (EARs) running
in WebSphere on a Linux system to
log4j2. Previously we were using an older log4j 1.X version.However,
once we converted
