You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Pavel Drasil (JIRA)" <ji...@apache.org> on 2008/11/03 11:09:05 UTC
[jira] Created: (SM-1672) BeanEndpoint: lazy initialization of the
"beanInfo" attribute in getBeanInfo() is not thread-safe
BeanEndpoint: lazy initialization of the "beanInfo" attribute in getBeanInfo() is not thread-safe
-------------------------------------------------------------------------------------------------
Key: SM-1672
URL: https://issues.apache.org/activemq/browse/SM-1672
Project: ServiceMix
Issue Type: Bug
Components: servicemix-bean
Affects Versions: servicemix-bean-2008.01
Reporter: Pavel Drasil
Lazy initialization of the "beanInfo" attribute in the BeanEndpoint.getBeanInfo() method is not thread-safe. It can happen (and it happens to me quite often:-) ), that the second invocation of the getBeanInfo() method sees the attribute not being null and returns its value, causing the exchange processing to fail because the BeanInfo object is not yet properly initialized (the introspect() method is not finished yet).
There are various solutions to this issue, the simplest one is marking the BeanEndpoint.getBeanInfo() method synchronized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-26) BeanEndpoint: lazy initialization of
the "beanInfo" attribute in getBeanInfo() is not thread-safe
Posted by "Pavel Drasil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Drasil updated SMXCOMP-26:
--------------------------------
Affects Version/s: servicemix-bean-2009.01
> BeanEndpoint: lazy initialization of the "beanInfo" attribute in getBeanInfo() is not thread-safe
> -------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-26
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-26
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-bean
> Affects Versions: servicemix-bean-2008.01, servicemix-bean-2009.01
> Reporter: Pavel Drasil
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Lazy initialization of the "beanInfo" attribute in the BeanEndpoint.getBeanInfo() method is not thread-safe. It can happen (and it happens to me quite often:-) ), that the second invocation of the getBeanInfo() method sees the attribute not being null and returns its value, causing the exchange processing to fail because the BeanInfo object is not yet properly initialized (the introspect() method is not finished yet).
> There are various solutions to this issue, the simplest one is marking the BeanEndpoint.getBeanInfo() method synchronized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.