PQ66574, 4.03, 4.04: In a multinode the plug-in
regen does not complete
Downloadable files
Abstract
WebSphere® Application Server users on 4.0.3 or later when
the plug-in is regenerated in a multinode environment, it does not
complete when one node in the domain is down.
Download 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(Compiled 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(SQLExceptionGenerator.java:269)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:206)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.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:110)
at
com.ibm.ws.dbcheck.util.WriteDBProps.write(WriteDBProps.java:193)
at
com.ibm.ws.dbcheck.util.WriteDBProps.main(WriteDBProps.java:72)
RECOMMENDATION:
Regenerate plug-in does not complete and fails if any node is down in the
multinode environment.
PROBLEM CONCLUSION:
This fix 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 this problem occurs.
These improvements prevent the entire plug-in regen procedure from failing
completely and provide more graceful error handling.
Prerequisites
None
Installation instructions
Please refer to the readme for detailed for installation
instructions.