PQ96242: SSL TRAFFIC LOGGED INTO WRONG LOG | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description ssl traffic is not going into the ssl logs it is going into the regular https logs. There is access log and there is access ssl log and it is going back and forth between the two. It is not logging to the correct log file.Local fix No work around.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users that use * * HTTP Transport Access and Error Logging * **************************************************************** * PROBLEM DESCRIPTION: Could not generate HTTP Transport * * Access and Error Logging Per Transport * **************************************************************** * RECOMMENDATION: * **************************************************************** Changed code to allow Access and Error logging Per TransportProblem conclusion One can generate Access and Error Log Per TransportTemporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ94233 APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ96242
IBM Group: Software Group
Modified date: Oct 26, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.