[jira] [Commented] (ARIES-1815) ConcurrentModificationException in TopologyManagerImport.unImportForGoneEndpoints

2018-07-02 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARIES-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530438#comment-16530438
 ] 

ASF subversion and git services commented on ARIES-1815:


Commit 729eb6413fbc3e307e92fad77c3c1d44c3baa3b0 in aries-rsa's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=aries-rsa.git;h=729eb64 ]

ARIES-1815 - Copy set to avoid concurrent modification


> ConcurrentModificationException in 
> TopologyManagerImport.unImportForGoneEndpoints
> -
>
> Key: ARIES-1815
> URL: https://issues.apache.org/jira/browse/ARIES-1815
> Project: Aries
>  Issue Type: Improvement
>  Components: Remote Service Admin
>Affects Versions: rsa-1.12.0
> Environment: Happens in the CXF-DOSGi itests.
>Reporter: Christian Schneider
>Assignee: Christian Schneider
>Priority: Major
> Fix For: rsa-1.13.0
>
>
> org.apache.aries.rsa.topology-manager[org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport]
>  : null
> java.util.ConcurrentModificationException
>  at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
>  at java.util.HashMap$KeyIterator.next(HashMap.java:1466)
>  at 
> org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.unImportForGoneEndpoints(TopologyManagerImport.java:183)
>  at 
> org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.syncronizeImports(TopologyManagerImport.java:127)
>  at 
> org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.access$000(TopologyManagerImport.java:47)
>  at 
> org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport$1.run(TopologyManagerImport.java:119)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARIES-1815) ConcurrentModificationException in TopologyManagerImport.unImportForGoneEndpoints

2018-07-02 Thread Christian Schneider (JIRA) 
Christian Schneider created ARIES-1815:
--

 Summary: ConcurrentModificationException in 
TopologyManagerImport.unImportForGoneEndpoints
 Key: ARIES-1815
 URL: https://issues.apache.org/jira/browse/ARIES-1815
 Project: Aries
  Issue Type: Improvement
  Components: Remote Service Admin
Affects Versions: rsa-1.12.0
 Environment: Happens in the CXF-DOSGi itests.
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: rsa-1.13.0


org.apache.aries.rsa.topology-manager[org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport]
 : null

java.util.ConcurrentModificationException

 at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)

 at java.util.HashMap$KeyIterator.next(HashMap.java:1466)

 at 
org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.unImportForGoneEndpoints(TopologyManagerImport.java:183)

 at 
org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.syncronizeImports(TopologyManagerImport.java:127)

 at 
org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport.access$000(TopologyManagerImport.java:47)

 at 
org.apache.aries.rsa.topologymanager.importer.TopologyManagerImport$1.run(TopologyManagerImport.java:119)

 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1174) Avoid service reference timeout when system bundle is stopping

2018-07-02 Thread Guillaume Nodet (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARIES-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530093#comment-16530093
 ] 

Guillaume Nodet commented on ARIES-1174:


bq. I think the solution would be to use the new {{ext:lifecycle="static"}} 
({{ext}} 1.6 namespace) on the {{reference}} element.  This should destroy the 
{{CamelContext}} when the reference isn't satisfied anymore.

> Avoid service reference timeout when system bundle is stopping
> --
>
> Key: ARIES-1174
> URL: https://issues.apache.org/jira/browse/ARIES-1174
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Affects Versions: blueprint-core-1.1.0
>Reporter: Benno Geißelmann
>Assignee: Guillaume Nodet
>Priority: Major
>
> The default timeout of Blueprint to wait for a service to come is 5 minutes. 
> A problem which comes with the timeout behaviour is, that in some states you 
> don't want to wait for the service. For example if the system bundle is in 
> state "stopping" this timeout will cause that the stopping takes 5 minutes. 
> In my opinion this makes no sense as the container will shutdown so there 
> shouldn't be waited for a service to come.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly

2018-07-02 Thread David Bosschaert (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARIES-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529594#comment-16529594
 ] 

David Bosschaert commented on ARIES-1814:
-

Thanks for offering to help out with this issue [~rotty3000]!

> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in 
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as 
> Import-Package



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ARIES-1814) Solve the start order limitations with SPI Fly

2018-07-02 Thread David Bosschaert (JIRA) 


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

David Bosschaert reassigned ARIES-1814:
---

Assignee: Raymond Augé  (was: David Bosschaert)

> Solve the start order limitations with SPI Fly
> --
>
> Key: ARIES-1814
> URL: https://issues.apache.org/jira/browse/ARIES-1814
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in 
> maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as 
> Import-Package



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)