Blueprint extender may block if blueprint invoked bean methods use mandatory
unsatisfied service references
-----------------------------------------------------------------------------------------------------------
Key: ARIES-60
URL: https://issues.apache.org/jira/browse/ARIES-60
Project: Aries
Issue Type: Bug
Components: Blueprint
Reporter: Valentin Mahrwald
Priority: Minor
ServiceReferenceRecipe.getService uses a Object.wait to wait for unresolved
service references to become available.
If getService is invoke during a Blueprint container invoked method such as a
bean init-method, a bean destroy-method or a bean property setter (etc), this
will block the blueprint extender thread. By default it appears that once the
three configured blueprint threads are blocked in this way, no more work can be
carried out by the blueprint extender (for any blueprint bundle) until the
threads unblock (due to the wait timing out or else).
This was discovered during investigations into ARIES-59. The fix for ARIES-50
will alleviate the problem where optional references are concerned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
