Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
8.0.6
-
None
Description
Issue We are using TomEE1.7.4 and we are trying to upgrade to TomEE8.0.6.
We are seeing WebappBeanManager calls getInjectionPointBean results in lot of UnsatisfiedResolutionException where in TomEE.1.7.4 there are no such exceptions.
UnsatisfiedResolutionException is not an issue but leads to thread blocking issue due to an issue in openwebbeans.
Our functionality works fine as the it finds the bean somewhere else but we get a performance issue due to repeated UnsatisfiedResolutionException thrown by openwebbeans code.
Observation:
We observed WebappBeanManager code is making some redundant call to with parentBm.getInjectionResolver().getInjectionPointBean(injectionPoint) resulting some in UnsatisfiedResolutionException but application works fine but we get in to thread blocking issues due to this exception from openwebbeans.
Openwebbeans issue (https://issues.apache.org/jira/browse/OWB-1388)* :
It has a instance variable with making System.Property call which calls java.util.HashTable (synchronized get method) causing threads to block.
private final String lineSeparator = System.getProperty("line.separator");
Change requested:
Either fix the WebappBeanManager class so that UnsatisfiedResolutionException is avoided when everything works fine.
Or
Once OWB-1388 is fixed please patch with TomEE 8.0.6. If exception can't be avoided then at at least threads will not be blocked causing a significant performance issue.
Attachments
Attachments
Issue Links
- relates to
-
OWB-1388 ViolationMessageBuilder has System.getProperty call as instance variable rather than static variable
- Open