[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3740) ManagedHibernateSession not disconnected after rendering response

Pete Muir (JIRA) jira-events at lists.jboss.org
Sun Nov 23 22:33:36 EST 2008

     [ https://jira.jboss.org/jira/browse/JBSEAM-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-3740:

    Issue Type: Feature Request  (was: Task)

> ManagedHibernateSession not disconnected after rendering response
> -----------------------------------------------------------------
>                 Key: JBSEAM-3740
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3740
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 2.0.2.SP1
>         Environment: jboss-4.2.3.ga
>            Reporter: Jakub Janczak
>            Priority: Optional
> It's not a bug, but it would be nice of Seam to close the connection of the hibernate session after rendering the page. It's crucial when hibernate is used in filters which are not using seam managed Session - especially for Jboss's CachedConnectionManager which is closing old jdbc connections before creating a new ones, causing a Seam managed session to disfunct. 
> Partial fix for this problem is to use the hibernate's release mode after_transaction, but it's not as effective as a on_close one.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list