db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5121) Data corruption when executing an UPDATE trigger
Date Thu, 17 Mar 2011 21:46:30 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008168#comment-13008168
] 

Mamta A. Satoor commented on DERBY-5121:
----------------------------------------

I am working on backporting this simple fix to disbale the column read optimization from 10.7
to trunk but I am seeing OOM errors for a subset of org.apache.derbyTesting.functionTests.tests.memory.TriggerTests.


The OOM should depend on how much heap the test gets run with. On both 10.7 and trunk(with
10.7 changes backported). I see no failures if I run the test with higher heap as shown below
java  -Dderby.tests.trace=true  -Xmx256M -XX:MaxPermSize=128M junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.memory.TriggerTests

But if I run the test on both 10.7 and trunk(with 10.7 changes backported) with lower heap,
I see OOM errors
java  -Dderby.tests.trace=true  -Xmx16M -Dderby.storage.pageCacheSize=100 junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.memory.TriggerTests

So the behavior on the 2 codelines with restricted and generous heap is the same when the
test is run directly. But when I run the junit suite as follows, I get OOM errors on trunk
but not on 10.7 codeline. At this point, I am not sure why. Is there a way that we change
the available heap on trunk for org.apache.derbyTesting.functionTests.tests.memory.TriggerTests
when it is run through the functionTests.suites.All junit suite? That's the only reason I
can think why the test would fail anywere. It appears that on 10.7, we do not change the heap
for org.apache.derbyTesting.functionTests.tests.memory.TriggerTests when it is run through
the functionTests.suites.All junit suite? Does anyone have any clue about this difference
in behavior between 10.7 and trunk? thanks
java  -Dderby.tests.trace=true  -Xmx256M -XX:MaxPermSize=128M junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All
> runall.out 2>&1


> Data corruption when executing an UPDATE trigger
> ------------------------------------------------
>
>                 Key: DERBY-5121
>                 URL: https://issues.apache.org/jira/browse/DERBY-5121
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.7.1.1, 10.8.0.0
>            Reporter: Rick Hillegas
>            Assignee: Mamta A. Satoor
>              Labels: derby_triage10_8
>         Attachments: DummyProc.java, derby5121_patch1_diff.txt, triggerBug.sql, triggerBug.sql,
triggeredBug2.sql, triggeredCorruption.sql
>
>
> When executing an UPDATE trigger, the following error is raised. I will attach a test
case:
> ERROR XCL12: An attempt was made to put a data value of type 'org.apache.derby.impl.jdbc.EmbedClob'
into a data value of type 'INTEGER'.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message