PQ60843: CANNOT USE THE NODENAME PROPERTY. EAR WILL NOT EXPAND PROPERLY | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer explanation of the problem is as follows: For configuring WAS on a machine with multiple NIC's, I add the following line to the admin.config file: com.ibm.ejs.sm.adminServer.nodeName=mydevnode I start WAS for the first time, and open the admin console. Everything looks fine, the node name is dev203e However, when I install an Enterprise Application the files do notget installed into /usr/WebSphere/AppServer/installedApps. I stopped WAS, dropped the admin database, and removed the extra line from the admin.config. I changed initial.config and createTables in admin.config. Started WAS and opened the admin console. I installed the same application, and it worked correctly, expanding the .ear to the local disk. I repeated this cycle from the beginning, and it seems that when the nodeName is set manually, Enterprise Applications do not expand to the /usr/WebSphere/AppServer/installedApps directory on the local machine. Is this expected? I need to use the nodeName property. Original PMR 52994,370,000. PMR 70824,370,000 is a continuation of PMR 52994,370,000.Local fix Customer is using a testfix, newtest.jar provided by L3 as a temporary fix until the APAR can be provided. newtest.jar located in wasdoc0/pmrs/70824370000/05,03,02_testfixProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.02 users * * with multiple network interface cards in * * their system(s). * **************************************************************** * PROBLEM DESCRIPTION: When user has multiple network * * interface cards in the system and * * goes to install a WebSphere * * Enterprise Application, the .ear file * * may not expand into the correct * * directory. * **************************************************************** * RECOMMENDATION: * **************************************************************** Note: Only applicable in systems with multiple network interface cards! WebSphere uses the value returned by the UNIX/Windows hostname command as its node name. This will generally be the primary NIC (network interface card) on the machine, which is a problem if you need it to bind to the secondary NIC. In this case, after installing an enterprise application on a WebSphere system, the contents of the .ear file are not placed in the $WAS_HOME/installedApps directory.Problem conclusion Changed the code in method installOnNode(), in file: com\ibm\ejs\sm\beans\EnterpriseAppBean.java so that .ear file will expand properly.Temporary fix Temporary fix provided to customer on 15MAY02. Fix location is wasdoc0:/apars/PQ60843/4.02 - it contains readme.txt and PQ60843_eFix.jar.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 #: PQ60843
IBM Group: Software Group
Modified date: Jun 27, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.