websphere log files
Shreya Menon
I have a question regarding rotating log files in websphere. My WAS
runs in Windows 2000. our application is running as a huge one and
hence we need to rotate the websphere log files every day at abt 12:00
AM. But we cannot delete the original log file and we are getting
"Process cannot be accessed because it is being used by another
process" in the console.
I read this article
http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/wrapping.html
and looked for the System.out and System.err properties in
logging.properties file. But my logging.properties file doesnt show
these properties.
My was is 4.0.3
Any suggestions or ideas ?
I am pasting the entries in my logging.properties file
#-----------------------------------------------------------------------------
# This file contains Ras properties that are used to enable or disable
# various services or to set service levels.
#
# The default state for each property is indicated, as well as the
valid
# options for that property. The usual rules for java properties files
apply.
# The expected format for an entry is key=value (with no separating
white space).
#-----------------------------------------------------------------------------
#---------------------------------------------------------------------------------
# Activity Log Properties
#
# WARNING Before changing any of the Activity Log properties, all
servers on the physical
# node, including AdminServers must be stopped.
#
# com.ibm.ws.ras.AcvitityLogEnabled : A property used to determine
whether or not the
# servers on this node will write Ras events to the activity log or
not. valid values
# are true and false, with true the default. Turning off this
logging may have serious
# serviceability impacts.
# com.ibm.ws.ras.AcvitityLogName : A property used to determine the
file name of the
# activity log on this node. Either a fully-qualified file name or
a relative file name
# can be specified. If a relative name is specified, the file will
be created in the
# <installl>/logs directory. A legal file name must be specified.
The file name must not
# end in a file separator character, for example, and the file
separator characters must
# be specified in a way the platform recognizes.
# com.ibm.ws.ras.ActivityLogSize : Size of the activity log in
kilobytes. The default value
# is 1024 which yields a log size of 1 megabyte. See the Problem
Determination guide for
# guidelines on setting the size of this log.
#---------------------------------------------------------------------------------
com.ibm.ws.ras.ActivityLogEnabled=true
com.ibm.ws.ras.ActivityLogName=activity.log
com.ibm.ws.ras.ActivityLogSize=1024
#---------------------------------------------------------------------------------
# Correlation Id property
#
# The following property is retrieved once for the life of a process
at startup. It
# can be changed in this file at any time, but in order for the change
to take effect
# on started processes, they must be restarted.
#
# com.ibm.ws.ras.UnitOfWork : A property that determines whether
messages and diagnostic
# trace entries will be flagged with a correlator. The intent of
the id is to allow
# correlation of events that occur in different processes as being
related to or caused
# by a single client request. Valid values are true and false. The
default value is true.
#---------------------------------------------------------------------------------
com.ibm.ws.ras.UnitOfWork=true
#---------------------------------------------------------------------------------
# Serious Event Forwarding property
#
# The following property is retrieved once for the life of a process
at startup. It
# can be changed in this file at any time, but in order for the change
to take effect
# on started processes, they must be restarted.
#
# com.ibm.ws.ras.SeriousEventEnable : A property that determines
whether Ras messages are
# forwarded to the central repository (Admin Database). Valid
values are true and false.
# The default value is true.
#---------------------------------------------------------------------------------
com.ibm.ws.ras.SeriousEventEnable=true
#---------------------------------------------------------------------------------
# Ras Message Filter level property
#
# The following property is retrieved once for the life of a process
at startup. It
# can be changed in this file at any time, but in order for the change
to take effect
# on started processes, they must be restarted.
#
# com.ibm.ws.ras.MessageFilterLevel : A property that determines which
levels of Ras
# messages are logged and which are not. Valid values are :
# - error : only messages of severity error are logged.
# - warning : only messages of severity error or warning are
logged.
# - audit : all messages are logged.
# The default value is audit.
#---------------------------------------------------------------------------------
com.ibm.ws.ras.MessageFilterLevel=audit
#---------------------------------------------------------------------------------
# Trace Format property
#
# The following property can be changed at any time. Whether or not
the effect is
# immediate or delayed until the next process restart is dependent
upon the
# facility.
#
# com.ibm.ws.ras.TraceFormat : A property that determines how trace
output is formatted.
# Valid values are :
# - basic : generates the sparse legacy trace format.
# - advanced : a more verbose style patterned after the basic
format. Recommended
# - in most cases.
# - loganalyzer : generate a trace output that can be parsed by
the Log Analyzer
# tool. Generates larger trace files than the other options.
Recommended when
# doing cross-process trace.
# The default value is basic
#---------------------------------------------------------------------------------
com.ibm.ws.ras.TraceFormat=basic
Please help
Thanks
JFenner
> Hi all,
> I have a question regarding rotating log files in websphere. My WAS
> runs in Windows 2000. our application is running as a huge one and
> hence we need to rotate the websphere log files every day at abt 12:00
> AM. But we cannot delete the original log file and we are getting
> "Process cannot be accessed because it is being used by another
> process" in the console.
>
> I read this article
> http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/wrapping.html
>
> and looked for the System.out and System.err properties in
> logging.properties file. But my logging.properties file doesnt show
> these properties.
>
> My was is 4.0.3
I run WAS on Solaris and have a script that runs some wscp commands.
You could do the same thing using Windows Scheduler.
WSCP allows you to run WAS commands from command line. My cron job
will stop WAS, move the log file to an archive location, and then
restart WAS. You can even get the full pathname for the Stdout and
Stderr logs from WSCP.
Hope this helps...
> Any suggestions or ideas ?
>
> <snipped>