Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1105502376.576061269943947355.JavaMail.jira@brutus.apache.org>
Date: Tue, 30 Mar 2010 10:12:27 +0000 (UTC)
From: "Tiago R. Espinha (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4584) Unable to connect to network server
 if client thread name has Japanese characters
In-Reply-To: <623896142.284071268721747334.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-4584?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1285=
1341#action_12851341 ]=20

Tiago R. Espinha commented on DERBY-4584:
-----------------------------------------

suites.All ran without problems (just the "normal" replication test failure=
 since I'm using a Windows box)

Next, I'll be running derbyall.

> Unable to connect to network server if client thread name has Japanese ch=
aracters
> -------------------------------------------------------------------------=
--------
>
>                 Key: DERBY-4584
>                 URL: https://issues.apache.org/jira/browse/DERBY-4584
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10=
.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.=
1, 10.5.2.0, 10.5.3.0
>            Reporter: Brett Wooldridge
>            Assignee: Tiago R. Espinha
>         Attachments: DERBY-4584-fix.diff, DERBY-4584-fix.diff, DERBY-4584=
-test.diff, DERBY-4584-test.diff, DERBY-4584.diff
>
>
> I am opening this bug, which is probably a duplicate of bug#728 so that o=
ther's may find it and save the hours I spent chasing it down.  Feel free t=
o mark this as a duplicate.  However, while related, it may not be a true d=
uplicate of 728.
> The exception is similar to 728:
> Exception in thread "main" org.apache.derby.client.am.SqlException: Unico=
de string can't convert to Ebcdic string
> (Here is the version of the exception I received -- excuse the Japanese c=
haracters):
> Caused by: org.apache.derby.client.am.SqlException: Unicode =E3=82=B9=E3=
=83=88=E3=83=AA=E3=83=B3=E3=82=B0=E3=82=92 EBCDIC =E3=82=B9=E3=83=88=E3=83=
=AA=E3=83=B3=E3=82=B0=E3=81=AB=E5=A4=89=E6=8F=9B=E3=81=99=E3=82=8B=E3=81=93=
=E3=81=A8=E3=81=AF=E3=81=A7=E3=81=8D=E3=81=BE=E3=81=9B=E3=82=93=E3=80=82
> =09at org.apache.derby.client.net.EbcdicCcsidManager.convertFromUCS2(Unkn=
own Source)
> =09at org.apache.derby.client.net.Request.writeScalarString(Unknown Sourc=
e)
> =09at org.apache.derby.client.net.Request.writeScalarString(Unknown Sourc=
e)
> =09at org.apache.derby.client.net.NetConnectionRequest.buildEXTNAM(Unknow=
n Source)
> =09at org.apache.derby.client.net.NetConnectionRequest.buildEXCSAT(Unknow=
n Source)
> =09at org.apache.derby.client.net.NetConnectionRequest.writeExchangeServe=
rAttributes(Unknown Source)
> =09at org.apache.derby.client.net.NetConnection.writeServerAttributesAndK=
eyExchange(Unknown Source)
> =09at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKe=
yExchange(Unknown Source)
> =09at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unkno=
wn Source)
> =09at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Sourc=
e)
> =09at org.apache.derby.client.net.NetConnection.initialize(Unknown Source=
)
> =09at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> =09at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)
> =09at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetCon=
nection(Unknown Source)
> =09at org.apache.derby.client.net.NetXAConnection.createNetConnection(Unk=
nown Source)
> =09at org.apache.derby.client.net.NetXAConnection.<init>(Unknown Source)
> =09at org.apache.derby.client.ClientPooledConnection.getNetXAConnection(U=
nknown Source)
> =09... 45 more
> However, the difference is that the database name (and connection URL) do=
es NOT contain unicode characters.  In this case, the *thread name* contain=
s Japanese characters.  If the thread performing java.sql.DriverManager.get=
Connection() has characters that cannot be translated into EBCDIC the above=
 exception is the result.  If the thread name is changed to contain only st=
andard ASCII characters, the connection to the DB is successful.  Note agai=
n, in my case, the connection URL is a standard connection URL with no i18n=
 characters, something similar to:
> jdbc:derby://localhost/database
> It is only the thread-name that contains i18n characters.  I don't know w=
hy the client feels it necessary to marshall the client-thread name, but th=
at seems to be the problem.  The fix for this issue is likely easier than 7=
28 if the requirement that the client marshall the thread name can be remov=
ed (it seems senseless).
> Finally, just for the record, a typical thread name that tickles this bug=
 is:
> "Running-2 (MOTD=E3=83=90=E3=83=8A=E3=83=BC=E3=81=AE=E8=A8=AD=E5=AE=9A fo=
r 10.0.0.90@Default)"
> If the Japanese is removed from the thread names, there is no problem.
> The workaround in our case was to change the thread names in our code to =
not contain Japanese characters.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.