Bug 1487313 - [GSS](6.4.z) HornetQ broker should shutdown if no journal file can be found within specified timeout.
Summary: [GSS](6.4.z) HornetQ broker should shutdown if no journal file can be found w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.4.16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.18
Assignee: Ivo Studensky
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6418-payload 1464499 1497151 1518851
TreeView+ depends on / blocked
 
Reported: 2017-08-31 15:32 UTC by Tom Ross
Modified: 2021-03-11 15:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 18:30:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HORNETQ-1560 0 Major Open HornetQ broker should shutdown if no journal file can be found within specified timeout 2020-03-16 09:16:44 UTC
Red Hat Issue Tracker JBEAP-13997 0 Major Resolved [GSS](7.0.z) Artemis broker should shutdown if no journal file can be found within specified timeout 2020-03-16 09:16:37 UTC

Description Tom Ross 2017-08-31 15:32:13 UTC 
Description of problem:
A HornetQ broker should shutdown immediately if journal file cannot be provision within specified timeout.
Comment 3 Jiří Bílek 2017-10-27 08:10:50 UTC 
Verified with EAP 6.4.18.CP.CR1
Comment 4 Petr Penicka 2017-12-06 18:30:30 UTC 
Released on Nov 14 2017 as part of EAP 6.4.18.
Note You need to log in before you can comment on or make changes to this bug.