Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <14447631.1184440684449.JavaMail.jira@brutus>
Date: Sat, 14 Jul 2007 12:18:04 -0700 (PDT)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Commented: (OPENJPA-149) non-jta-data-source must be
 specified in WebSphere environments
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Craig Russell commented on OPENJPA-149:
---------------------------------------

This issue is marked as "fix for 0.9.8". Is it still important? Is it ok to require the use of the non-transactional data source or use Patrick's workaround?

> non-jta-data-source must be specified in WebSphere environments
> ---------------------------------------------------------------
>
>                 Key: OPENJPA-149
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-149
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 0.9.6
>         Environment: WebSphere
>            Reporter: Patrick Linskey
>            Assignee: Kevin Sutter
>            Priority: Blocker
>             Fix For: 0.9.8
>
>
> The suspend(), resume(), begin(), and commit() methods in org.apache.openjpa.ee.WASManagedRuntime$WASTransaction all throw exceptions. This prevents the logic in org.apache.openjpa.jdbc.kernel.AbstractJDBCSeq from executing. See OPENJPA-144 for relevant stack traces. In particular, look at the Only-JTASpecified.txt trace.

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