Hi Gurus,
        Finally I was able to resolve the problem related to this issue.
        Generally the problem was related when ejbStore() was invoked after a call to setXXX() or ejbCreate().(Yes, now I know this is the expected behaviour :-).
        The solution is to use the following:
1. ejbCreate() - <trans-attribute> as 'RequiresNew'
2. setXXX() - <trans-attribute> as 'RequiresNew'
3. ejbStore() - <trans-attribute> as 'Supports'
4. EntityBeans - 'Instance Per Transaction BMP EntityBean'

        The issues I was facing is, after the ejbCreate or ejbStore, the data gets updated in the DB, but the entity beans either gets locked or, the next transaction don't receive the updated entity. This combination makes a commit after the method, plus before the next transaction is called ejbLoad() is also invoked, thus the entity is updated too. So cool, we have a solution.

PHEW!!!

Cheers
Muraly

At 14:20 21/08/2003 +0100, you wrote:
hi,

Try to close all other application like Interactive SQL and so on.
You can check also your Transaction settings.
We have simillar situation sometimes and at the very end the reason
is always the same, locked records, the problem is only to find where :)

maybe it helps...

greetings
adam


-----Ursprüngliche Nachricht-----
Von: Muraly R [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 19. August 2003 11:35
An: [EMAIL PROTECTED]
Betreff: Re: [JBoss-user] ejbStore(): Again!!!


Hi Alex,
        The problem I am facing is after a setXXX() business method in my
entity bean, the call to ejbStore() stays in progress for ever. The point of
failure is when I have inserted a new VO to the DB using the entity bean,
its corresponding ejbStore() is stuck. The exception I am getting is
attached.

I am using CMP

Yes there is only one client, i.e. one thread which initiates the action.

I am using sybase and the Isolation level set is '0'.

Sybase Doc's Defenition:
At isolation level 0, the database server needs only write locks. It makes
use
of these locks to ensure that no two transactions make modifications that
conflict. For example, a level 0 transaction acquires a write lock on a row
before it updates or deletes it, and inserts any new rows with a write lock
already in place.
Level 0 transactions perform no checks on the rows they are reading. For
example, when a level 0 transaction reads a row, it doesn't bother to check
what locks may or may not have been acquired on that row by other
transactions. Since no checks are needed, level 0 transactions are
particularly
fast. This speed comes at the expense of consistency. Whenever they read a
row which is write locked by another transaction, they risk returning dirty
data.

Hope this helps.

Actually the two versions of aour application are running on JOnAs2.4, 'OK'.
One the enxt version we are planning to release on JBoss3.0.7. I never
thought there will be such big diffrence between App. servers
implementation.

Thanks(as usual:-) for the Excellent support
Cheers
Muraly

At 18:55 18/08/2003 +0300, you wrote:

Are there more some info available other than "I have a problem in
ejbStore"?

is it BMP?
does it occur for one client (one thread)?
what is the tx isolation level in the db?
any stacktrace?

alex

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to