db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-3440) Run suites.All with statement pooling enabled and classify the problems occurring
Date Wed, 04 Jun 2008 10:51:45 GMT

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

Kristian Waagan closed DERBY-3440.
----------------------------------

    Resolution: Fixed

This hack served well as an initial smoke test.
I don't see any point in spending more time on it now.

Closing the issue.

> Run suites.All with statement pooling enabled and classify the problems occurring
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-3440
>                 URL: https://issues.apache.org/jira/browse/DERBY-3440
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions: 10.4.1.3
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.1.3
>
>         Attachments: WithCPDS-NoStatementPooling-errors-01.txt, WithCPDS-WithStatementPooling-errors-01.txt
>
>
> The patches for the statement pooling feature should soon make it possible to run suites.All
with statement caching enabled.
> I will post a patch that modifies TestConfiguration to return connections from a ConnectionPoolDataSource.
> There will be a substantial numbers of errors, and I hope to classify these and maybe
refer to JIRA issues that will make them go away.
> I have already tried this, and ended up at around 180 failures/errors, a report will
follow soon.

-- 
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