PQ93482: ADMC0053E is issued when starting server with security enabled.

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
Server startup attempts to open a SOAP connection.  If security
is enabled, and a userid/password is not supplied in the
soap.clients.prop file, you will get:
ADMC0053E: Could not create SOAP Connector to connect to host
{0} at
port {1} with SOAP Connector security enabled.

Performance Analyzer code is attempting to open a SOAP
connection to detemine if PMI is enabled.
Local fix
Provided userid/password for SOAP connection in the
soap.clients.prop file.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere 5.0.2 and 5.1 Runtime Performance  *
*                 Advisor users                                *
****************************************************************
* PROBLEM DESCRIPTION: ADMC0053E: Could not create SOAP        *
*                      Connector to connect to host{0} at      *
*                      port {1} with SOAP Connector security   *
*                      enabled.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Runtime Performance Advisor code is making a JMX call
to the nodeagent to find whether PMI is enabled on the
nodeagent. This JMX call makes a SOAP connection and with
security enabled, it will need the userid/password.
Since the userid/password is not supplied in the
SOAP.client.properties file, the connection is not made.
Problem conclusion
If Runtime Performance Advisor(RPA) is not able to make
a SOAP connection to the nodeagent, disable RPA and
issue a warning in the RPA Panel of the Admin Console .
Temporary fix Comments
APAR information
APAR number PQ93482
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-08-30
Closed date 2004-10-22
Last modified date 2005-06-20

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PK07630

Modules/Macros
ADVISOR          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ93482
IBM Group: Software Group
Modified date: Jun 20, 2005