Viknes Balasubramanee created AIRAVATA-882:
----------------------------------------------
Summary: 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
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
