Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CE6E1882A for ; Wed, 24 Jun 2015 06:18:43 +0000 (UTC) Received: (qmail 61461 invoked by uid 500); 24 Jun 2015 06:18:43 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 61381 invoked by uid 500); 24 Jun 2015 06:18:42 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 61263 invoked by uid 99); 24 Jun 2015 06:18:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2015 06:18:42 +0000 Date: Wed, 24 Jun 2015 06:18:42 +0000 (UTC) From: "Jens Behrens (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CAMEL-8895) camel-swagger component throws exception, when multiple different camel-contexts in jmx MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-8895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598923#comment-14598923 ] Jens Behrens edited comment on CAMEL-8895 at 6/24/15 6:18 AM: -------------------------------------------------------------- But actually shouldn't it be possible to deploy different (and other applications) of older camel-version within the same tomcat? I didn't want to use camel-swagger in the other application that broke my camel-swagger webapp. was (Author: jens.behrens): But actually should it be possible to deploy different (and other applications) of older camel-version within the same tomcat? I didn't want to use camel-swagger in the other application that broke my camel-swagger webapp. > camel-swagger component throws exception, when multiple different camel-contexts in jmx > --------------------------------------------------------------------------------------- > > Key: CAMEL-8895 > URL: https://issues.apache.org/jira/browse/CAMEL-8895 > Project: Camel > Issue Type: Bug > Components: camel-swagger > Affects Versions: 2.15.1 > Environment: Linux, Tomcat 7 > Reporter: Jens Behrens > > When deploying multiple camel-contexts (in different wars!) to a tomcat and one of the camel-contexts is e.g. of version 2.13.0, the camel-context that uses camel-swagger throws following exception when accessing /api-docs. > Additionally it is not possible to deploy 2 camel-swagger using webapps, because only one set of rest-methods (of one of the deployed contexts!) are exported via /api-docs. > {code} > javax.servlet.ServletException: Servlet execution threw an exception > org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44) > root cause > javax.management.MBeanException: Operation dumpRestsAsXml not in ModelMBeanInfo > javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:961) > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > org.apache.camel.component.swagger.DefaultCamelSwaggerServlet.getRestDefinitions(DefaultCamelSwaggerServlet.scala:49) > org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:168) > org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:98) > javax.servlet.http.HttpServlet.service(HttpServlet.java:621) > javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44) > root cause > javax.management.ServiceNotFoundException: Operation dumpRestsAsXml not in ModelMBeanInfo > javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:961) > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > org.apache.camel.component.swagger.DefaultCamelSwaggerServlet.getRestDefinitions(DefaultCamelSwaggerServlet.scala:49) > org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.renderResourceListing(RestSwaggerApiDeclarationServlet.scala:168) > org.apache.camel.component.swagger.RestSwaggerApiDeclarationServlet.doGet(RestSwaggerApiDeclarationServlet.scala:98) > javax.servlet.http.HttpServlet.service(HttpServlet.java:621) > javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > org.apache.camel.component.swagger.RestSwaggerCorsFilter.doFilter(RestSwaggerCorsFilter.scala:44) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)