[jbossts-issues] [JBoss JIRA] (JBTM-1570) Allow both Non-XA and XA servers
Tom Jenkinson (JIRA)
jira-events at lists.jboss.org
Mon Mar 25 11:56:42 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson moved BLACKTIE-445 to JBTM-1570:
----------------------------------------------
Project: JBoss Transaction Manager (was: Blacktie)
Key: JBTM-1570 (was: BLACKTIE-445)
Affects Version/s: 5.0.0.M2
(was: 5.0.0.M2)
Component/s: BlackTie
(was: All C++ )
Fix Version/s: 5.0.0.M3
(was: 5.0.0.M3)
> Allow both Non-XA and XA servers
> --------------------------------
>
> Key: JBTM-1570
> URL: https://issues.jboss.org/browse/JBTM-1570
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Affects Versions: 5.0.0.M2
> Reporter: Crispin Boylan
> Assignee: Amos Feng
> Fix For: 5.0.0.M3
>
>
> For our application we have a mixture of XA and non-XA servers, for performance and probably due to the fact that Informix (our main DB) only lets one datasource be used in XA mode.
> Unfortunately the blacktie servers do an implicit tx_open, so if you have any XA data sources defined these get used and Informix thinks its in XA mode.
> I currently have a workaround for this which is to have a duplicate btconfig.xml with the XA sources removed and the servers which are NonXA get passed this in the -c of the server args. Seems to work nice, but would be good not to have to do that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list