Mailing-List: contact commits-help@celix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@celix.apache.org
Date: Tue, 27 Jan 2015 06:29:35 +0000 (UTC)
From: "Alexander Broekhuis (JIRA)" <jira@apache.org>
To: celix-commits@incubator.apache.org
Message-ID: <JIRA.12769429.1421959237000.181422.1422340175071@Atlassian.JIRA>
In-Reply-To: <JIRA.12769429.1421959237000@Atlassian.JIRA>
References: <JIRA.12769429.1421959237000@Atlassian.JIRA>
 <JIRA.12769429.1421959237337@arcas>
Subject: [jira] [Assigned] (CELIX-205) RSA Discovery (Configured) bundle
 gets stuck
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alexander Broekhuis reassigned CELIX-205:
-----------------------------------------

    Assignee: Alexander Broekhuis

> RSA Discovery (Configured) bundle gets stuck
> --------------------------------------------
>
>                 Key: CELIX-205
>                 URL: https://issues.apache.org/jira/browse/CELIX-205
>             Project: Celix
>          Issue Type: Bug
>          Components: Remote Service Admin
>         Environment: REV 1652984
>            Reporter: Daniel Parker
>            Assignee: Alexander Broekhuis
>            Priority: Blocker
>
> Under certain situations, the apache_celix_rsa_discovery_configured bundle will get stuck somehow and attempts to connect to it to get the list of registered endpoints will time out.  When this happens, the bundle cannot be stopped from the shell (and the apache_celix_rs_topology_manager and apache_celix_remote_service_admin_http bundles have similar problems)
> This is difficult to reproduce.  Sometimes the bundle runs fine for a short time after the program is started and then it breaks (perhaps after endpoints or proxies are accessed).  Other times the bundle works fine and doesn't get stuck at all.
> The issue will only happen if there is actually a remote that is being connected to.


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