Exception in Installing WebSphere Portal Version 5.1.0.4 from Version 5.1.0

prashan...@hsbc.co.in

unread,

Nov 19, 2008, 12:47:29 AM11/19/08

to

I am trying to install WebSphere Portal 5.1.0.4 from 5.1.0 according to steps given in http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/pui_install5102to5104.html.
Steps I am following are as follows-
1. run setupCmdLine.bat and updatePortal.bat
2. change SOAP request time out to 6000 as mentioned
3. run stopserver.bat
4. run WPSconfig.bat CONFIG-WP-PTF-5104
at step 4 I am getting error as

start-portal-server:
[logmsg] 2008.11.18 19:16:38.644 start-portal-server
[logmsg] EJPCA3163I: Starting Server "WebSphere_Portal"

[exec] ADMU0116I: Tool information is being logged in file
[exec] C:\runtimes\base_v51\logs\WebSphere_Portal\startServer.log
[exec] ADMU3100I: Reading configuration for server: WebSphere_Portal
[exec] ADMU3028I: Conflict detected on port 8882. Likely causes: a) An instance of
[exec] the server WebSphere_Portal is already running b) some other
[exec] process is using port 8882
[exec] ADMU3027E: An instance of the server may already be running: WebSphere_Portal
[exec] ADMU0111E: Program exiting with error:
[exec] com.ibm.websphere.management.exception.AdminException: ADMU3027E: An
[exec] instance of the server may already be running: WebSphere_Portal
[exec] ADMU0211I: Error details may be seen in the file:
[exec] C:\runtimes\base_v51\logs\WebSphere_Portal\startServer.log
[exec] ADMU1211I: To obtain a full trace of the failure, use the -trace option.

