PQ66574: IN A MULTINODE ENVIRONMENT THE PLUG-IN REGEN DOES NOT COMPLETE WHEN ANY SINGLE NODE IS DOWN.

 Fixes are available

PQ66574, 4.03, 4.04: In a multinode the plug-in regen does not complete
4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Problem: After PTF 3 was applied, the nanny.trace file
contained multiple instaces of the message "NMSV0602E: Naming
Service unavailable. A communications error occurred." and when
any one node is down, unable to successfully regen the plug-in.

PQ61462 did not affect the situation.
.
Error in the nanny's file:
[5/14/02 14:53:17:370 CDT]     f4cb Nanny         E error
getting
nodeHome for : ejsadmin/homes/NodeHome :
java.lang.NullPointerException
[5/14/02 14:53:18:387 CDT]     f4cb WsnInitCtxFac W NMSV0602E:
Naming Service unavailable. A communications error
occurred.
[5/14/02 14:53:18:388 CDT]     f4cb Nanny         W SMTL0012W:
Waiting for initial context javax.naming.CommunicationException:
Caught CORBA.COMM_FAILURE when resolving initial
reference=WsnNameService. Root exception is
org.omg.CORBA.COMM_FAILURE:   minor code: 3
completed: No
.
Error in the XML Export:
ExceptionUtil X CNTR0019E: Non-application exception occurred
while processing method findAll:
InvalidBeanOStateException(current
= DESTROYED, expected = POOLED)
 at
com.ibm.ejs.container.EJSHome.getFinderBeanO(EJSHome.java(Compil
ed
Code))
.
ExceptionUtil X CNTR0020E: Non-application exception occurred
while processing method listInstances on bean
BeanId(admin#repository.jar#ClientAccess, null):
java.rmi.RemoteException: ; nested exception is:
 javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:
 org.omg.CORBA.TRANSACTION_ROLLEDBACK:
com.ibm.websphere.csi.CSITransactionRolledbackException: null;
nested exception is:
 InvalidBeanOStateException(current = DESTROYED, expected =
POOLED)
.
and the plug-in trace shows:
.
[7/22/02 17:27:41:080 CDT]  40405c3 AEPluginCfg   W PLGN0063W:
An exception occurred while generating the plugin configuration
for module default_app. The plugin configuration file will not
contain an entry for this module.
.
and the dbcheckprop.sh generates:
.
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000]
SQL0204N
"WAS40.TYPE_TABLE" is an undefined name.  SQLSTATE=42704
        at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQ
LExcepti
onGenerator.java:269)
        at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQ
LExcepti
onGenerator.java:206)
        at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQL
Exceptio
nGenerator.java:457)
        at
COM.ibm.db2.jdbc.app.DB2Statement.execute2(DB2Statement.java:617
)
        at
COM.ibm.db2.jdbc.app.DB2Statement.executeQuery(DB2Statement.java
:434)
        at
com.ibm.ws.dbcheck.util.WriteDBProps.readDb(WriteDBProps.java:11
0)
        at
com.ibm.ws.dbcheck.util.WriteDBProps.write(WriteDBProps.java:193
)
        at
com.ibm.ws.dbcheck.util.WriteDBProps.main(WriteDBProps.java:72)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users on 4.0.3  *
*                 or later who regenerate the plugin           *
*                 configuration in multinode environment       *
****************************************************************
* PROBLEM DESCRIPTION: On WAS 4.0.x, regenerate plugin         *
*                      failures occurs in multinode            *
*                      environment                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Regenerate plugin does not complete and fails if any node is
down in the multinode environment
Problem conclusion
This eFix is a cross-component fix between System Management
and Engine to improve code logic to detect and skip a node if
it is down and also properly handle the exceptions when such
problem occurs.
These improvements prevent the entire plugin regen procedure
from failing completely and provide more graceful error
handling for the user.
Temporary fix Comments
APAR information
APAR number PQ66574
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-09-25
Closed date 2002-10-03
Last modified date 2002-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ66574
IBM Group: Software Group
Modified date: Oct 3, 2002