[jira] [Commented] (KARAF-4878) Cellar Hazelcast unresponsive when ETH Down
[
https://issues.apache.org/jira/browse/KARAF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760266#comment-15760266
]
Jean-Baptiste Onofré commented on KARAF-4878:
-
I tried a fix that I'm testing now. I should be able to push pretty soon.
> Cellar Hazelcast unresponsive when ETH Down
> ---
>
> Key: KARAF-4878
> URL: https://issues.apache.org/jira/browse/KARAF-4878
> Project: Karaf
> Issue Type: Bug
> Components: cellar-hazelcast
>Affects Versions: 4.0.5
> Environment: Redhat Linux 7.2, CentOS 7.2
>Reporter: Suresh Perumal
>Assignee: Jean-Baptiste Onofré
>Priority: Blocker
>
> Cluster is configured with 2 Nodes. They are up and running.
> As part of fail-over scenario simulation. We are trying to test "ETHERNET
> down scenario" by running "/etc/sysconfig/network-scripts/ifdown eth0"
> command on the first node.
> During this scenario we are shutting down the first node where the ETH is
> down by using monitoring scripts(in-house scripts). The second node(Among
> those two nodes) is kept alive.
> Second Node's Hazelcast is not accessible for more than 15 minutes. We are
> getting bellow exception and no operation related to Hazelcast is working.
> Applications whichever uses hazelcast kept frozen.
> Invocation | 52 - com.hazelcast - 3.5.2 |
> [10.249.50.80]:5701 [cellar] [3.5.2] While asking 'is-executing': Invocation{
> serviceName='hz:impl:mapService', op=PutOperation{unacknowledged-alarm},
> partitionId=165, replicaIndex=0, tryCount=250, tryPauseMillis=500,
> invokeCount=1, callTimeout=6, target=Address[10.249.50.79]:5701,
> backupsExpected=0, backupsCompleted=0}
> java.util.concurrent.TimeoutException: Call Invocation{
> serviceName='hz:impl:mapService',
> op=com.hazelcast.spi.impl.operationservice.impl.operations.IsStillExecutingOperation{serviceName='hz:impl:mapService',
> partitionId=-1, callId=2114, invocationTime=1480511190143, waitTimeout=-1,
> callTimeout=5000}, partitionId=-1, replicaIndex=0, tryCount=0,
> tryPauseMillis=0, invokeCount=1, callTimeout=5000,
> target=Address[10.249.50.79]:5701, backupsExpected=0, backupsCompleted=0}
> encountered a timeout
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:366)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.IsStillRunningService.isOperationExecuting(IsStillRunningService.java:85)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.waitForResponse(InvocationFuture.java:275)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:224)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:456)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.putInternal(MapProxySupport.java:417)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:97)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:87)[52:com.hazelcast:3.5.2]
> at
> com.fujitsu.fnc.emf.fpmplatform.cachemanager.HazelcastCacheManagerMapServiceImpl.addToMap(HazelcastCacheManagerMapServiceImpl.java:87)[209:FPMHazelcastCache:4.1.0.SNAPSHOT]
> at Proxy1897a82c_c032_4a5c_9839_e71cb2af452a.addToMap(Unknown
> Source)[:]
> at
> com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.prepareJSON(FpmConsumerTask.java:151)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHOT]
> at
> com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.run(FpmConsumerTask.java:244)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_66]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4878) Cellar Hazelcast unresponsive when ETH Down
[
https://issues.apache.org/jira/browse/KARAF-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760180#comment-15760180
]
Suresh Perumal commented on KARAF-4878:
---
Any update or Fix planned?
> Cellar Hazelcast unresponsive when ETH Down
> ---
>
> Key: KARAF-4878
> URL: https://issues.apache.org/jira/browse/KARAF-4878
> Project: Karaf
> Issue Type: Bug
> Components: cellar-hazelcast
>Affects Versions: 4.0.5
> Environment: Redhat Linux 7.2, CentOS 7.2
>Reporter: Suresh Perumal
>Assignee: Jean-Baptiste Onofré
>Priority: Blocker
>
> Cluster is configured with 2 Nodes. They are up and running.
> As part of fail-over scenario simulation. We are trying to test "ETHERNET
> down scenario" by running "/etc/sysconfig/network-scripts/ifdown eth0"
> command on the first node.
> During this scenario we are shutting down the first node where the ETH is
> down by using monitoring scripts(in-house scripts). The second node(Among
> those two nodes) is kept alive.
> Second Node's Hazelcast is not accessible for more than 15 minutes. We are
> getting bellow exception and no operation related to Hazelcast is working.
> Applications whichever uses hazelcast kept frozen.
> Invocation | 52 - com.hazelcast - 3.5.2 |
> [10.249.50.80]:5701 [cellar] [3.5.2] While asking 'is-executing': Invocation{
> serviceName='hz:impl:mapService', op=PutOperation{unacknowledged-alarm},
> partitionId=165, replicaIndex=0, tryCount=250, tryPauseMillis=500,
> invokeCount=1, callTimeout=6, target=Address[10.249.50.79]:5701,
> backupsExpected=0, backupsCompleted=0}
> java.util.concurrent.TimeoutException: Call Invocation{
> serviceName='hz:impl:mapService',
> op=com.hazelcast.spi.impl.operationservice.impl.operations.IsStillExecutingOperation{serviceName='hz:impl:mapService',
> partitionId=-1, callId=2114, invocationTime=1480511190143, waitTimeout=-1,
> callTimeout=5000}, partitionId=-1, replicaIndex=0, tryCount=0,
> tryPauseMillis=0, invokeCount=1, callTimeout=5000,
> target=Address[10.249.50.79]:5701, backupsExpected=0, backupsCompleted=0}
> encountered a timeout
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:366)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.IsStillRunningService.isOperationExecuting(IsStillRunningService.java:85)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.waitForResponse(InvocationFuture.java:275)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:224)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:456)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.putInternal(MapProxySupport.java:417)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:97)[52:com.hazelcast:3.5.2]
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.java:87)[52:com.hazelcast:3.5.2]
> at
> com.fujitsu.fnc.emf.fpmplatform.cachemanager.HazelcastCacheManagerMapServiceImpl.addToMap(HazelcastCacheManagerMapServiceImpl.java:87)[209:FPMHazelcastCache:4.1.0.SNAPSHOT]
> at Proxy1897a82c_c032_4a5c_9839_e71cb2af452a.addToMap(Unknown
> Source)[:]
> at
> com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.prepareJSON(FpmConsumerTask.java:151)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHOT]
> at
> com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.run(FpmConsumerTask.java:244)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_66]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15759048#comment-15759048 ] Dariush Amiri commented on KARAF-4895: -- Thank you. I really appreciate the prompt response on this issue. > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15759020#comment-15759020 ] Dariush Amiri commented on KARAF-4895: -- That was another thing I realized when I tried to build Karaf locally. I couldn't because of the missing snapshot version of gogo. Then I tried to clone felix and build that and it didn't build. It seems like the way things are right now 4.1.0-SNAPSHOT is too unstable to use. Can we at least revert to a non-snapshot version of gogo? > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4895. --- Resolution: Won't Fix Fix Version/s: (was: 4.1.0) will be gone as soon as a newer version of Karaf 4.1.0 is available in the snapshot repo. Unfortunately right now it's missing the latest snapshot version for gogo shell > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758594#comment-15758594 ] Achim Nierbeck edited comment on KARAF-4895 at 12/18/16 10:39 AM: -- Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0. Seems to be some transitive dependency in that feature list. The issue is, the latest version available from the snapshot Repo still references 4.4.0 in it's feature file for Pax Web 4.4.0 while your own application already references 6.0.0 see [latest available feature descriptor|https://repository.apache.org/content/groups/snapshots-group/org/apache/karaf/features/standard/4.1.0-SNAPSHOT/standard-4.1.0-20161206.084410-264-features.xml] was (Author: achim_nierbeck): Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0. Seems to be some transitive dependency in that feature list. > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758594#comment-15758594 ] Achim Nierbeck edited comment on KARAF-4895 at 12/18/16 10:20 AM: -- Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0. Seems to be some transitive dependency in that feature list. was (Author: achim_nierbeck): Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0 > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758594#comment-15758594 ] Achim Nierbeck commented on KARAF-4895: --- Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0 > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-4895: - Assignee: Achim Nierbeck > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4895: -- Fix Version/s: 4.1.0 > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4895: -- Component/s: karaf-webcontainer > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
