IBM Support

PK71757; 7.0: Admin thin client on distributed environment does not work in RMI

Download


Abstract

There are multiple problems fixed by this APAR. Description of each follows: a) For users of WebSphere Administrative ThinClient 7.0 on distributed, the client fails to connect to

Download Description

PK71757 resolves the following problem:

ERROR DESCRIPTION:?
Admin thin client on distributed environment does not work for RMI/JSR160RMI with security on.

LOCAL FIX:?

PROBLEM SUMMARY:?

USERS AFFECTED:
All users of IBM® WebSphere® Application Server V7.0

PROBLEM DESCRIPTION:
There are multiple problems fixed by this APAR. Description of each follows:
a) For users of WebSphere Administrative ThinClient 7.0 on distributed, the client fails to connect to the server if security is turned on when using RMI or JSR160RMI connector.

b) A nested business-level application cannot be started as part of its parent business-level application. c) Using wsadmin in local mode (conntype NONE option) and assigning resources to AuthorizationGroup, the addResourcesToAuthorizationGroup command fails with an Exception "Invalid type"

RECOMMENDATION:
None

A summary of each problem follows:
a) When using wsadmin in the thinclient environment to connect to a secured server with RMI connector, it may fail with the error below:
WASX7023E: Error creating "RMI" connection to host "localhost"; exception information:
com.ibm.websphere.management.exception.ConnectorNotAvailableException: javax.naming.NamingException: Error during resolve [Root exception is org.omg.CORBA.UNKNOWN: Unexpected exception found while rethrowing pending exception after processing client-side response interceptor: com/ibm/ws/Transaction/client/NonRecoverableTranManagerSet vmcid: IBM minor code: EA3 completed: Maybe]
b) A business-level application can be added to another (parent) business-level application. When a parent business-level application is started or stopped, all members of the business-level application are started or stopped, including all nested business-level applications that were added to it. The start or stop operations on nested business-level applications fail, yielding a "partially successful" result on the parent start or stop operation. A nested business-level application can be started and stopped directly with successful results, however. The error message depends on whether the operation is executed from wsadmin or the Adminstrative console. The error message displayed in wsadmin for start and stop operations has this general form:
WASX7015E: Exception running command: "$AdminTask startBLA
{-blaID ParentBLA}"; exception information:
com.ibm.wsspi.management.bla.op.OpExecutionException
com.ibm.wsspi.management.bla.op.OpExecutionException
java.lang.NullPointerException:
java.lang.NullPointerException: name cannot be null
The error message displayed in the administrative console for
start operations is:
ParentBLA failed to start.
and the administrative console message for stop operations is:
An error occurred while stopping Parent BLA.
In the above messages, ParentBLA is the BLA being started or stopped.
c) Cannot use addResourcesToAuthorizationGroup command from wsadmin using local mode.
For example: When running the following command

$AdminTask addResourceToAuthorizationGroup {-authorizationGroupName ag1 -resourceName Server=server1}
The following error occurs:
ERROR: Caught Exception:
com.ibm.ws.scripting.ScriptingException:
com.ibm.websphere.management.cmdframework.CommandValidationException
com.ibm.websphere.management.cmdframework.CommandValidationException: Invalid Type. Server

PROBLEM CONCLUSION:?
For each problem:
a) Added the missing classes that need to be in administrative client com.ibm.ws.admin.client_7.0.0.jar.
b) Enabled a nested business-level application to be started and stopped successfully as part of a start or stop operation on its parent business-level application.
c) Changed the code to properly use the resource type validation code that is required to validate resource types in a wsadmin process running in local mode.

The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.1. Please refer to the recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Prerequisites

Please download the UpdateInstaller below to install this fix.

[{"PRLabel":"UpdateInstaller","PRLang":"US English","PRSize":"7250000","PRPlat":{"label":"AIX","code":"PF002"},"PRURL":"http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991"}]

Installation Instructions

Please review the readme.txt for detailed installation instructions.

[{"INLabel":"Readme","INLang":"US English","INSize":"8535","INURL":"ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PK71757/readme.txt"}]

Download Package

Download package
What is Fix Central (FC)?
What is DD?

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
7.0-WS-WAS-IFPK7175709-18-2008US English75042FCFTPDD

On
[{"DNLabel":"7.0-WS-WAS-IFPK71757","DNDate":"09-18-2008","DNLang":"US English","DNSize":"75042","DNPlat":{"label":"AIX","code":"PF002"},"DNURL":null,"DNURL_FTP":null,"DDURL":null}]

Technical Support

Contact IBM Support using SR (http://www-306.ibm.com/software/support/probsub.html), visit the WebSphere Application Server Support Web site (http://www.ibm.com/software/webservers/appserv/was/support/), or contact 1-800-IBM-SERV(U.S. only).

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"System Management\/Repository","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB15","label":"Integration"}}]

Document Information

Modified date:
15 June 2018

UID

swg24020598