Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 30 Apr 2012 14:10:48 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1890451001.9429.1335795048603.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <951417660.12212.1333553484382.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (KARAF-1309) Cellar causes Karaf container to
 freeze if system got network interface changes between container restarts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/KARAF-1309?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 resolved KARAF-1309.
-----------------------------------------

    Resolution: Fixed
   =20
> Cellar causes Karaf container to freeze if system got network interface c=
hanges between container restarts
> -------------------------------------------------------------------------=
---------------------------------
>
>                 Key: KARAF-1309
>                 URL: https://issues.apache.org/jira/browse/KARAF-1309
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.4
>         Environment: Karaf-2.2.6-SNAPSHOT from 20120403, Cellar-2.2.4-SNA=
PSHOT from 20120312
>            Reporter: Alexey Bespaly
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: cellar-3.0.0, cellar-2.2.4
>
>         Attachments: logs.tgz
>
>
> 1. Started 4 Karaf instances and installed Cellar on those=20
> cluster:node-list
>    No. Host Name             Port ID
> *    1 opti.local            5701 opti.local:5701
>      2 opti.local            5702 opti.local:5702
>      3 opti.local            5703 opti.local:5703
>      4 opti.local            5704 opti.local:5704
> opti.local =3D 192.168.1.86
> 2. 1,2 - default group; 3,4 - "group1" (not sure if groups are essential =
here, but were a part of the test case)
> cluster:group-list
>   Node                 Group
>   opti.local:5701      default
>   opti.local:5702      default
>   opti.local:5703      group1
> * opti.local:5704      group1
> 3. Stopped Karaf containers
> 4. Got the VPN client on - tun0 (172.27.210.11) network interface added
> 5. Restarted Karaf containers
>  - the 1st and the 2nd ones seemed to be working fine:
> cluster:node-list
>    No. Host Name             Port ID
> *    1 172.27.210.11         5701 172.27.210.11:5701
>      2 172.27.210.11         5703 172.27.210.11:5703
>      3 172.27.210.11         5702 172.27.210.11:5702
>      4 172.27.210.11         5704 172.27.210.11:5704
>  - the 3rd container got inresponsive:
> karaf@trun> osgi:list
> ...no response....
>  - the 4th shows the following static picture:
> ...skipped...
> [ 211] [Active     ] [Creating    ] [       ] [   60] hazelcast (1.9.4.6)
>                                        Fragments: 213
> [ 212] [Active     ] [Created     ] [       ] [   60] Apache Karaf :: Cel=
lar :: Core (2.2.4.SNAPSHOT)
> [ 213] [Resolved   ] [            ] [       ] [   60] Apache Karaf :: Cel=
lar :: Hazelcast (2.2.4.SNAPSHOT)
>                                        Hosts: 211
> [ 214] [Active     ] [GracePeriod ] [       ] [   60] Apache Karaf :: Cel=
lar :: Config (2.2.4.SNAPSHOT)
> [ 215] [Active     ] [GracePeriod ] [       ] [   60] Apache Karaf :: Cel=
lar :: Features (2.2.4.SNAPSHOT)
> [ 216] [Active     ] [GracePeriod ] [       ] [   60] Apache Karaf :: Cel=
lar :: Bundle (2.2.4.SNAPSHOT)
> [ 217] [Active     ] [Created     ] [       ] [   60] Apache Karaf :: Cel=
lar :: DOSGi (2.2.4.SNAPSHOT)
> [ 218] [Active     ] [Created     ] [       ] [   60] Apache Karaf :: Cel=
lar :: Utils (2.2.4.SNAPSHOT)
> [ 219] [Active     ] [Created     ] [       ] [   60] Apache Karaf :: Cel=
lar :: Shell (2.2.4.SNAPSHOT)
> [ 220] [Active     ] [Created     ] [       ] [   60] Apache Karaf :: Cel=
lar :: Management (2.2.4.SNAPSHOT)
> karaf@trun>=20
>  ...and the status does not get changed over the time
> Could it be that the stored config conflicts with the newly detected one =
and brings such an instability in?
> Logs of 4 Karaf instances are attached.=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira