[
http://jira.jboss.com/jira/browse/JBAS-3159?page=comments#action_12349174 ]
cbrettin commented on JBAS-3159:
--------------------------------
This was real, I discovered later 9yed there was another config issue, but it wasn't
causal - I've just been too busy to look into it) - so if anyone else has it: you are
not imagining it.
The problem is solved in 4.0.5 JBAS-3341 apparently described this issue in a way that got
it fixed.
messages dispatch to MDBeans started before referenced CMP beans are
properly initialised
-----------------------------------------------------------------------------------------
Key: JBAS-3159
URL:
http://jira.jboss.com/jira/browse/JBAS-3159
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.4.CR2
Environment: All (java logic)
Reporter: cbrettin
Since 4.0.4RC1 EjbModule startup has been changed (v 1.69) to start up persistence of
entity beans after all other startup calls have been made (to address JBAS-993).
MDBean start up in the first phase also causes endpoint activation (via the proxy factory
startup) - allowing message flow to start.
As a result the MDBean can be called before Entity persistence in the same module is
properly started leading to intermittent illegal state exceptions when messsge processing
causes calls to the unready entity beans.
A solution analogous to the entity startup changes is probably needed ensuring that
endpoint activation occurs last (after persistence startup).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira