server logs explanation about biemond-orawls HOT 10 CLOSED

I ended up using the following (to get two output files):

arguments:

• "-Dweblogic.Stdout=/logs/%{::domain}/weblogic/%{::appname}-s1.log"
• "-Dweblogic.Stderr=/logs/%{::domain}/weblogic/%{::appname}-s1.out"

logfilename: "/logs/%{::domain}/weblogic/%{::appname}-s1.log"

For instance, the logfilename parameter and the stdout JVM define both point to the same log file.

from biemond-orawls.

The 2 server java arguments are used by the nodemanager when it startups up the managed server, re-direct outlog and how the nodemanager starts the server.

The other are for the managed server, domain, http ,datasource log etc. with rotation and size
Don't think you used re-use the log files because of locking or performance.

from biemond-orawls.

Interesting, I know my customer has specifically requested two output log files (one for stdout and one for stderr) as described above. But, I see your point on the performance...

from biemond-orawls.

Yeah, I just tested this, and I don't see some of my applications output that is being sent to STDOUT, maybe this is due to what you were saying?

from biemond-orawls.

In the weblogic console you can try on the advanced log options of a managed server to enable redirect stdout to server log

from biemond-orawls.

My coworker says this option:
http://docs.oracle.com/cd/E17904_01/web.1111/e13739/config_logs.htm#WLLOG163

-Dweblogic.log.RedirectStdoutToServerLogEnabled=true

from biemond-orawls.

indeed that does the same.

is the application using a Logger or doing System.out

from biemond-orawls.

We just wrote a quick test app to write to stdout and stderr. He just used a System.out and System.err. Does it make a difference?

from biemond-orawls.

I think with a logger, default every under warning is ignored . So when you log a warning or an error you should see it. system out only when you set weblogic.log.RedirectStdoutToServerLogEnabled=true you can see this output in the normal log but It should be there in the nodemanager log, off course when you use the nodemanager to start the managed server.

from biemond-orawls.

So, I added the RedirectStdoutToServerLogEnabled for both my WL 10 and 12 offerings. This seems to have allowed the output to route to where it should go.

from biemond-orawls.