Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA47110DD2 for ; Tue, 9 Jul 2013 20:33:48 +0000 (UTC) Received: (qmail 81452 invoked by uid 500); 9 Jul 2013 20:33:48 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 81418 invoked by uid 500); 9 Jul 2013 20:33:48 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 81409 invoked by uid 99); 9 Jul 2013 20:33:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 20:33:48 +0000 Date: Tue, 9 Jul 2013 20:33:48 +0000 (UTC) From: "Suresh Marru (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRAVATA-882) Tomcat port configuration accessing problem in certain older tomcat 7 version 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/AIRAVATA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703748#comment-13703748 ] Suresh Marru commented on AIRAVATA-882: --------------------------------------- Good find Viknes. Will this patch work with latest tomcat also, I mean do we need to use ServerSettings.getTomcatPort(protocol) for older versions or will ApplicationSettings.getSetting("port") work with all 7+ versions of tomcat? > Tomcat port configuration accessing problem in certain older tomcat 7 version > ----------------------------------------------------------------------------- > > Key: AIRAVATA-882 > URL: https://issues.apache.org/jira/browse/AIRAVATA-882 > Project: Airavata > Issue Type: Bug > Reporter: Viknes Balasubramanee > Priority: Minor > Attachments: Airavata-882.patch > > > The port number of tomcat was not accessible during the server startup and hence the configuration database table did not have all the entries. > Below is the exception that occurs > [INFO] Registry service URL - http://localhost:8080/airavata-server/services/RegistryService?wsdl > Exception in thread "Thread-8" java.lang.NoSuchMethodError: org.apache.coyote.http11.Http11Protocol.getSslImplementationName()Ljava/lang/String; > at org.apache.airavata.common.utils.ServerSettings.getTomcatPort(ServerSettings.java:152) > at org.apache.airavata.common.utils.ServiceUtils.generateServiceURLFromConfigurationContext(ServiceUtils.java:67) > at org.apache.airavata.wsmg.msgbox.MsgBoxServiceLifeCycle$1.run(MsgBoxServiceLifeCycle.java:118) > Exception in thread "Thread-13" java.lang.NoSuchMethodError: org.apache.coyote.http11.Http11Protocol.getSslImplementationName()Ljava/lang/String; > at org.apache.airavata.common.utils.ServerSettings.getTomcatPort(ServerSettings.java:152) > at org.apache.airavata.common.utils.ServiceUtils.generateServiceURLFromConfigurationContext(ServiceUtils.java:67) > at org.apache.airavata.wsmg.broker.BrokerServiceLifeCycle$1.run(BrokerServiceLifeCycle.java:157) > Exception in thread "Thread-27" java.lang.NoSuchMethodError: org.apache.coyote.http11.Http11Protocol.getSslImplementationName()Ljava/lang/String; > at org.apache.airavata.common.utils.ServerSettings.getTomcatPort(ServerSettings.java:152) > at org.apache.airavata.common.utils.ServiceUtils.generateServiceURLFromConfigurationContext(ServiceUtils.java:67) > at org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton$1.run(WorkflowInterpretorSkeleton.java:186) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira