WebSphere Portal Server - xmlaccess problem with portlet update after installing fixpack 5 for WPS 4.1.2 (=4.1.5

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Portal Server > January 2004 > xmlaccess problem with portlet update after installing fixpack 5 for WPS 4.1.2 (=4.1.5





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author xmlaccess problem with portlet update after installing fixpack 5 for WPS 4.1.2 (=4.1.5
herrfurt

2004-01-19, 2:55 pm

Hello,

I have a problem with the use of xmlaccess with the supplied "UpdatePortlets.xml" after installing fixpack 5 for WPS 4.1 on a 2 node cluster system.

I have first installed the fixpack on a single node system before - there this update of portlets via the supplied xml file worked fine.

On the cluster system I get the following error:
########################################
##
<pre>
Reading input file: D:\WebSphere\PortalServer\fixpacks\5\Upd
atePortlets.xml
Request accepted
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE request PUBLIC "-//IBM//DTD Portal Configuration 1.0//EN" "PortalConfig.dtd"&gt;
&lt;!-- 1/23 --&gt;
&lt;request&gt;
&lt;status element="package" refname="com.ibm.wps.portlets.install" result="failed"&gt;
&lt;message&gt;com.ibm.wps.command.xml.XmlCommandException: Error during execution: [package globalid="com.ibm.wp
s.portlets.install" handle="com.ibm.wps.portlets.install"] Nested exception is: com.ibm.wps.command.Comma
ndFailedException: UpdatePortletApplication failed. WrappedException is: com.ibm.wps.portletcontainer.managers.PortletAp
plicationManagerException: Error with using WSCP Module install&lt;/message&gt;
&lt;/status&gt;
&lt;/request&gt;
<pre>
#######################################

The appserver-out log of the portal application server indicates, that a duplicate context root was specified.

The appserver-error log says, that the wscp module install failed with a ArchiveInstallException and a InvalidApplicationNameException, saying that this app name already exists.

I don't know why this happens, it should work fine, because the xml file requests an update, which also works on my single node system again, if I start it there again.

Thoughts and suggestions?
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com