I am able to control the result of the web app build. If another process (like Tomcat) is tethered to 8080 port, then the Webapp will not build. If I kill whatever is tethered to 8080 port (or reassign it to 8081), then the webapp does build successfully. IOW, webapp will only build if 8080 is open. OK, so that resolves the build. Now, what about Tomcat? I need Tomcat to run in order for the webapp service to be up. So now that I have reassigned Tomcat to 8081, it is up and running. And accoording to the message at the completion of the webapp build instance, the web app is up too (see below).
However, when I navigate my browser to localhost:8080, it gives me this error:
HTTP ERROR: 503.
Problem accessing /. Reason:
Powered by Jetty://
End-of-build message copied from SSH terminal:
2012-03-30 17:26:36.375:INFO::Started SocketConnector@0.0.0.0:8080 STARTING
= Your OneBusAway instance has started. Browse to:
= to see your instance in action.
= When you are finished, press return to exit gracefully...