db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2692) Client driver doesn't chain exceptions received from the server
Date Fri, 25 May 2007 07:15:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498967

Knut Anders Hatlen commented on DERBY-2692:

The concatenation of the error messages happens in the stored procedure SYSIBM.SQLCAMESSAGE
because the client passes in all the exceptions at once. I think that if the client receives
a chain of exceptions, it should call SQLCAMESSAGE once for each exception in the chain and
rebuild the exception chain as it was on the server.

The logic in Sqlca.processSqlErrmcTokens() on the client seems to be broken. It tries to split
an SQLERRMC message into tokens, but it uses a different token delimiter than the server (server
uses \u0014, client uses \u00FF). Therefore, the client always thinks it gets one big token
from the server. This doesn't seem to be a big problem, since it would anyway just split it
into separate tokens and concatenate the tokens again, but it seems a little strange. If we
want the client to split the SQLERRMC into a chain of exceptions, this has to be fixed though.

> Client driver doesn't chain exceptions received from the server
> ---------------------------------------------------------------
>                 Key: DERBY-2692
>                 URL: https://issues.apache.org/jira/browse/DERBY-2692
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions:,,
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
> When the client driver receives a chain of exceptions from the server, it generates one
exception with the messages from all the server-side exceptions concatenated into one message.
No next-exception chain is set up on the client. See the description of DERBY-1440 for an

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

View raw message