PQ56700: AFTER PQ43906 , EVENT MESSAGES ARE NOT BEING STORED IN THE SE_TABLE OF THE WEBSPHERE APP SERVER DATABASE


APAR

APAR status
Closed as program error.

Error description
Event messages are not stored in the SE_TABLE of the WebSphere
Application Server database.  For example, when an application
server is started or stopped, messages should appear in the
WebSphere Administrator's Console, viewed via the Event Viewer
or using SQL against the SE_TABLE.  If they are not being
stored in the database, they can not be retrieved by the Tivoli
Manager for WebSphere Application Server nor forwarded to the
Tivoli Enterprise Console.
.
Through WebSphere, there are 3 ways to determine if serious
events is broken in WAS 3.5.5.
.
1. Admin console.  When stopping and starting an application
   server, you should see messages in the console window
   indicating the application server has been stopped, and
   then at least 3 messages indicating it has started.
.
2. Admin console.  Using the event viewer, you should be able
   to browse and see new messages when stopping and starting an
   application server.
.
3. Database, table SE_TABLE.  The count of this table should
   increase when a stop/start of an application server has
   occured.  To know the count, you could use the following
   command:
.
   select count(*) from ejsadmin.se_table.
command:.select count(*) from ejsadmin.se_table.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of the    *
*                 Serious Event Logger in PTF 3.5.5.           *
****************************************************************
* PROBLEM DESCRIPTION: Due to changes in PQ43906, no entries   *
*                      were being put in the serious event     *
*                      table.  This results in numerous        *
*                      exceptions from the serious event       *
*                      logger and presented problems to        *
*                      users of this functionality.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Code changes in the above mentioned APAR resulted in no
messages being logged to the serious event table.  This
was a problem to code in the Admin Server and to application
code that relied on that table.
Problem conclusion
The code changes were backed out and events are now being
logged to the serious event table as expected.
Temporary fix
Comments
APAR information
APAR numberPQ56700
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-01-15
Closed date2002-01-30
Last modified date2002-01-30

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
ADMINSVR
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ56700
IBM Group: Software Group
Modified date: 2002-01-30