Return-Path: 
 <derby-dev-return-92265-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-derby-dev-archive@www.apache.org
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 308567087
	for <apmail-db-derby-dev-archive@www.apache.org>;
 Tue, 13 Dec 2011 15:02:02 +0000 (UTC)
Received: (qmail 8076 invoked by uid 500); 13 Dec 2011 15:02:02 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 8049 invoked by uid 500); 13 Dec 2011 15:02:02 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 8040 invoked by uid 99); 13 Dec 2011 15:02:02 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Dec 2011 15:02:02 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com
 designates 209.85.160.172 as permitted sender)
Received: from [209.85.160.172] (HELO mail-gy0-f172.google.com)
 (209.85.160.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Dec 2011 15:01:54 +0000
Received: by ghrr16 with SMTP id r16so554269ghr.31
        for <derby-dev@db.apache.org>; Tue, 13 Dec 2011 07:01:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=Lim+usvBcWH03KSmGzGLZF4+rd9Wgq+jvh0LRmKxsSM=;
        b=xVQFBEYpHfTfM8LdTMDzfxuSmzEK1OfwwQO80SII4sN11UKjDfAuMDmCNUGPpqwiAI
         tVxyen3rnQEFHByGyGcJbP0srujkBfqmRSEZXugtJyMQgR9mgZbzuhG6ld5QllPkFRHo
         gAQ//q1AuvKXObUV++ktybtnCiAhp6MiwfD+c=
Received: by 10.50.158.227 with SMTP id wx3mr19826694igb.52.1323788493508;
        Tue, 13 Dec 2011 07:01:33 -0800 (PST)
Received: from [192.168.0.100] (c-67-170-231-73.hsd1.ca.comcast.net.
 [67.170.231.73])
        by mx.google.com with ESMTPS id b31sm64846314ibh.9.2011.12.13.07.01.32
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 13 Dec 2011 07:01:33 -0800 (PST)
Message-ID: <4EE768C7.4020503@gmail.com>
Date: Tue, 13 Dec 2011 07:01:27 -0800
From: Bryan Pendleton <bpendleton.derby@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Derbyclient on Windows 7/JDK 7: "Invalid argument: connect"
References: <4EE61A97.7040203@gmail.com> <4EE64ACC.6070005@sbcglobal.net>
In-Reply-To: <4EE64ACC.6070005@sbcglobal.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> What is the exact jdk 7 version from oracle you were trying?

I'm not sure. Unfortunately I've lost access to that machine for now.

I'll try to re-create this on another machine.

thanks,

bryan

>
>> Recently, I happened to try using the ClientDriver from Derby 10.8.2.2 under Windows 7
>> with the latest download of JDK 7 from the Oracle site, and was unable to connect to
>> any server. The client kept reporting the error:
>>
>> Invalid argument: connect
>>
>> When I backed down to JDK 1.6, the problem went away.