You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/02/14 22:52:05 UTC
[jira] Created: (OPENJPA-149) non-jta-data-source must be specified
in WebSphere environments
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.
[jira] Commented: (OPENJPA-149) non-jta-data-source must be
specified in WebSphere environments
Posted by "Brad L Vandermoon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476062 ]
Brad L Vandermoon commented on OPENJPA-149:
-------------------------------------------
Is there a recommended solution on how to use DB2 SEQUENCES in websphere?
> 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.
[jira] Commented: (OPENJPA-149) non-jta-data-source must be
specified in WebSphere environments
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474324 ]
Kevin Sutter commented on OPENJPA-149:
--------------------------------------
The referenced method (com.ibm.ws.Transaction.TransactionManagerFactory.getTransactionManager) is an internal WebSphere SPI and should not be recommended as a resolution for the problem.
> 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.
[jira] Commented: (OPENJPA-149) non-jta-data-source must be
specified in WebSphere environments
Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473746 ]
Patrick Linskey commented on OPENJPA-149:
-----------------------------------------
According to OPENJPA-144, it would seem that this can be resolved with the following properties entry:
<entry key="openjpa.ManagedRuntime" value="invocation(TransactionManagerMethod=com.ibm.ws.Transaction.TransactionManagerFactory.getTransactionManager)"/>
> 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.
[jira] Updated: (OPENJPA-149) non-jta-data-source must be specified
in WebSphere environments
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter updated OPENJPA-149:
---------------------------------
Fix Version/s: 0.9.7
Priority: Blocker
Affects Version/s: 0.9.6
I am assigning this Issue to version 0.9.7, although it really doesn't require a change in the OpenJPA code. This Issue is dependent on a change in the WebSphere code that should be in the Beta release for the EJB3/JPA Feature Pack. I will also assign this Issue to myself for tracking purposes.
> 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
> Assigned To: Kevin Sutter
> Priority: Blocker
> Fix For: 0.9.7
>
>
> 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.
[jira] Assigned: (OPENJPA-149) non-jta-data-source must be
specified in WebSphere environments
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter reassigned OPENJPA-149:
------------------------------------
Assignee: Kevin Sutter
> 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
> Assigned To: Kevin Sutter
>
> 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.
[jira] Commented: (OPENJPA-149) non-jta-data-source must be
specified in WebSphere environments
Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473223 ]
Patrick Linskey commented on OPENJPA-149:
-----------------------------------------
This is primarily a usability issue.
> 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.
[jira] Commented: (OPENJPA-149) non-jta-data-source must be
specified in WebSphere environments
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ 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.