dev@glassfish.java.net

Re: All smoke tests failing when port 1044 is used by another process...

From: Kyle Grucci <Kyle.Grucci_at_Sun.COM>
Date: Mon, 02 Jul 2007 11:58:34 -0400

This file (and property) are only used if you install the appserver via
the CTS/TCK installation targets. This property does not have any
effect on the CTS smoke tests if you installed the appserver via some
other mechanism.

-Kyle

Mark A. Basler wrote:
> On a tip from Shreedhar, I checked the CTS smoke test code and found
>
> bin/xml/install_sjsas.xml: <property
> name="sjsas.das.securedWebServicePort" value="1044"/>
>
> This could be the problem, but I don't know if just changing this port
> will fix it. I can try changing the port if I run into the problem
> again..
>
> Does anyone know for sure...
>
> Please let me know...
>
> Thanks - Mark
>
>
> Mark A. Basler wrote:
>> HI Guys,
>>
>> Last night I was trying to run the CTS smoke tests on Glassfish and
>> they were all failing with an exception from the webtier in the log
>> stating the port 1044 isn't available.
>>
>> I checked netstat and found another process had this port. I
>> searched the web for "glassfish 1044" and got some references to the
>> the http-ssl port, but couldn't find any configuration in domain.xml
>> for the port number.
>>
>> Eventually all the tests passed when the other process released the
>> 1044 port, but for future reference, how can I work around this
>> problem if the port is in use again.
>>
>> Please let me know...
>>
>> Thanks - Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>

-- 
Kyle Grucci
CTS Architect
Java EE Compatibility
Sun Microsystems, Inc.
Voice x81455 / +1 781 730 4183
Email - kyle.grucci_at_sun.com