Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Wed, 9 Aug 2017 15:09:00 +0000 (UTC)
From: "Carlos Sierra (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13080045.1497522457000.128710.1502291340101@Atlassian.JIRA>
In-Reply-To: <JIRA.13080045.1497522457000@Atlassian.JIRA>
References: <JIRA.13080045.1497522457000@Atlassian.JIRA> <JIRA.13080045.1497522457555@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CXF-7409) ServiceConstructionException when
 adding JAX-RS application ruins existing applications
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 09 Aug 2017 15:09:04 -0000


    [ https://issues.apache.org/jira/browse/CXF-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120053#comment-16120053 ] 

Carlos Sierra commented on CXF-7409:
------------------------------------

In our case this address is coming from a property on a OSGi service reference. 

We are avoiding it at the moment using a custom destination Factory to detect the conflict before it gets to destroy the server. 
To be honest I did not think having several applications per servlet would be a problem. Would you suggest we spawn a servlet for each of the applications? If you think CXF does not support other way I will refactor and make sure there is only one application per servlet (if no other considerations apply)

I will try and find some time to create a test for you. I need to get acquainted with your tree. But with you comments I guess you encouraged me to change our implementation and completely work around this problem from the root.  


> ServiceConstructionException when adding JAX-RS application ruins existing applications
> ---------------------------------------------------------------------------------------
>
>                 Key: CXF-7409
>                 URL: https://issues.apache.org/jira/browse/CXF-7409
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.1.10
>            Reporter: Carlos Sierra
>
> if a new application conflicts with
> an existing one, an Exception:
> ---
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException:
> There is an endpoint already running on /test-application.
>       at
> org.apache.cxf.jaxrs.JAXRSBindingFactory.addListener(JAXRSBindingFactory.java:86)
>       at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:123)
>       at
> org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:206)
> ---
> is raised, which is expected. The problem is that the already existing
> application ceases to work in the bus.
> Following [~sergeyb]'s advice I tried removing 
> {code:java}
> server.destroy()
> {code}
> from the 
> {code:java}
> catch(RuntimeException e) {}
> {code}
> block in JAXRSServerFactoryBean's create method. However there is a comment saying that that invocation is there to prevent leaks. Also, invocations to server.destroy() in other moments don't affect other existing applications in the bus. 


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