Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

STOMP messages are not persistent by default #1857

Open
adam-vessey opened this issue Jun 23, 2021 · 0 comments
Open

STOMP messages are not persistent by default #1857

adam-vessey opened this issue Jun 23, 2021 · 0 comments
Labels
Type: bug identifies a problem in the software with clear steps to reproduce

Comments

@adam-vessey
Copy link
Contributor

Somewhat of an unexpected find, but STOMP messages do not survive a restart of ActiveMQ... I suppose another queue might default to persisting them, but with ActiveMQ:

STOMP messages are non-persistent by default. To use persistent messaging add the following STOMP header to all SEND requests: persistent:true. This default is the opposite of that for JMS messages.

Given there may be some depending on this behaviour... was looking for a way to alter the headers of STOMP messages; however, that does not appear to be possible: #1856
This was referenced Jun 23, 2021
Merged
Closed
Merged
@kstapelfeldt kstapelfeldt added Type: bug identifies a problem in the software with clear steps to reproduce and removed bug labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: bug identifies a problem in the software with clear steps to reproduce
Projects
Islandora Issues Queue
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kstapelfeldt @adam-vessey