]
Fyrn Jilot commented on HHH-891:
--------------------------------
Look [here |
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.
For more information on JIRA, see: