[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization

2017-10-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-5521:
---
Fix Version/s: (was: 1.7.12)
   1.7.11

> CommunicationObserver and its MBeans need proper synchronization
> 
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called 
> concurrently by multiple threads. The implementation of 
> {{CommunicationObserver}} doesn't currently use any form of synchronization 
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be 
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As 
> such, further synchronization is also needed in the MBeans to protect 
> concurrent access to shared data.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization

2017-10-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-5521:
---
Fix Version/s: (was: 1.7.10)
   1.7.12

> CommunicationObserver and its MBeans need proper synchronization
> 
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.12
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called 
> concurrently by multiple threads. The implementation of 
> {{CommunicationObserver}} doesn't currently use any form of synchronization 
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be 
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As 
> such, further synchronization is also needed in the MBeans to protect 
> concurrent access to shared data.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization

2017-10-09 Thread Davide Giannella (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella updated OAK-5521:
--
Fix Version/s: (was: 1.7.9)
   1.7.10

> CommunicationObserver and its MBeans need proper synchronization
> 
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.10
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called 
> concurrently by multiple threads. The implementation of 
> {{CommunicationObserver}} doesn't currently use any form of synchronization 
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be 
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As 
> such, further synchronization is also needed in the MBeans to protect 
> concurrent access to shared data.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization

2017-09-11 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-5521:
---
Fix Version/s: 1.7.9

> CommunicationObserver and its MBeans need proper synchronization
> 
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.9
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called 
> concurrently by multiple threads. The implementation of 
> {{CommunicationObserver}} doesn't currently use any form of synchronization 
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be 
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As 
> such, further synchronization is also needed in the MBeans to protect 
> concurrent access to shared data.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization

2017-01-26 Thread Francesco Mari (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Mari updated OAK-5521:

Summary: CommunicationObserver and its MBeans need proper synchronization  
(was: CommunicationObserver and its MBeans needs proper synchronization)

> CommunicationObserver and its MBeans need proper synchronization
> 
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.6
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called 
> concurrently by multiple threads. The implementation of 
> {{CommunicationObserver}} doesn't currently use any form of synchronization 
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be 
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As 
> such, further synchronization is also needed in the MBeans to protect 
> concurrent access to shared data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)