Re: [Wrapper-user] Wrapper behavior on Solaris 10 zone

[Santo74 <gds...@de...>]

Leif,

Regarding the issue of restarting the application after it crashed or was
forcedly killed I will
keep an eye on it and report back with more info whenever it should happen
again.
It is indeed not the behaviour that I would expect from the wrapper
especialy now that you confirmed that it isn't allocating the whole range.

As you already mentioned correctly I won't be able yet to verify if I can
start the app on a second zone after having stopped the app on the first
zone for at least 2 min.

Concerning your last question: our dev/test system is currently configured
with 5 zones, all using their own ip address.
I have no idea about the configuration of the solaris systems at our
customers.

regards,

gds


Leif Mortenson-2 wrote:
> 
> Santo,
> We are in the process of setting up a Solaris 10 server to do some
> testing with Zones in house.  We have a Solaris 9 server, but out
> Solaris 10 testing has been done IN a zone on Sun's EZqual loaner
> server.  I will let you know what we found.
> 
> As I explained, the Wrapper never actually attempts to allocate all
> 1000 ports unless they are already blocked.  If the first instance of
> your application uses ports 32000 and 31000 and that crashes, it is
> possible that the 32000 port will be locked for 2 minutes so the
> second invocation of the JVM would use 32001 and 31000.   But the
> other 999 ports would have never been accessed so I can imagine no
> reason why they would be locked.
> 
> In your case with Solaris Zones.  You say that the Wrapper can not
> start on these second Zone when one is running on the first.   Are you
> able to verify that the wrapper on the second Zone works if the first
> had not been running for at least 2 minutes?  I am wondering if it is
> a configuration issue.
> 
> We will be able to test this shortly ourselves.  And it doesn't sound
> like you will be able to test it until your system is back up and
> running.
> 
> Sorry for this next question as it may show my lack of knowledge with
> Solaris Zones:
> With your system, are both Zones sharing the same IP address?  If so,
> they should not be able to share ports on that IP.  In this case
> however, we are only binding to localhost, so it should not matter.
> 
> I will post back as soon as we have gotten this tested out.
> 
> Cheers,
> Leif
> 

-- 
View this message in context: http://www.nabble.com/Wrapper-behavior-on-Solaris-10-zone-tp12904287p23595451.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.