J2EE Application Servers Logs

Owned by Engineering (Unlicensed)
Last updated: Nov 18, 2015 by Haim Koschitzky
3 min read

Synopsis

The page contains patterns examples of J2EE Application Servers Logs such as WebLogic, WebSphere, Tomcat and JBoss.
Each J2EE application server generates log files containing messages that record all types of events, including startup and shutdown information, errors, warning messages, and access information about HTTP requests.

Examples

Example 1 - WebLogic Server Log Sample: 

####<Jan 23, 2013 9:49:12 AM IDT> <Info> <WebLogicServer> <serverwin> <> <Main Thread> <> <> <> <1184050152371> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R26.4.0-63_CR302700-72606-1.5.0_06-20061127-1108-win-ia32 from BEA Systems, Inc.>

####<Jan 23, 2013 9:49:12 AM IDT> <Info> <Management> <serverwin> <> <Main Thread> <> <> <> <1184050152746> <BEA-141107> <Version: WebLogic Server 10.0  Wed May 9 18:10:27 EDT 2007 933139 >

####<Jan 23, 2013 9:49:15 AM IDT> <Info> <WebLogicServer> <serverwin> <> <Main Thread> <> <> <> <1184050155058> <BEA-000215> <Loaded License : C:\bea\license.bea>

Example 1 - WebLogic Server Log Pattern: 

####<{date:Timestamp,locale=en,MMM dd, yyyy HH:mm:ss a z}> <{priority:Severity,Debug;Info;Warning;Error;Notice;Critical;Alert;Emergency}> <{text:Subsystem}> <{text:Machine Name}> <{text:Server Name}> <{text:Thread ID}> {block,start,emptiness=true}<{block,end,emptiness=true}<{text:User ID}>{block,start,emptiness=true}>{block,end,emptiness=true} <{text:Transaction ID}> <{string:Diagnostic Context ID}> <{string:Raw Time Value}> <{text:Message ID}> {string:Message}

Example 2 - WebLogic Access Log Sample:  

10.0.0.61 - - [9/Jan/2013:09:50:01 +0300] "GET /index.jsp HTTP/1.1" 200 8306

10.0.0.61 - - [9/Jan/2013:09:50:08 +0300] "GET /ootb.css HTTP/1.1" 200 6114

10.0.0.61 - - [9/Jan/2013:09:50:08 +0300] "GET /images/splash_server_90_short.gif HTTP/1.1" 200 10659

Example 2 - WebLogic Access Log Pattern: 

{text:Remote Host,Remote Host} {string:Remote Logical Username} {string:Remote User} [{date:Date,locale=en,dd/MMM/yyyy:HH:mm:ss z}] "{string:Method} {string:URL} {string:Protocol}" {number:Status} {string:Bytes Sent}{eoe}

Example 3 - WebSphere HTTP Error Log Sample: 

[Thu, 05 Jan 2013 06:29:58 GMT] [debug] [10.0.0.39:1853/10.0.0.61:9080] Connection persistence updated to true

[Thu, 05 Jan 2013 06:29:58 GMT] [debug] [10.0.0.39:1853/10.0.0.61:9080] Finished parsing the message

[Thu, 05 Jan 2013 06:29:58 GMT] [debug] [10.0.0.39:1853/10.0.0.61:9080] Connection persistence updated to true

Example 3 - WebSphere HTTP Error Log Pattern:

[{date:Date,locale=en,EEE, dd MMM yyyy HH:mm:ss z}] [{priority:Severity,debug;info;warn;error;crit}] [{string:Remote Host:Port}/{string:Server Host:Port}]{regexp:Remote Host,refIndex=2,(.*):.*}{regexp:Remote Port,refIndex=2,.*:(.*)}{regexp:Server Host,refIndex=3,(.*):.*}{regexp:Server Port,refIndex=3,.*:(.*)} {string:Message}

Example 4 - WebSphere HTTP Access Log Sample: 

10.0.0.39 - - [05/Jan/2013:09:23:18 +0300] "GET /logeye HTTP/1.1" 302 0

10.0.0.39 - - [05/Jan/2013:09:23:18 +0300] "GET /logeye/ HTTP/1.1" 304 0

10.0.0.39 - - [05/Jan/2013:09:23:18 +0300] "GET /logeye/root.html HTTP/1.1" 304 0

Example 4 - WebSphere HTTP Access Log Pattern:

{string:Remote Host} {string:Remote Logical Username} {string:Remote User} [{date:Date,locale=en,dd/MMM/yyyy:HH:mm:ss z}] "{string:Method} {string:URL} {string:Protocol}" {number:Status} {string:Bytes Sent}

Example 5 - WebSphere System Err Log Sample: 

[1/3/13 18:32:42:277 IDT] 00000026 SystemErr     R com.ibm.websphere.management.exception.AdminException: Error getting application documents from master repository.  The application may not be in the repository.
[1/3/13 18:32:42:277 IDT] 00000026 SystemErr     R     at com.ibm.ws.management.application.task.DistributionStatusTask.performTask(DistributionStatusTask.java:75)
[1/3/13 18:32:42:277 IDT] 00000026 SystemErr     R     at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)

Example 5 - WebSphere System Err Log Pattern:

[{date:Date,locale=en,MM/dd/yy HH:mm:ss:SSS z}] {string:Message ID} {string:Source,charsLength=13} {string:Priority} {string:Message}

Example 6 - WebSphere System Out Log Sample: 

[01/15/13 9:18:48:657 IDT] 0000000a  I UOW=null source=com.ibm.ejs.ras.ManagerAdmin org=IBM prod=WebSphere component=Application Server thread=[main]

          TRAS0017I: The startup trace state is *=info.

[01/15/13 9:18:53:672 IDT] 0000000a  I UOW=null source=com.ibm.ejs.ras.ManagerAdmin org=IBM prod=WebSphere component=Application Server thread=[main]

          TRAS0111I: The message IDs that are in use are deprecated

[01/15/13 9:18:53:829 IDT] 0000000a  A UOW=null source=com.ibm.ws.management.AdminInitializer org=IBM prod=WebSphere component=Application Server thread=[main]

          ADMN0015I: The administration service is initialized.

Example 6 - WebSphere System Out Log Pattern:

[{date:Date,locale=en,MM/dd/yy HH:mm:ss:SSS z}] {string:Thread ID,charsLength=9} {string:Event Type} UOW={string:UOW} source={string:Source} org={string:Organization} prod={string:Product} component={string:Component} thread=[{string:Thread}]{string:Message}

Links

Template applying instructions:

  1. Download the templates - WebSphere - Templates, WebLogic - Templates

  2. Import the templates (see Importing a Template)

  3. Apply the templates on multiple logs (see Applying a Template on Multiple Logs)