Error: Timeout for content=#number#

Question

RDBMS 8.1.6.3.
Sun solaris 2.6
My previous installation was OAS9i 1.0.2.0 with portal 3.0.6.x
Then yesterday I installed the OAS9i 1.0.2.2 (the runInstaller chose what software had to be deleted, upgraded or installed as new) and I upgraded the portal schemas with the script found here in OTN.
The whole process seemed all ok, but now when I access to the main portal page usually have the error in subject in the place of every portlet. Sometime the error is "Error: The portlet could not be located".
I think both are related to the upgrade process, but I checked the upgrade log produced by the script and found only errors about installing/upgrading Intermedia, but for me it is normal, as I have never installed it.
Does someone have suggestions/comments?
Thanks
Mauro
null

Answer 1

Hi all
First of all, I want to thank you for your suggestions.
Then I would inform you about my progress.
Following Hyundeok's suggestion (I don't use SSL), I checked the jserv.log and I found these errors:
1) Repository /pandorino_home/3rdsw/oradba/product/OAS9I/Apache/Jserv/servlets/Parallel.jar doesn't exist!
2) page/JNI: Exception when trying to connect in 1.
page/Timeout occurred, label=510 url=http://pandorino:7777/pls/dad_portal/!WWW_PORTAL.wwpro_app_provider.execute_portlet
page/ContentFetcher InterruptedIOException Caught, Fetcher Timedout name=content-fetcher5
3) (EMERGENCY) ajp12: ping: no reply (0) Please make sure that the wrapper.classpath is pointing to the correct version of ApacheJServ.jar
(EMERGENCY) ajp12[1]: cannot scan servlet headers (500)
(ERROR) an error returned handling request via protocol "ajpv12"
(ERROR) an error returned handling request via protocol "balance"
4) page/UncaughtException in thread name=content-fetcher2, starting a new fetcher after exception java.lang.ThreadDeath
My comments/actions:
About (1), very strange, the Parallel.jar file doesn't exist! But I don't think that
it is related to the error in subject. In any case this error is raised only at Apache startup.
About (2), when it occurs, I see the error "Error: Timeout for content=#number#" in the place of portlet.
following Randy's suggestion, I increased the timeout of:
(-) "Login Server" portlet provider (from 10 to 20 seconds),
(-) "Oracle Report Security" portlet provider (from 1(one) to 20 seconds),
(-) "Monitor" portlet provider (from 10 to 20 seconds).
About (3), I increased the timeout in the jserv.conf file: ApJServVMTimeout 20
About (4), when it occurs, I see the error "Error: The portlet could not be contacted" in the place of portlet.
No action performed.
After a week of tests, It seems that (2) and (3) have been fixed thanks to the increased timeout.
Concerning (4), it is still experienced by me and other users. I think that in this case the
last thing to try is to apply the patch fix suggested by John.
But at the moment I don't have time to do this, so in the meantime I will press the browser's "reload" button until the portlet is displayed.
Thanks again.
Mauro