You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Awasum Yannick (JIRA)" <ji...@apache.org> on 2019/02/15 15:41:00 UTC
[jira] [Commented] (FINERACT-625) Unable to deploy .war on Tomcat 7
[ https://issues.apache.org/jira/browse/FINERACT-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769425#comment-16769425 ]
Awasum Yannick commented on FINERACT-625:
-----------------------------------------
[~hemkesh041] Have you been able to resolve this? Fineract 1.X does not have a UI of its own. If you want a UI, see: https://github.com/openMF/community-app
> Unable to deploy .war on Tomcat 7
> ---------------------------------
>
> Key: FINERACT-625
> URL: https://issues.apache.org/jira/browse/FINERACT-625
> Project: Apache Fineract
> Issue Type: Bug
> Components: Build
> Environment: Ubuntu 16.04 on AWS EC2 T2 Large Instance
> Java 1.8
> MySQL Server 5.6
> Tomcat 7.0.86
> Reporter: Hemkesh Vijaya Kumar
> Priority: Major
> Labels: build
> Attachments: image-2018-05-11-15-04-24-126.png
>
>
> Using an Ubuntu 16.04, AWS T2 Large server to host a Java Webapp (Fineract) on Tomcat
>
> I followed the instructions to install fineract on Ubuntu as explained in the following site:
> [https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Installation+on+Ubuntu+Server]
> I was also able to build a .war file from the following repository:
> [https://github.com/apache/incubator-fineract]
> Moved the .war file to webapps folder in tomcat directory along with giving it 755 permission
>
> When accessing the hosted webapp remotely, The following error is appearing:
> !image-2018-05-11-15-04-24-126.png!
>
> Accessing the Tomcat Server Log files, the following is shown:
> May 10, 2018 2:27:01 PM org.apache.catalina.core.StandardService initInternal
> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-443]]
> org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-443]]
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
> at org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:820)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:642)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:667)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:253)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)
> Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
> at org.apache.catalina.connector.Connector.initInternal(Connector.java:982)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 12 more
> Caused by: java.net.BindException: Permission denied (Bind failed) <null>:443
> at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:413)
> at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:650)
> at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
> at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
> at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
> ... 13 more
> Caused by: java.net.BindException: Permission denied (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at java.net.ServerSocket.<init>(ServerSocket.java:237)
> at java.net.ServerSocket.<init>(ServerSocket.java:181)
> at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:136)
> at sun.security.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:113)
> at sun.security.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:87)
> at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:219)
> at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:400)
> ... 17 more
>
> May 10, 2018 2:27:01 PM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
> May 10, 2018 2:27:01 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 790 ms
> May 10, 2018 2:27:01 PM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
> May 10, 2018 2:27:01 PM org.apache.catalina.core.StandardEngine startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.68 (Ubuntu)
> May 10, 2018 2:27:01 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive /var/lib/tomcat7/webapps/sample.war
> May 10, 2018 2:27:01 PM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
> May 10, 2018 2:27:01 PM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deployment of web application archive /var/lib/tomcat7/webapps/sample.war has finished in 526 ms
> May 10, 2018 2:27:01 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["ajp-bio-8009"]
> May 10, 2018 2:27:01 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 623 ms
> May 10, 2018 2:27:23 PM org.apache.coyote.ajp.AjpMessage processHeader
> SEVERE: Invalid message received with signature 18245
> May 10, 2018 2:27:25 PM org.apache.coyote.ajp.AjpMessage processHeader
> SEVERE: Invalid message received with signature 18245
> May 10, 2018 2:27:25 PM org.apache.coyote.ajp.AjpMessage processHeader
> SEVERE: Invalid message received with signature 18245
> May 10, 2018 2:27:26 PM org.apache.coyote.ajp.AjpMessage processHeader
> SEVERE: Invalid message received with signature 18245
> May 10, 2018 2:28:32 PM org.apache.coyote.ajp.AjpMessage processHeader
> SEVERE: Invalid message received with signature 18245
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)