Our environment:
uPortal 2.6.1
postgres 8.2
java 1.6.0_16-b01
JAVA_OPTS "-server -verbose:gc -Xloggc:${LOGPATH}/gc.log -Xms1024m
-Xmx1024m -XX:MaxPermSize=256m -XX:+UseAdaptiveSizePolicy
-Dcatalina.logdir="$CATALINA_LOGDIR""
Our university's portal has been struggling over the last month with the
stability of our uPortal. The behavior is usually a really long wait
time that can result in either all of the portal not loading or
individual channels failing to load. It seems to take a while after the
portal has been restarted. Sometimes it will remain stable for a week,
but usually it become unstable after a couple days.
My suspicion from the log files has been some issue with the database
connection pool. Specifically resources from the connection pool being
used and not released. Earlier today the portal exhibited this behavior
prompting a restart. The portal.log file shows the following again and
again:
ERROR [org.jasig.portal.StandaloneChannelRenderer#254211]
portlet.CPortletAdapter.[] Oct/12 10:24:22 - Initialization of the
portlet container failed.
java.io.IOException: Could not load portlet publication preferences: No
resources available at this time
at
org.jasig.portal.container.om.entity.PortletEntityImpl.loadPreferences(PortletEntityImpl.java:216)
at
org.jasig.portal.channels.portlet.CPortletAdapter.initPortletWindow(CPortletAdapter.java:233)
at
org.jasig.portal.channels.portlet.CPortletAdapter.setRuntimeData(CPortletAdapter.java:415)
at
org.jasig.portal.ChannelRenderer$Worker.execute(ChannelRenderer.java:459)
at org.jasig.portal.utils.threading.BaseTask.run(BaseTask.java:27)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:643)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:668)
at java.lang.Thread.run(Thread.java:619)
Caused by: net.unicon.resource.ResourceUnavailableException: No
resources available at this time
at
net.unicon.resource.ResourcePoolBasic.allocate(ResourcePoolBasic.java:127)
at net.unicon.resource.Resources.getConnection(Resources.java:45)
at
net.unicon.resource.ResourceDataSource.getConnection(ResourceDataSource.java:56)
at
org.jasig.portal.RDBMServices.getConnection(RDBMServices.java:331)
at
org.jasig.portal.RDBMServices.getConnection(RDBMServices.java:305)
at
org.jasig.portal.RDBMPortletPreferencesStore.getDefinitionPreferences(RDBMPortletPreferencesStore.java:194)
at
org.jasig.portal.container.om.entity.PortletEntityImpl.loadPreferences(PortletEntityImpl.java:206)
... 9 more
Is there any way to try and pinpoint the offending code that could be
responsible for opening connections and not properly closing them? We
are not currently using any home-grown code in our instance.
If there is any other information that could help, let me know.
Thanks
--
Paul
---
You are currently subscribed to
[hidden email] as:
[hidden email]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-user
