Jboss halts when using transaction-attribute not-supported

[kbk]

Env.
Win2k, JDK 1.4.x
JBossweb 3.0.6
Firebird 1.x/MySQL 4.x

Scenario:
- 1 Session bean using 4 entity beans
- All beans are using container managed transactions, incl. the session bean.
- The method (entry point) in the session bean has the transaction property set
to 'Required' and this method is using different finder methods on the entity
beans and creating instances of the 4 different entities.

The entity beans have the following transaction properties;
- All finder methods have the transaction attribute set to 'Supports'
- 3 of the entites have their the transaction attribute in the ejbCreate
methods set to 'Required'
- 1 of the entites have the transaction attribute in the ejbCreate
methods set to 'NotSupported'. This entity is for logging purpose only, and thus
even if
the transaction fails, all logging done in the process must not be rolled back
-> transaction attribute set to 'Not Supported'.

Problem;
The method (with transaction attr='Required') in the session bean is called and
it is successfully creating the entity beans with the transaction attribute in
ejbCreate set to 'Required'. When it tries to create the entity bean with the
transaction attribute in ejbCreate set to 'NotSupported', the whole process is
halted and remains hanging for 5 minutes before the transaction gets a timeout
and is rolled back. This is not the kind of behaviour expected. According to the
EJB spec the transaction should be suspended while the non- transactional entity
is created and then resumed after the creation -> leaving the log entries
persisted to the database even if the transaction should fail.

Anybody seen this behaviour before, any suggestions ??

[julien1]

test

[juhalindfors]

"For entity beans that use EJB 2.0 container-managed persistence, only the Required,
RequiresNew,or Mandatory transaction attributes should be used for the methods defined in the
bean.s component interface [...] Containers may optionally support the use of the NotSupported, Supports, and Never transaction attributes for the methods of entity beans with container-managed
persistence. However, entity beans with container-managed persistence that use these transaction
attributes will not be portable.


The behavior of JBossCMP engine without a transaction context is unspecified and not supported. In your case, RequiresNew should work for the logging behavior.

-- Juha

[kbk]

Hi Juha,

Thanks, will try that...