openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Catalina Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-375) DB2 autoCommit(true) causes Result Set prematurely closed in WebContainer JEE environment.
Date Tue, 30 Oct 2007 21:57:50 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538930
] 

Catalina Wei commented on OPENJPA-375:
--------------------------------------

The fix for this problem has been undone under svn commit: r590481.
Here is the reason:
In WebSphere, there is a costom property that is configurable for DB2 datasources. This property
is named "resultSetHoldability", the default value is 2; which means CLOSE_CURSOR_AT_COMMIT.
This property should be set to 1 if running with OpenJPA; 1 means HOLD_CURSORS_OVER_COMMIT.

Catalina


> DB2 autoCommit(true) causes Result Set prematurely closed in WebContainer JEE environment.
> ------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-375
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-375
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.0, 1.0.1, 1.1.0
>            Reporter: Catalina Wei
>            Assignee: Catalina Wei
>             Fix For: 1.0.1, 1.1.0
>
>
> 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