You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2012/05/08 19:59:51 UTC
[jira] [Created] (QPID-3989) [Java Broker] Add ability to run Derby
Store "in-memory" and create a test profile to utilise this feature
Rob Godfrey created QPID-3989:
---------------------------------
Summary: [Java Broker] Add ability to run Derby Store "in-memory" and create a test profile to utilise this feature
Key: QPID-3989
URL: https://issues.apache.org/jira/browse/QPID-3989
Project: Qpid
Issue Type: Improvement
Components: Java Broker, Java Tests
Reporter: Rob Godfrey
Assignee: Rob Godfrey
Priority: Minor
Fix For: 0.17
Derby allows for the use of an "in memory" database. Allowing the virtual host configuration to select this as an option, and then using this for a test profile, should allow much more performant testing against the Derby store. Even tests which stop and restart the broker should work provided the broker is restarted within the same JVM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-3989) [Java Broker] Add ability to run
Derby Store "in-memory" and create a test profile to utilise this feature
Posted by "Rob Godfrey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270667#comment-13270667 ]
Rob Godfrey commented on QPID-3989:
-----------------------------------
I have modified the Derby Store implementation so that the store location ":memory:" in the config can be used to trigger the use of an in-memory store.
test profiles have been added, however I currently see a small number of failures in both the 0-10 and 0-9-1 profiles.
For example AsynchMessageListenerTest fails in both the 0-9-1 and 0-10 versions of this profile.
The likely cause is some sort of failure to properly clean up between tests.
> [Java Broker] Add ability to run Derby Store "in-memory" and create a test profile to utilise this feature
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-3989
> URL: https://issues.apache.org/jira/browse/QPID-3989
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Tests
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Priority: Minor
> Fix For: 0.17
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Derby allows for the use of an "in memory" database. Allowing the virtual host configuration to select this as an option, and then using this for a test profile, should allow much more performant testing against the Derby store. Even tests which stop and restart the broker should work provided the broker is restarted within the same JVM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org