<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Guy Pardon: Transactional J2EE Apps with Spring</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Sat, 18 May 2013 06:14:18 -0400</pubDate>


    <item>

        <title>And what about database isolation levels</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[<blockquote>Nice presention Guy. Could you also explain if it is possible, and if so how, you can specify a specific database isolation level for different data access methods. For example for many select queries a &quot;dirty-read&quot; (fast!) is ok....]]></description>
        

        <pubDate>Sat, 03 Dec 2005 07:02:17 -0500</pubDate>

        

        <jf:creationDate>Sat, 03 Dec 2005 07:02:17 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 03 Dec 2005 07:02:17 -0500</jf:modificationDate>
        <jf:date>Dec 3, 2005</jf:date>
        <jf:author>GuyPardon</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Another scenario</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[I know of a couple of other options to avoid the race condition.<br><br>WebLogic 9.0 provides a JDBC option that safely avoids XA protocol overhead with the database and also happens to guarantee that the database's portion of the transaction is always...]]></description>
        

        <pubDate>Wed, 30 Nov 2005 13:41:58 -0500</pubDate>

        

        <jf:creationDate>Wed, 30 Nov 2005 13:41:58 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 30 Nov 2005 13:41:58 -0500</jf:modificationDate>
        <jf:date>Nov 30, 2005</jf:date>
        <jf:author>Tom Barnes</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>XA overhead</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[<blockquote>BTW one trick to improve throughput if you must use XA with JMS and database is to use batching; since the XA protocol adds a relativley fixed overhead, you can process 100 or 1000 messages in a single XA transaction which greatly improves...]]></description>
        

        <pubDate>Wed, 30 Nov 2005 13:14:05 -0500</pubDate>

        

        <jf:creationDate>Wed, 30 Nov 2005 13:14:05 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 30 Nov 2005 13:14:05 -0500</jf:modificationDate>
        <jf:date>Nov 30, 2005</jf:date>
        <jf:author>Tom Barnes</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>EJB component model but without app server</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[What I don't like too much is the fact that Spring forces me to build a lot of code *around&quot; the basic EJB model to make applications run outside an application server. That's not what I would call &quot;easy to use&quot;. Check out the CUBA project...]]></description>
        

        <pubDate>Tue, 29 Nov 2005 20:08:59 -0500</pubDate>

        

        <jf:creationDate>Tue, 29 Nov 2005 20:08:59 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 29 Nov 2005 20:08:59 -0500</jf:modificationDate>
        <jf:date>Nov 29, 2005</jf:date>
        <jf:author>Jan Lessner</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Another scenario</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[<blockquote>Thread 1:1) Starts a new XA Transaction2) Inserts a record into DB3) Sends a JMS message4) Commits the XA transactionThread 2:1) Receives message from the above2) </blockquote><br>It just means your JMS session doesn't work in XA mode or...]]></description>
        

        <pubDate>Tue, 29 Nov 2005 02:31:53 -0500</pubDate>

        

        <jf:creationDate>Tue, 29 Nov 2005 02:31:53 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 29 Nov 2005 02:31:53 -0500</jf:modificationDate>
        <jf:date>Nov 29, 2005</jf:date>
        <jf:author>Timur Evdokimov</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Guy Pardon: Transactional J2EE Apps with Spring</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[<blockquote>Duplicate detection is an efficient solution as well since it avoids all those slow sync-to-disks of XA and you can perform the duplicate detection if the JMS message has Message.isJMSRelivered() returning true. i.e. for normal operation,...]]></description>
        

        <pubDate>Tue, 29 Nov 2005 02:27:00 -0500</pubDate>

        

        <jf:creationDate>Tue, 29 Nov 2005 02:27:00 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 29 Nov 2005 02:27:00 -0500</jf:modificationDate>
        <jf:date>Nov 29, 2005</jf:date>
        <jf:author>Timur Evdokimov</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Why not use EJBs??</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[EJB session beans (stateless and stateful) provide a good programming model for transactional boundary control and packaging of business logic.  <br><br>As someome mentioned before, it is important to be clear on which type of &quot;EJB&quot; one is...]]></description>
        

        <pubDate>Mon, 28 Nov 2005 10:57:47 -0500</pubDate>

        

        <jf:creationDate>Mon, 28 Nov 2005 10:57:47 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 28 Nov 2005 10:57:47 -0500</jf:modificationDate>
        <jf:date>Nov 28, 2005</jf:date>
        <jf:author>Randy  Schnier</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>And what about database isolation levels</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[Nice presention Guy. <br><br>Could you also explain if it is possible, and if so how, you can specify a specific database isolation level for different data access methods. For example for many select queries a &quot;dirty-read&quot; (fast!) is ok. For...]]></description>
        

        <pubDate>Mon, 28 Nov 2005 07:52:52 -0500</pubDate>

        

        <jf:creationDate>Mon, 28 Nov 2005 07:52:52 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 28 Nov 2005 07:52:52 -0500</jf:modificationDate>
        <jf:date>Nov 28, 2005</jf:date>
        <jf:author>robin bakkerus</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Another scenario</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[The problem is that you are assuming the database is committed before JMS when committing the JTA global transaction; I dont think it's valid to assume a specific ordering of XA resource commits within a global transaction. Instead of thread 1 inserting...]]></description>
        

        <pubDate>Mon, 28 Nov 2005 00:49:31 -0500</pubDate>

        

        <jf:creationDate>Mon, 28 Nov 2005 00:49:31 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 28 Nov 2005 00:49:31 -0500</jf:modificationDate>
        <jf:date>Nov 28, 2005</jf:date>
        <jf:author>Jeff Tuatini</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Another scenario</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[What you are running into is s race condition in the 2nd phase of the 2pc. WLS can send the 2nd phase commit message in parallel and often, especially if you're using a JMS filestore, JMS commits much faster while the DB is still chugging along. The MDB...]]></description>
        

        <pubDate>Mon, 28 Nov 2005 00:45:18 -0500</pubDate>

        

        <jf:creationDate>Mon, 28 Nov 2005 00:45:18 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 28 Nov 2005 00:45:18 -0500</jf:modificationDate>
        <jf:date>Nov 28, 2005</jf:date>
        <jf:author>Satadru Roy</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Another scenario</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[I am not sure if this is transaction related but I ran into lots of problem related to the following:<br><br>Thread 1:<br>1) Starts a new XA Transaction<br>2) Inserts a record into DB<br>3) Sends a JMS message<br>4) Commits the XA...]]></description>
        

        <pubDate>Sun, 27 Nov 2005 22:24:31 -0500</pubDate>

        

        <jf:creationDate>Sun, 27 Nov 2005 22:24:31 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 27 Nov 2005 22:24:31 -0500</jf:modificationDate>
        <jf:date>Nov 27, 2005</jf:date>
        <jf:author>Vincent Shek</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>Duplicate elimination by application</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[<blockquote>Golden rule is - duplicates in messaging should be avoided by application code without TX.</blockquote><br>Hi,<br><br>Thanks, I like your point about duplicate responses. <br><br>Putting duplicate detection in the application is possible, but...]]></description>
        

        <pubDate>Sun, 27 Nov 2005 15:57:27 -0500</pubDate>

        

        <jf:creationDate>Sun, 27 Nov 2005 15:57:27 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 27 Nov 2005 15:57:27 -0500</jf:modificationDate>
        <jf:date>Nov 27, 2005</jf:date>
        <jf:author>GuyPardon</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>More information on JTA use cases</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[If you will store message number somewhere in database you can easily avoid duplicate message processing. When number in message is already in your database, you can discard incoming message because it was for sure processed.<br>More problem is with...]]></description>
        

        <pubDate>Sat, 26 Nov 2005 21:52:53 -0500</pubDate>

        

        <jf:creationDate>Sat, 26 Nov 2005 21:52:53 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 26 Nov 2005 21:52:53 -0500</jf:modificationDate>
        <jf:date>Nov 26, 2005</jf:date>
        <jf:author>Pavel Tavoda</jf:author>
        <jf:replyCount>6</jf:replyCount>
    </item>


    <item>

        <title>More information on JTA use cases</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[Hi,<br><br>First of all: thank you all for the feedback!<br><br>I have had so many email requests for more information on the JTA use cases that I have prepared some entries in our FAQ; see <a...]]></description>
        

        <pubDate>Sat, 26 Nov 2005 06:15:05 -0500</pubDate>

        

        <jf:creationDate>Sat, 26 Nov 2005 06:15:05 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 26 Nov 2005 06:15:05 -0500</jf:modificationDate>
        <jf:date>Nov 26, 2005</jf:date>
        <jf:author>GuyPardon</jf:author>
        <jf:replyCount>7</jf:replyCount>
    </item>


    <item>

        <title>Why not use EJBs??</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=37689</link>

        

        
            <description><![CDATA[I used Stateless session Beans which for Transaction management for updating 2 different databases , with failover recovery. Certainly with EJB 3.0 , things would be lot better. But surely Transaction management with Spring is worth trying.<br><br>Are we...]]></description>
        

        <pubDate>Fri, 25 Nov 2005 00:24:46 -0500</pubDate>

        

        <jf:creationDate>Fri, 25 Nov 2005 00:24:46 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 25 Nov 2005 00:24:46 -0500</jf:modificationDate>
        <jf:date>Nov 25, 2005</jf:date>
        <jf:author>shailendra Pandey</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>



</channel>
</rss>

