Re: [Wrapper-user] Stopping a JVM, but leaving it around?

[Leif M. <le...@ta...>]

Prashant Reddy wrote:

>Leif,
>  
>
>>    The Wrapper will have no problems having 2 copies of itself running at
>>the same time.
>>    The following is an idea (untested)
>>    
>>
>We use this configuration to run two instances of our server application lot
>of times, I was apprehensive of both instances writing to same .log
>file..but everything seems to be working fine even with one log file.
>If wrapper.port property is deprecated..Does it mean it will not be
>configurable. The default value will be what, 1777+?
>  
>
Maybe deprecated is the wrong word.  It is no longer required.  I kept 
having people ask
about warning caused when they tried to run multiple copies of the 
Wrapper with the same
port.  The socket is only used internally so there is not really any 
reason for the user to have
to specify it.

As of version 3.0.5, the wrapper will use the value of wrapper.port if 
it is specified.
Otherwise if will look for the first available port over port 32000.  I 
use the high number
to avoid possible conflicts with any user defined well known ports.  
This is up in the
range that ports are dynamically pulled from by the system.

There should be no loss of functionality here.  Only a simplification 
for new users.

Cheers,
Leif