Just a quick look at the JavaDocs, it seems that it's up to the code creating the exception to call new BindException(String) to provide the port in an exception message, instead of using BindException() with no details.

You could always start/attach to the server in Eclipse and add that exception as a breakpoint and inspect the code for the port being used....


-Donald

Vamsavardhana Reddy wrote:
I am wondering if there is anyway to find out the exact port number resulting in the exception from the exception itself.

++Vamsi

On Feb 1, 2008 7:30 PM, Upul Godage <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    You can use a tool like netstat to check which ports programs are
    listening on at the moment and unusable by the server instance.
    netstat -anb
    You can find which ports the server instance will use by the
    config.substitutions.properties entries.

    Upul



    On Feb 1, 2008 6:38 PM, Vamsavardhana Reddy <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        Very often I run into Geronimo startup failure with a
        BindException since some port or the other is in use.  Then I
        change the PortOffset to get going.  How do I figure which
        port/address is resulting in the exception?



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to