02-03-06 12:48 PM
Hi,
I'm having problems to start the WLS service after I added the -log
option as described in official BEA Documentation "Administration
Guide"
When I start the service I get a windows message error. Removing the
-log entry from the regisitry solves the problem.
I need to have std out and std err in a file starting WLS as
service....does anybody got the same issue before ?
Thanks and kind regards.
Paolo
Redirecting Standard Out and Standard Error to a File
By default, when you install a WebLogic Server instance as a Windows
service, you cannot see the messages that the server or its JVM print
to standard out and standard error.
To view these messages, you must redirect standard out and standard
error to a file:
1. Create a backup copy of the WL_HOME\server\bin\installSvc.cmd
master script.
2. In a text editor, open the WL_HOME\server\bin\installSvc.cmd
master script.
3. In installSvc.cmd, the last command in the script invokes the
beasvc utility. At the end of the beasvc command, append the following
command option:
-log:"pathname "
where pathname is a fully qualified path and filename of the file
that you want to store the server's standard out and standard error
messages.
The modified beasvc command will resemble the following command:
"%WL_HOME%\server\bin\beasvc" -install
-svcname:"%DOMAIN_NAME%_%SERVER_NAME%"
-javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%"
-extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%"
-cmdline:%CMDLINE%
-log:" d:\bea\user_projects\myWLSdomain\myWLSse
rver-stdout.txt
4. By default, every 24 hours the Windows service archives messages
to a file named pathname-yyyy_mm_dd-hh_mm_ss. New messages collect in
the file that you specified in the previous step.
After you install the service and restart the Windows host, to view the
messages that the server writes to standard out or standard error, do
one of the following:
* Make a copy of the file that you specified and view the copy. The
Windows file system cannot write to files that are currently opened.
* To view the messages as they are being printed to the file, open
a command prompt and use the DOS command tail -f stdout-filename.
[ Post a follow-up to this message ]
|