[
https://issues.apache.org/jira/browse/QPID-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724497#action_12724497
]
Martin Ritchie commented on QPID-1924:
--------------------------------------
IMO this is the wrong way to get the Store to use QPID_WORK.
... System.getProperty("QPID_WORK")+"/derbyDB");
If QPID_WORK is not set you end up making directory 'null/derbyDB' in the
current directory to put the store in which is worse than it simply writting to
derbyDB in the current directory.
Ideally there should be no default and it should fail to startup if
ENVIRONMENT_PATH_PROPERTY is not configured.
If we want to write to QPID_WORK/derbyDB then we should add it in the
configuration, such as:
<environment-path>${work}/derbyDB/test-store</environment-path>
I see the that Derby does not honour the environment-path specified for the
virtualhost as it progromatically adds the virtualhost name to the end of that
path. If you were used to using the BDB store then this is not what you would
expect.
Using ${work}/store in env-path results in {$work}/store/<vhost-name> being
made on disk, which has the DB stored in it. I would not expect that. The store
should honour the env-path set by the configuration.
> Derby doesn't honour QPID_WORK for storage
> ------------------------------------------
>
> Key: QPID-1924
> URL: https://issues.apache.org/jira/browse/QPID-1924
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker MessageStore - DerbyStore
> Affects Versions: 0.6
> Reporter: Aidan Skinner
> Assignee: Aidan Skinner
> Fix For: 0.6
>
>
> DerbyMessageStore doesn't honour QPID_WORK, if path isn't specified it
> defaults to cwd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
