PQ62502: XMLCONFIG CHANGES NOT UPDATED IN A RUNNING WSCP SESSION | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer found a problem where changes made by xmlconfig are not visibe in wscp if the wscp session was started before the xmlconfig act. . Here is the steps we followed to reproduce the problem: . Step 1) create application server as_test using XMLConfig /opt/WebSphere/AppServer/bin> ./XMLConfig.sh -adminNodeName wsmajestix -import $HOME/as.xml -substitute "action=create" [4/17/02 19:09:36:960 CEST] 3f74d NodeConfig A XMLC0053I: Importing Node : wsmajestix [4/17/02 19:09:37:904 CEST] 3f74d ApplicationSe A XMLC0053I: Importing ApplicationServer : as_test . step 2) Start wscp (session 1) and verify XMLconfig action wscp> ApplicationServe show /Node:wsmajestix/ApplicationServer: as_test/" -attribute SystemProperties {SystemProperties {}} . ==> Ok, as_test is there, everything ok. . step 3) remove appserver as_test using XMLConfig /opt/WebSphere/AppServer/bin> ./XMLConfig.sh -adminNodeName wsmajestix -import $HOME/as.xml -substitute "action=delete" [4/17/02 19:12:26:461 CEST] 3f74d NodeConfig A XMLC0053I: Importing Node : wsmajestix [4/17/02 19:12:27:428 CEST] 3f74d ApplicationSe A XMLC0053I: Importing ApplicationServer : as_test . step 4) create application server as_test again /opt/WebSphere/AppServer/bin> ./XMLConfig.sh -adminNodeName wsmajestix -import $HOME/as.xml -substitute "action=create" [4/17/02 19:12:59:588 CEST] 3f74d NodeConfig A XMLC0053I: Importing Node : wsmajestix [4/17/02 19:13:00:569 CEST] 3f74d ApplicationSe A XMLC0053I: Importing ApplicationServer : as_test . step 5) using wscp (session 1) which is still open from before wscp> ApplicationServer show Node:wsmajestix/ApplicationServer: as_test/" -attribute SystemProperties RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: ; nested exception is: javax.ejb.ObjectNotFoundException . ==> OOPS the applicaton server as_test could not be found . step 5) open a second new wscp session (session 2) /opt/WebSphere/AppServer/bin> ./wscp.sh wscp> ApplicationServer show /Node:wsmajestix/ApplicationServer: as_test/" -attribute SystemProperties {SystemProperties {}} . ===> Ok, if I open a new wscp session I can see the changes that were made previously . This looks to me as if some xmlconfig changes are not correctly reflected in a open wscp session.Local fix Work Around: Before step 5 do a list wscp>ApplicationServer list step 5) wscp>ApplicationServer show Node:wsmajestix/ApplicationServer: as_test/" -attribute SystemPropertiesProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server Users of * * WSCP and XMLCONFIG * **************************************************************** * PROBLEM DESCRIPTION: Running WSCP session does not * * recognize changes made by XMLConfig. * **************************************************************** * RECOMMENDATION: * **************************************************************** Running WSCP session does not recognize changes made by XMLConfig.Problem conclusion Running WSCP session does not recognize changes made by XMLConfig. Stale objects are being removed from Cache as part of this fix.Temporary fix eFix PQ62502 has been provided to the customer, waiting for feed backComments
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 #: PQ62502
IBM Group: Software Group
Modified date: Aug 6, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.