db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-3287) Failure in TriggerTest.testBlobInTriggerTable.
Date Thu, 07 May 2009 14:16:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden closed DERBY-3287.
---------------------------------

    Resolution: Duplicate

This looks like  a duplicate of DERBY-3811 which has a reproduction attached.


> Failure in TriggerTest.testBlobInTriggerTable.
> ----------------------------------------------
>
>                 Key: DERBY-3287
>                 URL: https://issues.apache.org/jira/browse/DERBY-3287
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.4.1.3
>            Reporter: A B
>            Priority: Minor
>
> On 12/14 while running suites.All with ibm142 I saw the following error in TriggerTest.testBlobInTriggerTable():
> java.lang.ArrayIndexOutOfBoundsException: -1
> 	at org.apache.derby.impl.store.raw.data.BasePage.getHeaderAtSlot(Unknown Source)
> 	at org.apache.derby.impl.store.raw.data.StoredPage.restorePortionLongColumn(Unknown
Source)
> 	at org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(Unknown Source)
> 	at org.apache.derby.impl.store.raw.data.BufferedByteHolderInputStream.read(Unknown Source)
> 	at java.io.FilterInputStream.read(FilterInputStream.java:86)
> 	at java.io.FilterInputStream.read(FilterInputStream.java:86)
> 	at org.apache.derbyTesting.functionTests.tests.lang.TriggerTest.assertInputStreamContents(TriggerTest.java:705)
> 	at org.apache.derbyTesting.functionTests.tests.lang.TriggerTest.testBlobInTriggerTable(TriggerTest.java:684)
> 	at org.apache.derbyTesting.functionTests.tests.lang.TriggerTest.testBlobInTriggerTable(TriggerTest.java:575)
> It only happened once (so far), but I'm filing the Jira for tracking in case it happens
again.  I do not have a stack trace with sane build readily available as the failure only
happened once...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message