You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Raghunandan (Jira)" <ji...@apache.org> on 2021/07/17 02:00:05 UTC
[jira] [Updated] (TOMEE-3776) WebappBeanManager calls to
getInjectionPointBean(injectionPoint) results in
UnsatisfiedResolutionException lot of times
[ https://issues.apache.org/jira/browse/TOMEE-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghunandan updated TOMEE-3776:
-------------------------------
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:*
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/cdi/WebappBeanManager.java]
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 atleast threads will not be blocked.
!image-2021-07-16-18-51-16-158.png!
was:
*Issue :*We are using TomEE1.7.4 and we upgraded to TomEE8.0.6 and we are seeing WebappBeanManager calls getInjectionPointBean results in lot of UnsatisfiedResolutionException.
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:*
[https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/cdi/WebappBeanManager.java]
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 atleast threads will not be blocked.
!image-2021-07-16-18-51-16-158.png!
> WebappBeanManager calls to getInjectionPointBean(injectionPoint) results in UnsatisfiedResolutionException lot of times
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TOMEE-3776
> URL: https://issues.apache.org/jira/browse/TOMEE-3776
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
> Affects Versions: 8.0.6
> Reporter: Raghunandan
> Priority: Major
> Attachments: image-2021-07-16-18-51-16-158.png
>
>
> *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:*
> [https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/cdi/WebappBeanManager.java]
> 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 atleast threads will not be blocked.
> !image-2021-07-16-18-51-16-158.png!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)