<?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 - Concurrency and Entity EJBs</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>Tue, 21 May 2013 02:12:18 -0400</pubDate>


    <item>

        <title>Transactions vs none</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Thangs Guy, your answer really helps. I was hoping that I've missed something and this common situation has any solutions more lightweight than transactions.<br><br>We're using JBoss &amp; MySQL, and JBoss doc explicitly says to make transactions as...]]></description>
        

        <pubDate>Mon, 04 Oct 2004 19:00:24 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 19:00:24 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 19:00:24 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Konstantin Sobolev</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Sure, you are right, a bean must throw NoSuchEntityException if, say, ejbStore fails. (And we're using BMP). I mixed it up with NoSuchObjectException which is thrown by a container (6.7.1). And in case of manual control I'll have to catch it as well.]]></description>
        

        <pubDate>Mon, 04 Oct 2004 17:43:24 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 17:43:24 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 17:43:24 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Konstantin Sobolev</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Transactions vs none</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Hi,<br><br>In the hope that I understand your question the right way, here is my view of the situation:<br><br>(also see 10.5.10 of the EJB 2.0 specs):the container has the option to use transactions or some optimistic strategy for your problem. There is...]]></description>
        

        <pubDate>Mon, 04 Oct 2004 16:22:39 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 16:22:39 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 16:22:39 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>GuyPardon</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[- Only your bean methods then run in separate transactions... -<br><br>That is ofcourse not true, entities always use CMT.]]></description>
        

        <pubDate>Mon, 04 Oct 2004 13:39:59 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 13:39:59 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 13:39:59 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Paul Maessen</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[It is the *bean* that throws the exception, the container only handles it. But if you are using CMT then the deployment tools generate the bean code so you are right, it is of no use.<br><br>So, one way would be to use BMP instead of CMP. Only your bean...]]></description>
        

        <pubDate>Mon, 04 Oct 2004 13:28:58 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 13:28:58 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 13:28:58 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Paul Maessen</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Hi Paul,<br><br>Erm.. I don't understand. Yes, I surely can modify entity bean code, but it is EJB container who throws NoSuchEntityException. Catching it in the client (session) bean is one of the options I've described in my original post.]]></description>
        

        <pubDate>Mon, 04 Oct 2004 10:44:37 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 10:44:37 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 10:44:37 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Konstantin Sobolev</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>multiple solutions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Hi Bruce,<br><br>I can use row-level locks/table locks but I will end up with RemoveExceptions instead of NoSuchEntityException, thus having to invent some remove-fail-retry logic.<br><br>Soft delete won't work at all because after you call B.remove(),...]]></description>
        

        <pubDate>Mon, 04 Oct 2004 10:41:12 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 10:41:12 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 10:41:12 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Konstantin Sobolev</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Is it possible for you to modigy the enititybean code? Then you could catch the NoSuchEntityException and do something more sensible.]]></description>
        

        <pubDate>Mon, 04 Oct 2004 06:39:56 -0400</pubDate>

        

        <jf:creationDate>Mon, 04 Oct 2004 06:39:56 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 04 Oct 2004 06:39:56 -0400</jf:modificationDate>
        <jf:date>Oct 4, 2004</jf:date>
        <jf:author>Paul Maessen</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>multiple solutions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[1. Increasing the isolation level should cause some control as well as using &quot;select for update&quot; to acquire row level locks.<br><br>2. A non-J2EE way to solve this is to lock objects either via db or a lock table. This would stop clients from...]]></description>
        

        <pubDate>Sun, 03 Oct 2004 21:37:05 -0400</pubDate>

        

        <jf:creationDate>Sun, 03 Oct 2004 21:37:05 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 03 Oct 2004 21:37:05 -0400</jf:modificationDate>
        <jf:date>Oct 3, 2004</jf:date>
        <jf:author>bruce goldstein</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[In this particular case I can catch this exception and continue processing. But the pattern<br>-find the bean<br>-call it's methods<br>is very common, and carefully catching NoSuchEntityException is not an option. I understand that dozens of our session...]]></description>
        

        <pubDate>Sat, 02 Oct 2004 18:01:24 -0400</pubDate>

        

        <jf:creationDate>Sat, 02 Oct 2004 18:01:24 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 02 Oct 2004 18:01:24 -0400</jf:modificationDate>
        <jf:date>Oct 2, 2004</jf:date>
        <jf:author>Konstantin Sobolev</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[I think the correct answer depends on your specifics?  Is the disappearing bean required for the operation?  If so, you might want to wrap the NoSuchEntityException and throw something more meaningful.  If it isn't, then you'll need to isolate the...]]></description>
        

        <pubDate>Sat, 02 Oct 2004 12:34:00 -0400</pubDate>

        

        <jf:creationDate>Sat, 02 Oct 2004 12:34:00 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 02 Oct 2004 12:34:00 -0400</jf:modificationDate>
        <jf:date>Oct 2, 2004</jf:date>
        <jf:author>Paul Ste. Marie</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Concurrency and Entity EJBs</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29180</link>

        

        
            <description><![CDATA[Hi all,<br><br>What is the correct way to deal with the following problem:<br>Let's say we have 2 clients, C1 and C2.<br>C1 finds entity bean B<br>C2 removes B<br>C1 calls B.foo() and gets NoSuchEntityException<br><br>Transactions can help, but we're...]]></description>
        

        <pubDate>Sat, 02 Oct 2004 06:37:50 -0400</pubDate>

        

        <jf:creationDate>Sat, 02 Oct 2004 06:37:50 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 02 Oct 2004 06:37:50 -0400</jf:modificationDate>
        <jf:date>Oct 2, 2004</jf:date>
        <jf:author>Konstantin Sobolev</jf:author>
        <jf:replyCount>11</jf:replyCount>
    </item>



</channel>
</rss>