action-deploy-transformation-dynamicui-5102:
[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:9081/wps/config
[xmlaccess] EJPXB0002I: Reading input file C:\runtimes\PORTAL~1\config\work\DeployDynamicUITransformation.xml
[xmlaccess] EJPXB0012E: Received error response code 503
[xmlaccess] java.net.ConnectException: HTTP status not ok: 503

BUILD FAILED
file:../config/includes/wp-ptf-5102.xml:913: EJPXB0016E: An error occurred on the client: HTTP status not ok: 503

Total time: 39 minutes 1 second

I am attaching startserver.log with this.
Kindly revert back to me if some fix is found. Thanks !

huntman25

unread,

Nov 19, 2008, 6:59:10 AM11/19/08

to

Hi, could you clarify one point? The 5104 upgrade was only supported when upgrading from 5101, 5102, and 5103. Are you really upgrading from just 510?

Also the exception implies that your Portal server is no longer working. Could you also upload these files:

SystemOut.log
wps_ The last two or three of these would be good
ConfigTrace.log

Thanks!

~HT
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

prashan...@hsbc.co.in

unread,

Nov 19, 2008, 7:43:58 AM11/19/08

to

Hi
I am upgrading websphere portal from 5.1.0.1 Attaching log files as needed. Thanks!

huntman25

unread,

Nov 19, 2008, 7:56:12 AM11/19/08

to

Ok, the key exception from the upgrade failure is this:

=============================

action-deploy-transformation-dynamicui-5102:
[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:9081/wps/config
[xmlaccess] EJPXB0002I: Reading input file C:\runtimes\PORTAL~1\config\work\DeployDynamicUITransformation.xml
[xmlaccess] EJPXB0012E: Received error response code 503
[xmlaccess] java.net.ConnectException: HTTP status not ok: 503

Target finished: action-deploy-transformation-dynamicui-5102
==============================

That "HTTP status not ok" exception tells us that we can't access Portal. The startup exception prior this is irrelevant because all it's saying is that Portal is already started.

To see why we can't access Portal, we need to look at the SystemOut and wps_ .log files. In the wps_.log you submitted, Portal fails to work because of a transaction exception:

==============================
2008.11.19 15:53:46.653 E com.ibm.wps.engine.Servlet init
com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem javax.transaction.TransactionRolledbackException: CORBA TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: vmcid: 0x0 minor code: 0 completed: No
at com.ibm.wps.services.puma.RealmAwareURManager.initRealms(RealmAwareURManager.java:143)
.
.
.
Caused by: org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: vmcid: 0x0 minor code: 0 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
===============================

This is most likely due to leftover transaction files in the AppServer/tranlog directory. Also, since the upgrade is running xmlaccess right now, it means that Portal should be working right now. In other words, to test this we can just access Portal in the browser rather than wait 40 mins for the upgrade to fail. Please do the following:

1. Stop the WebSphere_Portal server
2. Delete the following directory:
AppServer/tranlog/WebSphere_Portal
3. Start the WebSphere_Portal server
4. Try to bring it up in a browser
5. If it works, stop the server and continue the upgrade.
If it does not work, please let us know. Also the SystemOut.log was not included in the zip file you submitted, please resubmit that as well.

prashan...@hsbc.co.in

unread,

Nov 20, 2008, 12:24:31 AM11/20/08

to

Followed the steps 1, 2 given. Run \portal_v51\bin\startServer5.bat, and when accessed url 'http://localhost:9081/wps/config' in browser, it shows 'Error 503: Failed to load target servlet [config] '.

Attaching files SystemOut, wps_ as they have got updated now.

huntman25

unread,

Nov 20, 2008, 9:20:30 AM11/20/08

to

Ok, the SystemOut.log shows what the real problem is. You're hitting a transaction timeout before the exceptions we see in the wps_.log:

==========================
[11/19/08 15:50:51:326 IST] 666f767d TimeoutManage I WTRN0006W: Transaction 57415344:000000000000000100000001600e71da7d2415c4c339f2608029baf4be0b86cf5765625370686572655f506f7274616c[] has timed out after 120 seconds.
[11/19/08 15:53:45:153 IST] 7585767f SystemOut O WMM Implementation Version: WMM5.1.x_060711 (July 11 2006)
[11/19/08 15:53:45:435 IST] 7585767f TranManagerIm I WTRN0041I: Transaction 57415344:000000000000000100000001600e71da7d2415c4c339f2608029baf4be0b86cf5765625370686572655f506f7274616c[] has been rolled back.
[11/19/08 15:53:45:497 IST] 7585767f ExceptionUtil E CNTR0019E: Non-application exception occurred while processing method "setDataSourceName". Exception data: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction rolled back; nested exception is:
javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout
at com.ibm.ejs.csi.TransactionControlImpl.completeTxTimeout(TransactionControlImpl.java:1380)
==========================

This technote here should address your issue:

http://www-01.ibm.com/support/docview.wss?rs=688&ca=port&uid=swg21297844

Once that is resolved, you can continue with the upgrade.

Prashant S Pathak

unread,

Nov 21, 2008, 8:56:19 AM11/21/08

to

WPSconfig.bat CONFIG-WP-PTF-5104] which again gave me the error. Attaching logs files.

huntman25

unread,

Nov 21, 2008, 10:11:52 AM11/21/08

to

It does not look like you made the transaction timeout changes correctly. The transactions are still timing out after 120 seconds:

============================
[11/21/08 19:14:44:479 IST] 48c698e4 TimeoutManage I WTRN0006W: Transaction 57415344:000000000000000100000001b712de3f58d82920b3dd4d4e1531f082ed876f455765625370686572655f506f7274616c[] has timed out after 120 seconds.
[11/21/08 19:17:39:305 IST] 7587d8e7 SystemOut O WMM Implementation Version: WMM5.1.x_060711 (July 11 2006)
[11/21/08 19:17:39:508 IST] 7587d8e7 TranManagerIm I WTRN0041I: Transaction 57415344:000000000000000100000001b712de3f58d82920b3dd4d4e1531f082ed876f455765625370686572655f506f7274616c[] has been rolled back.
[11/21/08 19:17:39:586 IST] 7587d8e7 ExceptionUtil E CNTR0019E: Non-application exception occurred while processing method "setDataSourceName". Exception data: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction rolled back; nested exception is:

javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout
at com.ibm.ejs.csi.TransactionControlImpl.completeTxTimeout(TransactionControlImpl.java:1380)

at com.ibm.ejs.csi.TransactionControlImpl.preInvoke(TransactionControlImpl.java:283)
=============================

Also you need to make sure Portal actually renders in a browser first before you attempt the upgrade again. Please upload the following file so I can make sure the transaction timeout values are set correctly:

AppServer/config/cells/cellname/nodes/nodename/servers/WebSphere_Portal/server.xml

Prashant S Pathak

unread,

Nov 24, 2008, 3:33:50 AM11/24/08

to

Actually the technote http://www-01.ibm.com/support/docview.wss?rs=688&ca=port&uid=swg21297844 guided me to upgrade WebSphere Application Server's "Total transaction lifetime timeout" & "Client inactivity timeout" to 1200 seconds.
Updated now the Websphere Portal server's timeouts to 1200 and WPSconfig.bat CONFIG-WP-PTF-5104 command was successful.
Thanks for help!