Issue 11001
Separate web app and thread pool to run in separate JVMs
11001
Reporter: kbraak
Assignee: kbraak
Type: Improvement
Summary: Separate web app and thread pool to run in separate JVMs
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-03-20 14:38:26.899
Updated: 2013-01-15 14:40:03.336
Resolved: 2012-04-02 15:03:03.738
Description: Have a functioning version of the HIT "as it is. The only difference is that it will have processes running in different JVM instances for the web app and thread pool.
This means that initially there won't exist any interaction with the MetadataSync service.]]>
Author: kbraak@gbif.org
Created: 2012-04-02 14:41:01.754
Updated: 2012-04-02 14:41:01.754
Fede has made good progress on this issue. The web app and harvest-service (thread pool) now run in separate JVMs. He has modified the projects to use a Maven profile, automatically built via Jenkins, and deployed to staging using shell scripts.
Provided everything is built successfully, the application is deployed to http://staging.gbif.org:8080/harvest-webapp/