PQ75164: Create variable on a new Server causes Error 500 and RepositoryExcep tion | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description From Deployment Manager Admin Console, create a new server, save it and start the server. From AdminConsole, go to Environment->Manage WebSphere Variables and select newly created server for context and click New, and info about variable and click OK. You get following error. Error 500 An error occurred while processing request: /syncworkspace.do Message: RepositoryException while updating documents in master repository com.ibm.ws.sm.workspace.WorkSpaceException: RepositoryException while updating documents in master repository at com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.up date(WorkSpaceMasterRepositoryAdapter.java:341) at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.update(Reposi toryContextImpl.java:1263) at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.synch(Reposit oryContextImpl.java:1219) at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.synch(WorkSpaceImpl.j ava:324) at com.ibm.ws.console.core.action.SyncWorkSpaceAction.perform(SyncW orkSpaceAction.java:164) at org.apache.struts.action.ActionServlet.processActionPerform(Acti onServlet.java:1791) at org.apache.struts.action.ActionServlet.process(ActionServlet.jav a:1586) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java: 492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWr apper.java:255) at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java :229) at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java: 137) at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.j ava:237) at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService( StrictServletInstance.java:110) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service( StrictLifecycleServlet.java:174) at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictL ifecycleServlet.java:313) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(S trictLifecycleServlet.java:116) at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletI nstance.java:283) at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispa tch(ValidServletReferenceState.java:42) at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatc h(ServletInstanceReference.java:40) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWeb AppDispatch(WebAppRequestDispatcher.java:923) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch( WebAppRequestDispatcher.java:528) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(W ebAppRequestDispatcher.java:176) at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoke r.java:79) at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(W ebAppInvoker.java:201) at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handle Invocation(CachedInvocation.java:71) at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationCont ext.invoke(CacheableInvocationContext.java:114) at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByUR I(ServletRequestProcessor.java:186) at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.servic e(OSEListener.java:334) at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpCoLocal fix nnection.j va:56) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnecti on.java(Compiled Code)) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code)) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) LOCAL FIX:ン NoneProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * 5.0 who are trying to create a new variable * * on a new application server. * **************************************************************** * PROBLEM DESCRIPTION: The variable.xml file is not created * * when a new application server is * * created through the Thin Admin. * **************************************************************** * RECOMMENDATION: * **************************************************************** From the Deployment Manager ( DMgr ) Admin Console, if the user creates a new server, saves it and starts the server the log file will have an Error 500 message about the variables.xml file because it does not exist. Also, from the DMgr Admin Console, if the user attempts to create a variable at the server context, the same Error 500 is thrown, which creates a zero length variables.xml file on the server.Problem conclusion This problem is fixed in Fix Pack 5.0.2 with a few internal defects which are related: 162519.1 , 162519 , and 161475.1 . Basically, the variable.xml file was not created when a new applciation server was added. the file is created from a template, however, the template was missing. The following files were modified: VariableSubstitutionEntryDetailAction.java J2EEResourcePropertyDetailAction.java ServerUtilImpl.java ServerDelegator.java A new file, variables.xml was created as well.Temporary fix Fixed in PTF2Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ75164
IBM Group: Software Group
Modified date: Aug 7, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.