Doubts in Serializing the Session bean methods

[Senthil Kumar]

I have read this umpteen times and but never seem to make sense of it.
what they mean here by saying 'Serializing'. Is it the one regarding persisting into a secondary storage or sequencing the calls.

I was thinking that container is the one which gives us the Session object to work with it. But how does an another client can try to access the same session object which is still executing a method or the same client try to run a another method.

Is this what they mean here or what else.

"Clients are not allowed to make concurrent calls to a stateful session object. If a client-invoked business method is in progress on an instance when another client-invoked call, from the same or different client,
arrives at the same instance of a stateful session bean class, if the second client is a client of the bean�s business interface, the concurrent invocation may result in the second client receiving the javax.ejb.ConcurrentAccessException"

[Shivani Chandna]

This is related to sequencing of calls.

I can have a standalone java client having a SFSB Object and spawning threads and in each thread calling the same/different method of the SFSB Object.
[ June 18, 2007: Message edited by: Shivani Chandna ]