PQ79305: THE "OSE SPECIFICATION VIOLATION!!!" ERROR MESSAGE IS LOGGED IN IPLANET 4.1 ERROR LOG.


APAR

APAR status
Closed as program error.

Error description
Customer reported this error message in iPlanet 4.1 with
WebSphere 3.5.4 plugin on Solaris 8:
[01/Oct/2003:09:21:22] failure (27972): [was error] reports:WebSphere 3.5.4 plugin on Solaris 8:[01/Oct/2003:09:21:22], failure (27972): [was error]
OSE specification violation!!! ns_prepare_for_write() was alread called [01/Oct/2003:09:21:22] failure (27972): [was error] reports:reports:OSE specification violation!!! ns_prepare_for_write() was alreadcalled[01/Oct/2003:09:21:22], failure (27972): [was error]
Exitting ns_prepare_for_write_cb with failure . Despite of this error iPlanet plugin for WebSphere 3.5.4 seems working fine.
reports:Exitting ns_prepare_for_write_cb with failure.Despite of this error iPlanet plugin for WebSphere 3.5.4 seemsworking fine.
Local fix
Not available, it looks like a cosmetic problem, but I am not
sure at this time.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere 3.5 plugin users running iPlanet   *
****************************************************************
* PROBLEM DESCRIPTION: "OSE specification violation" error     *
*                      message logged.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The error checking code that logs that error message assumed
that the application server would never allow headers to
be set twice, and that if it did, it was a sign of a defect
in the application server.  It ends up that this isn't
true in the face of error pages that will try to set the
headers after the application that triggered the error page
had already set them.
Problem conclusion
The actual handling code for this condition was correct
for the iPlanet plugin, so all that needed to be changed
was the logging level of the "OSE specification violation" -
it will no longer be logged as an error, and will only appear
if TRACE logging is enabled.
Temporary fix
Comments
APAR information
APAR numberPQ79305
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2003-10-07
Closed date2004-02-09
Last modified date2004-02-09

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
plugin
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Applicat, ion & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ79305
IBM Group: Software Group
Modified date: 2004-02-09