[Wrapper-user] Wrapper behavior on Solaris 10 zone

[ahmadk72 <reg...@in...>]

I have a problem that is perplexed me to no end.  Even our UNIX admin is
stumped, so this mailing list is a last resort.

We have a third-party application that uses the Java Service Wrapper
(v3.2.1).  The application is installed on two different Zones in Solaris
10.  One zone is called rhdam-dev and the other is called rhdam-tst.

If i startup the rhdam-dev (DEV box) application, the Java service wrapper
uses ports 31000 and 32000 for communicating to and listening from the JVM.
Everything works fine, and I have no problems running the application as
expected.

Then recently we installed the application on the dam-tst (TEST box)
application on another Solaris zone.  When the wrapper starts up, I see the
following error (logging output is set to DEBUG level) in the attached log
file.

>From what I have been able to deciper, it is complaining about port 32000
already being in use.  However, the port is not in use on the rhdam-tst
zone.  I can run a netstat -an command and see that there is nothing running
on port 32000.

The really weird part is that is I stop the wrapper service on the rhdam-dev
zone, and try to startup the rhdam-tst instance, then the wrapper service
starts successfully.

For now I have been able to start both up by changing adding the
wrapper.port.min and wrappper.port.max settings so the ports don't conflict
between rhdam-dev and rhdam-tst.

However, I need to know why this is happening.  Has anyone seen this
behavior?  The ports are suppose to be independent on Solaris zone.  Why is
the Java Service wrapper socket complaining about the port being used in
another zone.

If anyone can help me solve this mystery that would be just great.

Thanks

Kashif http://www.nabble.com/file/p12904287/artesia-service-wrapper.log
artesia-service-wrapper.log 
-- 
View this message in context: http://www.nabble.com/Wrapper-behavior-on-Solaris-10-zone-tf4523339.html#a12904287
Sent from the Java Service Wrapper mailing list archive at Nabble.com.