PQ67047: ATTEMPT TO MODIFY VIRTUAL HOST WITH WSCP PRODUCES INCOMPLETE RESULTS. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Virtual host created with wscp 1) Does NOT appear in admin console or in XMLConfig export. 2) Does appear in config plugin file regenerated. 3) Produces error when app server is started 4) Is detected by admin console as existing when attempt is made to add same virtual host from admin console after first adding it in wscp . I was able to reproduce the problem in WAS v4.0.2. I had the default_server as part of a server group. I had all of the symptoms the customer described except that I could start the default_server without error.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0.5 and * * earlier users of WSCP to modify Virtual * * Host binding on Module. Problem reported * * on 4.0.4. * **************************************************************** * PROBLEM DESCRIPTION: When modifying Virtual Host * * attribute information on Module with * * WSCP, the changes are not reflected * * on console nor xmlconfig. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following WSCP command example was used to modify Virtual Host attribute on Module: wscp> Module modify {/EnterpriseApp:sampleApp/Module:sample_web_module} -attribute {{ModuleBindingsConfig {WebAppBindings {{VirtualHostName new_vh}}}}} The command runs without any error and the subsequent GenPluginCfg.sh recreated the plugin-cfg file with the correct vhost references. A Module show also reflected the change in its output. However, the admin console and XMLConfig output still showed the old virtual host.Problem conclusion This APAR fixed the problem that use WSCP to modify Virtual Host information on a Module does not get updated on the ModuleBinding in the repository.Temporary fix customer is testing the supplied test eFix, waiting for statusComments
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 #: PQ67047
IBM Group: Software Group
Modified date: Nov 5, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.