[
http://jira.dspace.org/jira/browse/DS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10685#action_10685
]
Flávio Botelho commented on DS-320:
-----------------------------------
Maybe i am calling victory too soon, but seems like the bug is finally gone.
Only 1 day of real testing.
The second patch gets XMLUI to follow the same behavior of JSPUI in regard to
the Context finalization. That seems to have made it go away.
> java.util.NoSuchElementException: Timeout waiting for idle objec
> ----------------------------------------------------------------
>
> Key: DS-320
> URL: http://jira.dspace.org/jira/browse/DS-320
> Project: DSpace 1.x
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.5.2
> Reporter: Flávio Botelho
> Priority: Blocker
> Attachments: dspace_context_finalize.patch,
> dspace_statement_closed_problem_XMLUI.txt
>
>
> We have been restarting Tomcat daily now, sometimes multiple times a day, the
> connections are running out.
> From a heap dump its clear that there is a lot of Context objects not being
> released, actually being hold onto by Finalizer.
> When applied Mark Woods patch:
> http://jira.dspace.org/jira/browse/DS-253
> That seemed to make it longer for the problems to appear, but still they end
> up happening. (Nevertheless the patch brings other concurrent critical
> problem from cocoon, that we never actually spotted in production).
> There are some Exceptions appearing before the one about no connections left,
> but the most common one is:
> Caused by: org.postgresql.util.PSQLException: This statement has been closed.
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.checkClosed(AbstractJdbc2Statement.java:2444)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.setInt(AbstractJdbc2Statement.java:1150)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:117)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.setInt(DelegatingPreparedStatement.java:117)
> at
> org.dspace.storage.rdbms.DatabaseManager.loadParameters(DatabaseManager.java:1676)
> at
> org.dspace.storage.rdbms.DatabaseManager.query(DatabaseManager.java:219)
> at
> org.dspace.storage.rdbms.DatabaseManager.querySingle(DatabaseManager.java:302)
> But i don't know why this is happening? Any clues?
> Anyways, maybe there is some problem with the top-level Exception handling in
> XMLUI that is ending up making Contexts getting 'leaked'?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
