We were notified that calendar portlet in the production server became unusable all the sudden, even though the same version of calendar portlet is still working fine. The calendar portlet in development environment is using the exact same sets of ics files. Therefore, they should not be the cause of issue. We did not apply any change around the time that the calendar became unusable.
We searched through logs to figure out the reason why the portlet stopped working. In catalina.out we found a line
"INFO: Marking servlet calendar as unavailable"
I assume this is when calendar servlet stopped showing up because we can only see "WARNING: Servlet calendar is currently unavailable" after that line.
Is there a way to make the calendar portlet available again?
Environment
LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 5.8 (Final)
Release: 5.8
Codename: Final
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
Apache-Tomcat-6.0.24
uPortal_3-2-2_20795
Activity
James Wennmacher
September 26, 2013 at 6:02 PM
Not much detail on this and I can't find the strings "Marking servlet", "as unavailable", or "is currently unavailable" in the uP4.1 code. Not sure if this is a Pluto thing or what. I thought maybe the calendar had errors and enough were put into the hung threads queue to have uPortal no longer attempt to render the portlet, but I'd expect to find the string in a log message.
We were notified that calendar portlet in the production server became unusable all the sudden, even though the same version of calendar portlet is still working fine. The calendar portlet in development environment is using the exact same sets of ics files. Therefore, they should not be the cause of issue. We did not apply any change around the time that the calendar became unusable.
We searched through logs to figure out the reason why the portlet stopped working. In catalina.out we found a line
"INFO: Marking servlet calendar as unavailable"
I assume this is when calendar servlet stopped showing up because we can only see "WARNING: Servlet calendar is currently unavailable" after that line.
Is there a way to make the calendar portlet available again?