Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: 7.2.6.GA
Component/s: JMS
Labels:
None

Target Release:

7.2.z.GA
Steps to Reproduce:
Hide

Please integrate AMQ-7.5 with JBoss EAP 7.2.6 using the embedded JMS RAR provided in the EAP 7.2.6

Please create an MDB to listen to a Queue that does not exist in AMQ7

On the MDB, make sure to set useJNDI ActivationConfigurationProperty to 'false' and specify a nonexistent Queue physical name ie "testQueue".

Start the AMQ-7.5 broker, then JBoss EAP 7.2.6

Please deploy the MDB, the EAP server would start logging the following message at INFO level for every two seconds infinitely
AMQ151004: Instantiating javax.jms.Queue "autoCreatedQueue" directly since UseJNDI=false
Show
Please integrate AMQ-7.5 with JBoss EAP 7.2.6 using the embedded JMS RAR provided in the EAP 7.2.6 Please create an MDB to listen to a Queue that does not exist in AMQ7 On the MDB, make sure to set useJNDI ActivationConfigurationProperty to 'false' and specify a nonexistent Queue physical name ie "testQueue". Start the AMQ-7.5 broker, then JBoss EAP 7.2.6 Please deploy the MDB, the EAP server would start logging the following message at INFO level for every two seconds infinitely AMQ151004: Instantiating javax.jms.Queue "autoCreatedQueue" directly since UseJNDI=false

SFDC Cases Counter:
SFDC Cases Links:

Description

JBoss EAP 7.2.6 continually logs 'AMQ151004' message[1] at INFO level if the remote AMQ 7 broker hasn't been configured with the corresponding destination.

[1] AMQ151004: Instantiating javax.jms.Queue "autoCreatedQueue" directly since UseJNDI=false

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

test-case.tar.bz2
12 kB
2020/03/05 11:28 PM

Activity

People

Assignee:: Howard Gao

Reporter:: Tyronne Wickramarathne

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2020/03/05 11:29 PM

Updated:: 2023/09/07 11:51 PM