Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.0.Final
Affects Version/s: 7.1.0.CR1b
Component/s: JMS
Labels:
None

Steps to Reproduce:

Hide

1. Start jboss as usual. At this stage it loads as it should, with queues recognized and everything.
2. Deploy something at standalone/deploy folder, no matters what, every war / jar / something will go.
3. The standalone-full.xml (or the one you are using, name it) is being rewritten by jboss, without the whole <jms-destinations> part at all.
4. From next start and on, jboss is not creating my queues, obviously, because it doesn't have a clue it should.

Show
1. Start jboss as usual. At this stage it loads as it should, with queues recognized and everything. 2. Deploy something at standalone/deploy folder, no matters what, every war / jar / something will go. 3. The standalone-full.xml (or the one you are using, name it) is being rewritten by jboss, without the whole <jms-destinations> part at all. 4. From next start and on, jboss is not creating my queues, obviously, because it doesn't have a clue it should.
Forum Reference:
http://community.jboss.org/thread/176534
Affects:

Compatibility/Configuration

Description

I have 2 JMS queues defined at standalone-full.xml. JBoss recognized them on first run and everything seems to be ok, but it rewrites standalone.xml without queues definition, i.e. completely ommiting the <jms-destinations> element, so after jboss restart queues don't exist anymore.
This happens on the first standalone-full.xml rewrite (i.e. after something have been deployed, etc.)

This bug is a regression, beta1 and earlier worked just fine.
Please see forum thread for detailed discussion, more users' reports and example standalone.xml

Attachments

Activity

People

Assignee:: Stuart Douglas

Reporter:: Alex Krasov (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2012/01/03 11:34 AM

Updated:: 2012/01/03 5:33 PM

Resolved:: 2012/01/03 5:33 PM