Hi Saminda, I am not able to stop the server using ./airavata-server.sh stop. I am getting following log message and it stays like that. [INFO] Requesting airavata server(s) to stop…
Another suggestion is to have a rolling file logs for the server. That way if user restarts the service, old logs are not lost. Thanks Raminder On Mar 10, 2014, at 11:20 AM, Saminda Wijeratne <[email protected]> wrote: > 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], > > Start the server as a daemon when needed > eg: $./airavata-server.sh start > Stop the server (daemon or otherwise) > eg: $./airavata-server.sh stop > 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 > 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: > Update the integration-test pom to start airavata server [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 >
