openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-149) non-jta-data-source must be specified in WebSphere environments
Date Wed, 28 Feb 2007 22:12:50 GMT

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

Kevin Sutter commented on OPENJPA-149:
--------------------------------------

Brad,
For now, go ahead and use the workaround as documented by Patrick's comment.  This is not
the preferred method (from a WebSphere perspective), but if it helps with your immediate usage
of db2 sequences, then go for it.  The use of the internal WebSphere TransactionManager interfaces
should be considered a temporary workaround.  I am waiting for a new transaction API from
WebSphere development before I can formally resolve this Issue.  According to my sources,
this should be available soon.  Thanks for your patience.

Kevin

> 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
>         Environment: WebSphere
>            Reporter: Patrick Linskey
>
> 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.


Mime
View raw message