posted 21 years ago
WebSphere 4 produces an activity log file in c:\%websphere_install_dir%\AppServer\logs\activity .log which traps server/application errors. In the absance of an application debug framework this file can prove extremely useful.
It needs to be formatted using the WebSphere "showlog.bat" utility in c:\%websphere_install_dir%\AppServer\bin.
call showlog d:\ibm\websphere\appserver\logs\activity.log > d:\ibm\websphere\appserver\logs\activity_formatted.
log
Produces error messages like:
ComponentId:
ProcessId: 1548
ThreadId: 615c7735
FunctionName:
ProbeId:
SourceId: com.ibm.ejs.security.registry.ldap.LdapRegistryImpl
Manufacturer: IBM
Product: WebSphere
Version: AE 4.0.4 ptf40230.02
SOMProcessType:
ServerName: server1/Default Server
ClientHostName:
ClientUserId:
TimeStamp: 2002-09-24 14:33:29.672000000
UnitOfWork:
Severity: 1
Category: ERROR
FormatWarning:
PrimaryMessage:
ExtendedMessage: SECJ0153E: Invalid LDAP user ID
RawDataLen: 0