PQ70906: WSCP START PROBLEM AFTER APPLYING 02-05-03 SYSMGMT CUMULATIVE EFIX ON WEBSPHERE APPLICATION SERVER VERSION 4.05 PQ71152 | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customers running Websphere Application Server Version 4.0X, and apply system management cumulative efix named "WAS SySMgmt 02-05-2003 4.05-4.04-4.03-4.02 AE Cumm efix", will see the following error when trying to invoke wscp: . [2/7/03 12:29:20:589 EST] 2bab88 ORBRas X com.ibm.CORBA.iiop.Profile JORB00106: In Profile.getIPAddress(), InetAddress.getByName( null ) threw an UnknownHostException P=955715:O=0:CT The following exception was logged java.net.UnknownHostException:Local fix Create a property file that will specify the wscp.Hostname and then use in a property file when starting wscp.sh: . For example, create a file called wscp.ini containing: . wscp.hostName=boomslang.austin.ibm.com . Then, when you start wscp.sh, use the following command line syntax: . wscp.sh -p wscp.iniProblem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users that * * applied the WebSphere System Mgmt. * * cumulative fix: * * * * WAS_Sysmgmt_02-05-2003_4.05-4.04-4.03-4.02_ * * AE_*_cumlative_eFix.jar * **************************************************************** * PROBLEM DESCRIPTION: When wscp is invoked, it fails with: * * UnknownHostException. * **************************************************************** * RECOMMENDATION: * **************************************************************** After applying system management cumulative efix named: WAS_SySMgmt_02-05-2003_4.05-4.04-4.03-4.02_AE_<platform>_ cumulative_eFix.jar customer may see the following error when invoking wscp: 2/7/03 12:29:20:589 EST 2bab88 ORBRas X com.ibm.CORBA.iiop.Profile JORB00106: In Profile.getIPAddress(), InetAddress.getByName( null ) threw an UnknownHostException P=955715:O=0:CT The following exception was logged java.net.UnknownHostException . This was due to a change put in by an internal defect that took out the logic to set the target host to "localhost" if the hostname was not set in a properties file. Result was that target host name is set to null.Problem conclusion Restored logic to set target host to "localhost" if it is not set in a properties file.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ70906
IBM Group: Software Group
Modified date: Mar 14, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.