tomcat RA: remain starting and fails

Using the latest RA tomcat the script start does not return and hangs same behavior using ocf:heartbeat:tomcat:
tomcat 9
OCF_RESKEY_catalina_base=/usr/share/tomcat
OCF_RESKEY_catalina_home=/usr/share/tomcat

/usr/lib/ocf/resource.d/heartbeat/tomcat start
INFO: validate_all_tomcat[tomcat]

systemctl status tomcat.service
```# systemctl status tomcat.service --no-pager
● tomcat.service - Apache Tomcat Web Application Container
Loaded: loaded (/usr/lib/systemd/system/tomcat.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 2019-10-31 19:45:06 CET; 5s ago
Main PID: 7882 (java)
Tasks: 49 (limit: 576)
CGroup: /system.slice/tomcat.service
└─7882 /usr/lib64/jvm/jre/bin/java -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr…rt

Okt 31 19:45:07 tomcat1 server[7882]: 31-Oct-2019 19:45:07.488 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
Okt 31 19:45:07 tomcat1 server[7882]: 31-Oct-2019 19:45:07.488 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.21]
Okt 31 19:45:07 tomcat1 server[7882]: 31-Oct-2019 19:45:07.866 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no…e.
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.120 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no…e.
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.472 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no…e.
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.653 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no…e.
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.833 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no…e.
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.840 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.853 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
Okt 31 19:45:08 tomcat1 server[7882]: 31-Oct-2019 19:45:08.870 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [1,427] milliseconds

Start with /usr/lib/ocf/resource.d/heartbeat/tomcat and reproduce the reported start command while checking systemctl status tomcat.service. Trace why the resource-agent start operation does not return after Tomcat reports server startup; done means the command returns successfully while the service remains active.

Written by the indexing model from the issue text.