Error uninstalling Portal v9: disable-v9-features fails with WASX7015E
When uninstalling Portal v9, I got a message in the Installation Manager wizard telling me that the disable-v9-features task was unsuccessful and that I needed to fix the problem and re-run the task in order to complete the process.
When I try to run the task, I get this error:
WASX7015E: Exception running command: "source "/opt/IBM/WebSphere/PortalServer/base/wp.script/config/was/wp_VirtualPortalListAll.jacl""; exception information:
com.ibm.bsf.BSFException: error while eval'ing Jacl expression:
javax.management.ServiceNotFoundException: MBean not found: WebSphere:node=paix439Node,type=WPScriptLink,*.
while executing
"$Portal login $fileprop"
(file "/opt/IBM/WebSphere/PortalServer/base/wp.script/config/was/wp_VirtualPortalListAll.jacl" line 30)
(file line 30)
invoked from within
"source "/opt/IBM/WebSphere/PortalServer/base/wp.script/config/was/wp_VirtualPortalListAll.jacl""
and the Portal server is not reachable from a browser. How can I correct this?
This problem was observed on AIX, but other platforms may be affected.
The root of the problem is that this Portal server is configured to use a Derby database, and Derby allows only a single connection at a time. A rogue process was still running in the background with a lock on the database; killing that process allowed the disable-v9-features task to complete.
-Details-
The problem was discovered by examining the WebSphere_Portal SystemOut.log file, where this error was observed:
Caused by: ERROR XJ040: Failed to start database '/opt/IBM/WebSphere/wp_profile/PortalServer/derby/wpsdb' with class loader com.ibm.ws.bootstrap.ExtClassLoader@fcb706cd, see the next exception for details. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 87 more Caused by: ERROR XSDB6: Another instance of Derby may have already booted the database /opt/IBM/WebSphere/wp_profile/PortalServer/derby/wpsdb.
We stopped the Portal server and ran a command to search for other running processes that might have a lock on the database. This revealed an unexpected older server instance that was still running:
# ps -ef | grep WebSphere
root 13828182 1 0 Dec 01 pts/0 20:58 /opt/IBM/WebSphere/AppServer/java/8.0/bin/java... [[ very long command string here ]]
#
A final review of SystemOut.log revealed that process 13828182 was a previous instance of the Portal server for which the shutdown process had not fully completed. This "zombie" process did not prevent us from starting a new Portal Server process later, but it kept a lock on the Derby database, which prevented the new server instance from accessing the data.
The solution was to issue a kill command to terminate process 13828182. Once that was done, the disable-v9-features task was able to complete successfully.