Hi all,
I've just downloaded the latest release 3.2.2. The release 3.2.1 had a problem with commit option c unable to passivate due to ctx lock. I've tried to use 3.2.2 to see if this problem is fixed. It seems like it got worse. One thing I noticed is with commit option c jboss returns or destroys the bean before saving the state in memory. If we use create() it creates entries in database. Right after create assign any fields using set methods on remote interface and exit your session bean. Those settings will not be saved to database. The behavior is not the same with commit option A or B. This is a very big bug. By the way, we use ejb 1.1 with 2.0 descriptor and declare cmp-version=1.x in ejb-jar.xml descriptor.
I appreciate the response,
Misak
I've just downloaded the latest release 3.2.2. The release 3.2.1 had a problem with commit option c unable to passivate due to ctx lock. I've tried to use 3.2.2 to see if this problem is fixed. It seems like it got worse. One thing I noticed is with commit option c jboss returns or destroys the bean before saving the state in memory. If we use create() it creates entries in database. Right after create assign any fields using set methods on remote interface and exit your session bean. Those settings will not be saved to database. The behavior is not the same with commit option A or B. This is a very big bug. By the way, we use ejb 1.1 with 2.0 descriptor and declare cmp-version=1.x in ejb-jar.xml descriptor.
I appreciate the response,
Misak
This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
