Hi, After adding the logmonitor the failed statement is coming as null in derby log file. Please guide me on the same
With Regards Jayaram On Sun, Jun 19, 2011 at 2:39 PM, Jayaram Subramanian <[email protected]>wrote: > Hi All, > After adding the monitor.logmonitor the failed statement is coming as null > in derby.log file... Could you please guide me on how to proceed further on > this issue.. > > With Regards > Jayaram > > > > On Sun, Jun 19, 2011 at 2:35 PM, Jayaram Subramanian (JIRA) < > [email protected]> wrote: > >> >> [ >> https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051723#comment-13051723] >> >> Jayaram Subramanian commented on DERBY-5010: >> -------------------------------------------- >> >> As mentioned added the Monitor.getMonitor().logThrowable(new >> Exception("Trace in isEquivalent") and then executed java >> org.apache.derbyTesting.functionTests.tests.lang.LangScripts aggregate >> >> June19.out .. >> >> >> in the derby log file got >> Sun Jun 19 14:08:06 CDT 2011 Thread[main,5,main] (XID = 624), (SESSIONID = >> 3), (DATABASE = wombat), (DRDAID = null), Failed Statement is: null >> >> the failed statement is coming as null.. Attaching the log file for >> reference... The log file shows the "isequivalent" method being invoked but >> the statement could not be traced out.. >> >> > [patch] bad equivalence check >> > ----------------------------- >> > >> > Key: DERBY-5010 >> > URL: https://issues.apache.org/jira/browse/DERBY-5010 >> > Project: Derby >> > Issue Type: Bug >> > Components: SQL >> > Affects Versions: 10.7.1.1 >> > Reporter: Dave Brosius >> > Priority: Trivial >> > Fix For: 10.8.1.4 >> > >> > Attachments: IsEquivalent_DoNotCommit_June11.txt, >> IsEquivalent_Donotcommit_june14.txt, bad_equivalence_check.diff, june15.out, >> runoutputJune14.out, runoutputJune2.out >> > >> > Original Estimate: 1h >> > Remaining Estimate: 1h >> > >> > code attempts to compare two BaseColumnNodes but doesn't compare the >> tableName correctly. >> >> -- >> This message is automatically generated by JIRA. >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> >> >
