PQ78179: RMI exceptions with XMLConfig

 A fix is available

PQ78179; 4.0.6: RMI exception with Concurrent EAR installs through XMLConfig



APAR status
Closed as program error.

Error description
Problem:
Recently we upgraded from WebSphere 4.0.4 to WebSphere 4.0.5
with a new JDK from IBM (J2RE 1.3.1 IBM AIX build
ca131w-20030425) to address a JVM restarting issue.  Since the
upgrade we have been experiencing a problem performing imports
via XMLConfig and the admin console.  Under WAS 4.0.4 we were
able to run multiple concurrent instances of XMLConfig to
install multiple EAR files at the same time.  For instance, we
have a script that spawns 8 XMLConfig processes from the command
line with different EAR files on the local machine to install
them all at once. With the new upgrades we are now receiving the
following errors:

[5/18/03 23:46:09:713 GMT+00:00] 7629d0ba ExceptionUtil X
CNTR0020E:
Non-application exception occurred while processing method
duplicateContextRootCheck on bean
BeanId(admin#repository.jar#Node,
1053122438613): java.rmi.RemoteException: ADMR2326E: An error
occurred obtaining Module or Virtual Host attributes.; nested
exception is:
com.ibm.ejs.sm.exception.RemoteOpException: ADMR4354E: Fail to
request the application server name
com.ibm.ejs.sm.exception.RemoteOpException: ADMR4354E: Fail to
request the application server name





In fact, we are now able to only install one EAR file at a time.

Toubleshooting:
Here are the steps we have taken so far to try and troubleshoot
the
issue:
1.  We tried migrating 8, 4, 2 and 1 EAR files at a time.  The
only successful test was with 1 EAR a time.
2.  We backed out the new JDK and tried running the migrations
with just FP5 installed.  This also failed when running multiple
concurrent XMLConfig processes.  One EAR at a time did work.
3.  Thinking we had a possible DB problem we dropped and created
a new
Admin Repository DB.  Then we let WebSphere recreate and
populate the tables.  The problem still existed after running
against the new DB. This exposed a new problem though.  I ran a
full export via the console and produced an XML file on my local
machine.  Then I attempted to        import that same XML file
via the console and received this error:

Exception:
java.lang.NullPointerException
at
com.ibm.websphere.xmlconfig.VirtualHostConfig.locate(VirtualHost
Config.j
ava:111)
at
com.ibm.websphere.xmlconfig.VirtualHostConfig.importXML(VirtualH
ostConfi
g.java:156)
at
com.ibm.websphere.xmlconfig.XMLConfig.importDOM(XMLConfig.java:1
046)
at
com.ibm.websphere.xmlconfig.XMLConfig.importFromFile(XMLConfig.j
ava:1001
)
at
com.ibm.ejs.sm.client.command.ImportCommand.execute(ImportComman
d.java:7
0)
at
com.ibm.ejs.sm.client.command.CommandManager$ExecutionThread.run
(Command
Manager.java:264)
at
com.ibm.ejs.sm.client.command.ThreadPool$PooledThread.run(Thread
Pool.jav
a:89)
--------
com.ibm.ejs.sm.client.command.ExecutionException: Error during
import
at
com.ibm.ejs.sm.client.command.ImportCommand.execute(ImportComman
d.java:7
4)
at
com.ibm.ejs.sm.client.command.CommandManager$ExecutionThread.run
(Command
Manager.java:264)
at
com.ibm.ejs.sm.client.command.ThreadPool$PooledThread.run(Thread
Pool.jav
a:89)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users using     *
*                 XMLConfig to install concurrent EARs.        *
****************************************************************
* PROBLEM DESCRIPTION: When concurrent EAR installs are        *
*                      executed the users get a                *
*                      RemoteException.                        *
****************************************************************
* RECOMMENDATION: Apply this fix if one is performing          *
*                 concurrent EAR installs using XMLConfig.     *
****************************************************************
This problem surfaces when one is performing concurrent EAR
installs through the XMLConfig admin interface.  The user
will see on the XMConfig stdout a Non-Application error
ocurred message.
Problem conclusion
Traced the code in the EnterpriseAppBean.java.  Turns out
resetting the beanObj to null cured the symptom.
Temporary fix
This shouldbe the final fix.  However, would like customer
testing.
Comments
Fix uploaded to 
pq99999.  Expecting feedback by Oct 24.
APAR information
APAR number PQ78179
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-09-06
Closed date 2003-10-23
Last modified date 2003-10-23

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
SM          

SRLS

Fix information

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 #: PQ78179
IBM Group: Software Group
Modified date: Oct 23, 2003