activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-59) allow JDBC persistence to be linked with normal JDBC operations to avoid XA
Date Thu, 15 Jun 2006 04:46:51 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-59?page=all ]

Hiram Chirino updated AMQ-59:
-----------------------------

    Fix Version: 4.3

putting on road map out there in 4.3 land.  Perhaps someone will get interested in this idea
sooner and implement it.

> allow JDBC persistence to be linked with normal JDBC operations to avoid XA
> ---------------------------------------------------------------------------
>
>          Key: AMQ-59
>          URL: https://issues.apache.org/activemq/browse/AMQ-59
>      Project: ActiveMQ
>         Type: New Feature

>   Components: Message Store
>     Reporter: james strachan
>     Priority: Minor
>      Fix For: 4.3

>
>
> Its a common use case to perform JDBC operations along with JMS and want XA. If we're
using JDBC persistence for the message store, we could use the same JDBC connection and avoid
the need for XA.
> To implement this we could
> * use a synchronous VM TransportChannel (currently VMTransportChannel is async)
> * let the JDBCMessageStore use the current Connection that the users persistence code
is using (e.g. using Spring's helper methods or something - a custom DataStore provider could
hide this
> Then the Connection.commit() could effectively be an XA like commit across any persistence
code and JMS operations

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message