We should be able to. Should it be a server implementation level configuration? If so can be put it in the server properties?
On Mon, Mar 10, 2014 at 10:20 AM, Lahiru Gunathilake <[email protected]>wrote: > Hi Saminda, > > Can we support TThreadPoolServer and make it configurable ? > > Regards > Lahiru > > > On Mon, Mar 10, 2014 at 8:54 AM, Saminda Wijeratne <[email protected]>wrote: > >> A few updates to the standalone server startup [1], >> >> >> 1. Start the server as a daemon when needed >> - eg: $./airavata-server.sh start >> 2. Stop the server (daemon or otherwise) >> - eg: $./airavata-server.sh stop >> 3. What servers to start are mentioned in the server properties file >> ("servers=<server1><server2>..."). The servers will start in the given >> order >> - eg: servers=apiserver,orchestrator >> 4. Command line parameters of the form "--<arg-key>=<arg-value>" >> updates or overrides existing server configs. >> - eg: $./airavata-server.sh --servers=orchestrator >> --myproxy.user=ogce --myproxy.pass=mpass >> >> >> TODO: >> >> 1. Update the integration-test pom to start airavata server [2] >> 2. The windows batch script needs to be updated. >> >> >> >> 1. https://issues.apache.org/jira/browse/AIRAVATA-1045 >> 2. https://issues.apache.org/jira/browse/AIRAVATA-1054 >> > > > > -- > System Analyst Programmer > PTI Lab > Indiana University >
