PQ42102: WEBSPHERE 3.5 ADMINSERVER FAILS WITH STALECONNECTIONEXCEPTION


APAR

APAR status
Closed as documentation error.

Error description
.
**Note** This is a documentation apar; code apar PQ42775 has
been cancelled, as this is not a Websphere code defect. If a
permanent code change is made it will most likely be in DB2,
Java, or some combination of the two.
.
After installing Websphere App Server 3.5 with DB2, the
adminserver starts the first time, but fails upon subsequent
start attempts. Even after dropping and recreating repository
database.
Error messages in tracefile show:
 00.09.18 17:11:01:128 MST  a41a45c8 DBMgr         W Exception o
n database query (find all):Error messages in tracefile show:00.09.18 17:11:01:128 MST  a41a45c8 DBMgr         W Exception o
00.09.18 17:11:01:374 MST a41a45c8 AdminServer F Encountered an exception java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:n database query (find all):00.09.18 17:11:01:374 MST a41a45c8 AdminServer F Encounteredan exception java.rmi.ServerException: RemoteException occurred
java.rmi.RemoteException: Database select failed to find all instances of VirtualHost.; nested exception is:in server thread; nested exception is:java.rmi.RemoteException: Database select failed to find all
com.ibm.ejs.cm.portability.StaleConnectionExceptionjava.rmi.Remo teException: Database select failed to find all instances of VirtualHost.; nested exception is:instances of VirtualHost.; nested exception is:com.ibm.ejs.cm.portability.StaleConnectionExceptionjava.rmi.RemoteException: Database select failed to find all instances of
com.ibm.ejs.cm.portability.StaleConnectionExceptioncom.ibm.ejs.c m.portability.StaleConnectionException at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:254)
VirtualHost.; nested exception is:com.ibm.ejs.cm.portability.StaleConnectionExceptioncom.ibm.ejs.cm.portability.StaleConnectionExceptionat java.lang.Class.newInstance0(Native Method)at java.lang.Class.newInstance(Class.java:254)
Local fix
Our Websphere Application Server 3.5
documentation states that we need to set
EXTSHM=ON, which is also stated
as 'never to be set' when using db2/udb by the DB2/UDB
support group in the following
http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/
winos2unix/support/document.d2w/report?&fn=DWEB-4MKHBD
.
The Websphere documentation is incorrect; EXTSHM should not be
set, as this causes problems with DB2 on AIX.
-------
This is a new environment setting for Websphere 3.5x.
------------------
DB2 support recommends using TCP/IP
loopback, instead of setting EXTSHM=ON, for a
workaround to this problem. Details on configuring
TCP/IP loopback can be found below.
------------------
Additional Symptom: SQL1224N when starting websphere as too
      many processes attempt to access db2 shared segment
Problem summary
DB2 AIX Database Configuration Must: How to
configure a database to look like a remote database when it's
on the local machine.
To set up DB2 as a client to a remote database.
On the machine with the database that you want to connect to:
1. Configure the database manager to use TCP/IP on AIX:On the machine with the database that you want to connect to:
On the server machine, log in as the DB2 instance owner. Set DB2COMM to TPC/IP, e.g., db2set DB2COMM=tcpip 2. Edit /etc/services file to include DB2 connection and interrupt service ports if they do not already exist, e.g., server1 3700/tcp # DB2 connection service port server1i 3701/tcp # DB2 interrupt connection # service port 3. Update the database manager configuration, e.g., db2 update dbm cfg using svcename server1 the arguement after svcename must match the name of the service that you placed in /etc/services. 4. start and stop db2 % db2stop % db2start The following instructions allow you to connect to your local machine as though it was a remote client. On the client machine:1. Configure the database manager to use TCP/IP on AIX:On the server machine, log in as the DB2 instance owner.Set DB2COMM to TPC/IP, e.g.,db2set DB2COMM=tcpip2. Edit /etc/services file to include DB2 connection andinterrupt service ports if they do not already exist, e.g.,server1 3700/tcp # DB2 connection service portserver1i 3701/tcp # DB2 interrupt connection# service port3. Update the database manager configuration, e.g.,db2 update dbm cfg using svcename server1the arguement after svcename must match the name of theservice that you placed in /etc/services.4. start and stop db2% db2stop% db2startThe following instructions allow you to connect to your localmachine as though it was a remote client.
1. Catalog the node, e.g., db2 catalog tcpip node <NodeName> remote <hostname> server server1 Note: the server name must match the name of the DB2 connection port service which you specified in /etc/services. To verify that the catalog command worked properly, you may issue the following command:On the client machine:1. Catalog the node, e.g., db2 catalog tcpip node, remoteserverserver1Note: the server name must match the name of the DB2 connectionport service which you specified in /etc/services.To verify that the catalog command worked properly, you may
db2 list node directory 2. Catalog the database as follows:issue the following command:db2 list node directory
a. db2 catalog db <database name> as <database alias> b. db2 uncatalog db <database name> c. db2 catalog db <database alias> as <database name> at node <nodename> (this part of the workaround will prevent the SQL1334N error that can occur when the database name is the same as the database alias) 3. Stop and start DB2. % db2stop % db2start Now, you can start your admin server. DB2 does not support EXTSHM on AIX due to an AIX restriction.
2. Catalog the database as follows: a. db2 catalog db, as, b. db2 uncatalog db, c. db2 catalog db, as, at node(this part of the workaround will prevent the SQL1334N errorthat can occur when the database name is the same as thedatabase alias)3. Stop and start DB2.% db2stop% db2startNow, you can start your admin server.DB2 does not support EXTSHM on AIX due to an AIX restriction.
Problem conclusion
Closing doc.
Temporary fix
Comments
APAR information
APAR numberPQ42102
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED DOC
PENoPE
HIPERNoHIPER
Submitted date2000-09-29
Closed date2000-10-06
Last modified date2001-04-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

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

Applicable component levels











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ42102
IBM Group: Software Group
Modified date: 2001-04-09