[ http://issues.apache.org/jira/browse/DERBY-815?page=all ] A B reopened DERBY-815: -----------------------
I have a test that runs using the DB2 client; before the patch for this issue was checked in, the test passed; now it hangs. To make sure, I synced my client at revision 371896 and the test passed; I then synced it to 371897 and it hung--so it does indeed appear to be caused by this checkin. I'm still trying to figure out what part of the test is causing the issue, and am trying to create a repro using either the Derby Client or the JCC. I will post more when I find out. In the meantime, I'm reopening this issue for tracking... > Prevent unneeded object creation and excessive decoding in parseSQLDTA_work() > ----------------------------------------------------------------------------- > > Key: DERBY-815 > URL: http://issues.apache.org/jira/browse/DERBY-815 > Project: Derby > Type: Sub-task > Components: Network Server, Performance > Versions: 10.0.2.2, 10.1.1.0, 10.1.2.0, 10.1.1.1, 10.1.1.2, 10.1.2.1, > 10.1.3.0, 10.1.2.2 > Reporter: Knut Anders Hatlen > Assignee: Dyre Tjeldvoll > Priority: Minor > Fix For: 10.2.0.0 > Attachments: derby-815.diff, derby-815.stat, derbyall_report.txt > > Reported by Kathey Marsden in DERBY-212: > In reviewing the Network Server Code and profiling there were several > areas that showed potential for providing performance > improvement. Functions that need optimizing to prevent unneeded object > creation and excessive decoding: parseSQLDTA_work() -- 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
