I believe those files are showing up because the async event queue is
designed to overflow to disk if it is low on memory. It uses a disk store,
which creates those files to show the disk store is in use by a process.

You should be able to control where these files end up by setting the
disk-store-name on the async event queue to a disk store that you have
configured. In the disk store configuration you can set the directory where
the files go.

-Dan

On Tue, Jan 15, 2019 at 6:53 AM Thacker, Dharam <[email protected]>
wrote:

> Hello Team,
>
> Could some one help me with this? For my case app is running from
> read-only file system so it's failing to initialize due to creation of lock
> and backup files for async event queue.
>
> Thanks,
> Dharam
>
>
> Sent with BlackBerry Work (www.blackberry.com)
> ------------------------------
> *From: *"Thacker, Dharam" <[email protected]>
> *Sent: *Jan 10, 2019 5:07 PM
> *To: *[email protected]
> *Subject: *Lock files with Async event queue
>
> Hi Team,
>
>
>
> I have following configuration for async event queue but it still creates
> lock and backup files as shown below.
>
> Is there any way to prevent it?
>
>
>
> If not, how I can configure directory for following files? I don’t want my
> queue to be persisted as well.
>
>
>
>
>
> <geode:async-event-queue id=*"test-event-queue"* persistent=*"false"*
> batch-time-interval=*"1000"* dispatcher-threads=*"4"*>
>
>        <geode:async-event-listener ref=*"testEventListener"*/>
>
> </geode:async-event-queue>
>
>
>
>
>
>
>
> Thanks,
>
> Dharam
>
> This message is confidential and subject to terms at: https://
> www.jpmorgan.com/emaildisclaimer
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.jpmorgan.com_emaildisclaimer&d=DwMFAg&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=WLfm1gWdzznUCrPAWyBJYQjifxLutUaeKbwnfk4TP0w&m=5xZn8PoWWgYeHd0P4zB8zlqvplHx8zRFrv-Uic8TPx0&s=Ltqf_YKZkTBkstBzrtKGcaq1LH3tsizd5aJzDK2t6qQ&e=>
> including on confidentiality, legal privilege, viruses and monitoring of
> electronic messages. If you are not the intended recipient, please delete
> this message and notify the sender immediately. Any unauthorized use is
> strictly prohibited.
>

Reply via email to