db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1061) SqlException while fetching message results in recursive calls between SqlException.getSQLException and Sqlca.getJDBCMessage
Date Fri, 10 Mar 2006 15:13:52 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1061?page=all ]

Kristian Waagan updated DERBY-1061:
-----------------------------------

    Attachment: JDBC4StackOverflowErrorReproduction.java
                derby-1061_2-unix.diff

Had some problems applying diff on Linux, seems to be related to newline style. Changed it
and posted a updated file 'derby-1061_2-unix.diff'.

Tried out the patch, but it does not seem to fix my problem. I attach the repro 'JDBC4StackOverflowErrorReproduction.java'
that demonstrate the error. Might be a different problem than this issue is fixing, if so
I hope the patch contributer can inform about that.

To run, start a JDBC4 enabled network server (run with JDK 1.6), then run the script with
JDK 1.6.

> SqlException while fetching message results in recursive calls between SqlException.getSQLException
and Sqlca.getJDBCMessage
> ----------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1061
>          URL: http://issues.apache.org/jira/browse/DERBY-1061
>      Project: Derby
>         Type: Sub-task
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>  Attachments: JDBC4StackOverflowErrorReproduction.java, derby-1061.diff, derby-1061_2-unix.diff,
derby-1061_2.diff, derbyall_report.txt
>
> stored procedure is used to fetch localised message in net work client
> because of issue 1059 the call to the stored prcedures fails resulting in SqlException.
When  SqlException.getSQLException, to set exceptionThrownOnStoredProcInvocation_, is called
it again results in a call to SqlException.getMessage which call Sqlca.getJDBCMessage. 
> The cycle repeats and finally ends up with StackOverfilowError
> fixing 1059 will solve this problem temporarily but some other situaltion may cause it
again.
> Isuggest seting SqlException itself to exceptionThrownOnStoredProcInvocation_ to break
this loop.

-- 
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


Mime
View raw message