Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9362C200C6E for ; Mon, 8 May 2017 08:56:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9202B160BCA; Mon, 8 May 2017 06:56:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D61E5160B99 for ; Mon, 8 May 2017 08:56:08 +0200 (CEST) Received: (qmail 19047 invoked by uid 500); 8 May 2017 06:56:07 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 19035 invoked by uid 99); 8 May 2017 06:56:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 May 2017 06:56:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 487E5C132E for ; Mon, 8 May 2017 06:56:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id dnRkS5m0vIBp for ; Mon, 8 May 2017 06:56:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 85EB55FDC4 for ; Mon, 8 May 2017 06:56:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 933DFE07D6 for ; Mon, 8 May 2017 06:56:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2792F21DF7 for ; Mon, 8 May 2017 06:56:04 +0000 (UTC) Date: Mon, 8 May 2017 06:56:04 +0000 (UTC) From: "Dennis Kieselhorst (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-6465) Facing WSDL end point URL cache issue in CXF (2.7.7 as well as in 3.1.0) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 08 May 2017 06:56:09 -0000 [ https://issues.apache.org/jira/browse/CXF-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000348#comment-16000348 ] Dennis Kieselhorst commented on CXF-6465: ----------------------------------------- 3.1.11 > Facing WSDL end point URL cache issue in CXF (2.7.7 as well as in 3.1.0) > ------------------------------------------------------------------------ > > Key: CXF-6465 > URL: https://issues.apache.org/jira/browse/CXF-6465 > Project: CXF > Issue Type: Bug > Components: Services > Affects Versions: 2.7.7, 3.1 > Environment: PROD > Reporter: Manikandan > Priority: Critical > Attachments: pom.xml > > > We are facing an issue while using CXF framework in our application, where CXF is caching the webservice wsdl end point URL . Provided more details below with version details, > We are using spring based web application which uses maven build. To connect to the OSB services, we are using CXF framework to generate services java-schema jar. Actual issue is happening in clustered & PROD-BCP environment. > Lets say, we have deployed our application into 2 different set of servers, ex. PROD and BCP. Same code base and all configurations are same on both the servers. > 1. Our application is live in PROD servers and the equivalent prod OSB servers url is prodosb.com > 2. From our prod web application if i invoke PROD OSB service (prodosb.com), which use prodosb.com and it works fine. > 3. Now, we are rolling our application to BCP environment > 4. After moving to BCP servers (web app & OSB in bcposb.com), if we invoke the services from our BCP web application, its going to prodosb.com instead of bcposb.com. > 5. If we bounce the web application instance, then its working fine and all the requests goes to specific servers where are active. But we are not supposed to bounce the web application servers, since our application should be live 24/7. > We see that the application is caching the service end point and using the same for further requests. > I have gone through below JIRA tickets & forums, and decided to migrated to newer version 3.1.0, but still facing the same issue. > https://issues.apache.org/jira/browse/CXF-5737 > https://issues.apache.org/jira/browse/CXF-5216 > Can you please help me to resolve this issue? Thanks in advance. > Version Details: > Spring - 3.2.2.RELEASE > Maven - 3.1 (pom - 4.0.0) > CXF - 3.1.0 > NOTE: > Earlier we were using CXF 2.7.7 and thought this would be fixed in latest version and migrated to 3.1.0, but no use. > We are using maven build to generate the CXF jar, attached the pom.xml for the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)