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] Commented: (DERBY-1061) SqlException while fetching message results in recursive calls between SqlException.getSQLException and Sqlca.getJDBCMessage
Date Sun, 12 Mar 2006 14:33:07 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12370067 ] 

Kristian Waagan commented on DERBY-1061:
----------------------------------------

I tried the repro script with unpatched trunk, 'derby-1061_v2' diff and 'derby-1061-david.diff'.
For me, running on Gentoo 2.6.15-gentoo-r7 64bit, only 'derby-1061-david.diff' solved the
problem. I have heard reports that also the v2 diff fixed it for others, but it did not for
my environment. I would therefore recommend we commit patch 'derby-1061-david.diff', assuming
that this patch also fixes the problem for others seeing this problem.

> 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-david.diff, derby-1061-david.stat,
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