On Tue, Jun 8, 2010 at 2:00 PM, Christoph Zwerschke <email@example.com>
Am 07.06.2010 22:00 schrieb Steve Schwarz:
> We are looking to run multiple Webware instances from a single WebwareJust out of curiosity, why do you want to do that? I'm usually running
> directory/checkout and can do so by providing configuration differences
> via command line args.
different instances from different working dirs only.
We'd like to simplify our deployment. Now our admins have to install Webware multiple times for each appserver instance on multiple servers. It would be easier to just deploy once and have all instance refer to that one check out.
We also see better performance running with a pool of single threaded appservers instead of using the ThreadedAppServer. So we are looking to substantially increase the number of AppServers running and don't want to setup dozens of Webware directories that only differ in port number and some logging parameters.
> each adapter: ...
> But I noticed that ThreadedAppServer.addSocketHandler() creates files
> like http.address and adapter.address containing the address:port for
> Can anyone explain the purpose? Trying to stop running multipleI think they are only used as a way to communicate the appserver port to
> appservers on the same address/port? If so the port will already be
> bound so the appserver will fail...
some of the adapters, e.g. the CGIAdapter.
We're only using the HTTP adapter for our current tests and it didn't seem to care if that file exists. So I didn't look any further...
If you start a second instance, the file should be overwritten with a
warning, doesn't this work for you?
If you don't want this, you can set a different name for it in the 2nd
instance via the AppServer setting "AddressFiles", e.g. '%s.address2'
Thanks I didn't see that config. We'll just specify it also on the command line and now I won't have to override addSocketHandler() anymore