Vendors / Apache Software Foundation / Apache HTTP Server / WebSphere Plugin Error Log

Event type

WebSphere Plugin Error Log

Application server connection and failover errors

IBM WebSphere Application Server Plugin for Apache error logs recording connection failures, server failover events, transport errors, and application server communication issues

PLAIN TEXT 11 fields Low Generator

websphere plugin application-server failover connection-error

Preview Sample View Schema

CLI Install

meltr templates install apache

Overview

What this event covers

Records errors and warnings from the IBM WebSphere Application Server Plugin for Apache HTTP Server. Logs connection failures to application servers, server failover events, transport errors, SSL handshake failures, session affinity issues, and retry attempts.

When generated

›Failed connection attempts to WebSphere application servers
›Application server marked as down during health checks
›Transport stream read timeouts or connection refused errors
›SSL/TLS handshake failures with backend servers
›Server failover events when primary server is unavailable
›IOR (Interoperable Object Reference) file access errors
›Session affinity routing failures
›Maximum retry limits reached for server groups

Security relevance

High

Compliance

PCI DSS (Requirement 10.2 - System component failures) ISO 27001 (A.12.4.1 - Event logging) NIST SP 800-53 (AU-2, AU-3, SI-4 - System monitoring) SOX (System availability monitoring)

Frequency notes

Low-frequency events under normal conditions (12-13 events/hour during business hours, 3 events/hour nights, 2 events/hour weekends). Frequency increases significantly during application server outages, network issues, or deployment activities. Healthy environments see minimal plugin errors.

Resources

Docs and tools

IBM WebSphere Plugin Documentation official WebSphere Plugin Troubleshooting official WebSphere Plugin Configuration Guide official WebSphere Error Messages reference WebSphere Plugin Analyzer IBM tool for analyzing WebSphere plugin logs and configurations Splunk App for WebSphere Splunk application for monitoring and analyzing WebSphere logs IBM Support Assistant Diagnostic tool for WebSphere Application Server issues

Generation

Configuration

Base frequency: 5 events/hour
Time patterns: business_hours night_hours weekend
Business hours: 2.5x
Night hours: 0.6x
Weekend: 0.4x

Schema

Field definitions

Field reference for this event type — types, requirements, examples, and allowed values.

timestamp

DateTime Required

Date and time when the plugin error occurred, with microseconds

Source: now() | format_datetime('%d/%b/%Y:%H:%M:%S.%f')

Format DD/Mon/YYYY:HH:MM:SS.microseconds

Example 20/Dec/2025:15:31:09.53371

request_id

String Required

Hexadecimal request identifier for correlation

Source: random_hex(10000000, 99999999)

Format 8-digit hexadecimal

Example 0001da25

thread_id

String Required

Hexadecimal thread identifier

Source: random_hex(10000000, 99999999)

Format 8-digit hexadecimal

Example a7af5700

log_level

String Required

Severity level of the plugin log entry

Source: random_choice(['ERROR', 'WARN', 'INFO', 'DEBUG'])

Format Log level

Example ERROR

Values

ERROR Error condition requiring attention
WARN Warning condition, non-fatal
INFO Informational message
DEBUG Debug-level diagnostic information

component

String Required

WebSphere plugin component that generated the log entry

Source: Embedded in error message

Format Component name

Example ws_common

Values

ws_common Common plugin utilities and request handling
ws_server Server connection and failover management
ws_transport Transport layer and stream handling
ws_config Configuration management

function

String Required

Function or method within the component where the error occurred

Source: Embedded in error message

Format Function name

Example websphereHandleRequest

error_message

String Required

Detailed error message describing the plugin issue

Source: random_choice of realistic WebSphere plugin error messages

Format Free text

Example Failed to execute the transaction to 'lpdscwasapp01Node_BOH_1' on host 'lpdscwasapp01.mclaneco.com:9450'

server_name

String Optional

WebSphere application server name involved in the error

Source: registry.get_random_device().hostname

Format Server identifier

Example lpdscwasapp01Node_BOH_1

server_host

String Optional

Hostname or FQDN of the WebSphere application server

Source: registry.get_random_device().fqdn

Format Hostname or FQDN

Example lpdscwasapp01.mclaneco.com

server_port

Integer Optional

Port number of the WebSphere application server

Source: random_choice([9080, 9443, 9081, 9082])

Format Port number

Example 9450

error_code

Integer Optional

OS-level error code (errno) when applicable

Source: random_int(104, 111) for connection errors

Format Error number

Example 104