|
Home > Archive > WebSphere Portal Server > May 2007 > Update 6.0.1 from 6.0 failed
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 |
Update 6.0.1 from 6.0 failed
|
|
|
| Hi,
I am doing update from portal 6.0 to 6.0.1, but I always get error messages said: ../config/actions/was_config.xml: Portal Server failed to start.
I checked this file, it seems the XMLAccessPort is not available. I found that normally it will display failed at around 20 minutes, so I modified this file to setup up the timeout = 12000000, But still get the same error. I am running portal 6.0 on my la
ptop and it normally take around 20 - 30 minutes to startup. I am wondering that where the setting should I set to avoid the timeout issue. Since everytime, it will fail before the XMLAccessPort is available.
I attached my log file. Could anybody please help me solve this issue. I have tried many times but always get the same issue. Any help and advide will be very appreciated.
Cheers,
hj
| |
|
| Hi hj,
I'm no export but I updated my portal lately. I did some timeout settings.. the following:
Open <application server PROFILE root>\properties\soap.client.props
Set com.ibm.SOAP.requestTimeout=6000
Save & close file
Start application server
Logon to the Administrator console
Browse | Servers -> Application Servers -> Websphere_Portal -> Web container settings -> Web container transport chains
For EVERY channel in the list change HTTP Inbound Channel's read and write settings to 180 seconds.
I guess you might tune up these settings to the sky on your laptop.
This might help.
Regards
Tobias
| |
|
| ok, after uninstall wps 6.0, then reinstall it, the update can be installed successfully. But I really don't think this is a good idea.
|
|
|
|
|