[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-891) SET CHAINED command not allowed within multi-statement transaction

Steve Ebersole (JIRA) noreply at atlassian.com
Mon Mar 21 13:00:38 EDT 2011


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-891.
------------------------------


Closing stale resolved issues

> SET CHAINED command not allowed within multi-statement transaction
> ------------------------------------------------------------------
>
>                 Key: HHH-891
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-891
>             Project: Hibernate Core
>          Issue Type: Bug
>         Environment: Sybase 12.5, IBM Rational Application developer and WAS 6.0, Windows XP development stations. We'reusing latest verions of Spring.  The JDBC Driver is JConnect 5.5
>            Reporter: Harry Grongstad
>            Priority: Blocker
>
> We are using the OpenSessionInView filter to open the Hibernate session, we call a service layer to load *most* data and that layer has transactional methods ( findXXX() ).  The OpenSessionInView implementation we use starts a transaction (JTA).  The service layer uses "REQUIRES NEW" as trasnaction attribute.
> The problem "ERROR JDBCExceptionReporter:58 - SET CHAINED command not allowed within multi-statement transaction" which was reported before in  another JIRA post, happens if we try to load any data ( fetching for lazy loaded collections for example ) without a trasaction started.
> We have looke at this extensively and ended up with having to have the OpenSessionInView filter open a transaction, just to make sure one exists, then when we call the service layer another stransaction is started ( which we belive is overkill, but works as a stop gap measure)
> We belive we should be able to fetch the data (READ ONLY) for lazy loaded collections without explicitly starting a trasaction.

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

        


More information about the hibernate-issues mailing list