openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1036) CLONE -DB2 autoCommit(true) causes Result Set prematurely closed in WebContainer JEE environment.
Date Thu, 30 Apr 2009 14:53:30 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dick updated OPENJPA-1036:
----------------------------------

    Fix Version/s:     (was: 1.1.0)

Not sure if this issue is resolved or not but there are no commits so I'm guessing it's not
in 1.0.1 or 1.1.0. 

> CLONE -DB2 autoCommit(true) causes Result Set prematurely closed in WebContainer JEE
environment.
> -------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1036
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1036
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.0, 1.0.1, 1.1.0
>            Reporter: Bogdan Stroe
>            Assignee: Catalina Wei
>
> Invalid operation: Result set is closed is reported from DB2, running in Web Container,
non-jta-data-source, transaction local, JEE environment.
> A workaround is to set the following property in persistence.xml for DB2:
> <property name="openjpa.jdbc.DBDictionary"
>             value="db2(supportsMultipleNontransactionalResultSets=false)"/>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message