Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1238456804.1141688671637.JavaMail.jira@ajax>
Date: Mon, 6 Mar 2006 23:44:31 +0000 (GMT)
From: "Jeff Levitt (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-283) On IPv6/Ipv4 dual stack windows
 machines, the network server needs the following jvm properties to be
 prefixed while starting the server .
In-Reply-To: <1421066702.1116019028891.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-283?page=all ]

Jeff Levitt updated DERBY-283:
------------------------------

    Attachment: derby283.diff
                tadminconfigipx.html

Attached patch adds the information to the Admin Guide in the section about Starting the Network Server.  HTML output included for review.  Please let me know if it looks good so a committer can commit.  Thanks!

> On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server .
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-283
>          URL: http://issues.apache.org/jira/browse/DERBY-283
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.0.2.1
>     Reporter: Manjula Kutty
>     Priority: Minor
>  Attachments: derby283.diff, tadminconfigipx.html
>
> On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . 
> -Djava.net.preferIPv4Stack=false 
> -Djava.net.preferIPv6Addresses=true 
> This is a Windows OS problem and have to track to to see when MS is going to fix and then make the appropriate changes in our docs

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira