[
https://issues.apache.org/activemq/browse/AMQ-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies reassigned AMQ-1294:
-------------------------------
Assignee: Rob Davies
> Kaha can't be completely disabled in activemq-5.0
> -------------------------------------------------
>
> Key: AMQ-1294
> URL: https://issues.apache.org/activemq/browse/AMQ-1294
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build diablo-1.5.0-b01)
> Java HotSpot(TM) Server VM (build diablo-1.5.0_07-b01, mixed mode)
> Reporter: Tom Samplonius
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.0.0
>
>
> Kaha can't be completely disabled in activemq-5.0-20070621.
> With this config:
> <persistenceAdapter>
> <journaledJDBC journalLogFiles="5"
> dataDirectory="${activemq.base}/activemq-data"/>
> </persistenceAdapter>
> ActiveMQ should just use JDBC/Derby+Journal, as soon as the first consumer
> gets a message, ActiveMQ logs this:
> INFO KahaStore - Kaha Store successfully deleted data
> directory activemq-data/localhost/tmp_storage
> INFO BrokerService - Successfully deleted temporary storage
> So ActiveMQ is trying to delete temporary files belong to a persistence
> engine that isn't used.
> It seems odd that Kaha purges temporary files during consumer startup, rather
> than ActiveMQ startup when Kaha would normally (if I was using it), be
> recovering/checking its database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
