Hi all, I have 2 clients that call a stateful session bean's method. Inside this method the session bean starts a transaction and then retrieves/update an entity bean.
The behaviour of the method differs depending the client that called it. In particular, for Client 1 the method performs this steps: 1) retrieves the entity bean (with findByPrimaryKey()) 2) sleeps for 45 seconds 3) updates the entity bean For Client 2 the steps are: 1) retrieves the entity bean (with findByPrimaryKey()) 2) updates IMMEDIATELY the entity bean I'm doing some tests about competion among these 2 clients. I run Client 1 and after few seconds I run Client 2. I expect that Client 2 ends before Client 1 but the strange thing is that Client 2 waits till the end of the sleep(45) of Client 1 !! I'm non able to understand this behaviour :-( I'd have understood it if there had been a <row-locking> tag with TRUE value in the defaults section of standardjbosscmp-jdbc.xml file, but this tag is set to FALSE. | <defaults> | <datasource>java:/PostgresDS</datasource> | <datasource-mapping>PostgreSQL</datasource-mapping> | | <create-table>false</create-table> | <remove-table>false</remove-table> | <read-only>false</read-only> | <read-time-out>300000</read-time-out> | <row-locking>false</row-locking> | Can anyone give me an explanation ? Many thanks Moreno View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843614#3843614 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843614 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
