Wildfly 17.0.1 activemq warning

[marcanthony]

Morning All

Could someone shed some light on the meaning of this message:

08:32:01,421 WARN  [org.apache.activemq.artemis.ra] (default-threads - 6) AMQ153005: Unable to retrieve ${0} from JNDI. Creating a new ${1} named ${2} to be used by the MDB.

I get at least 2 on server startup with my project deployed, I know it is a warning but would like to understand what if any is wrong with my setup

Thanks

Marc

[jaikiran]

The presence of those raw ${0} etc parameter placeholders does indeed look odd. Can you file a JIRA for this here - JBoss Issue Tracker  and reference this thread. If possible please attach to that JIRA an application which reproduces this.

[marcanthony]

Hi Jaikiran

I will create a sample app to reproduce the issue

Thanks

[artk2002]

I'm seeing the same problem, except that it seems to be in a loop.

[artk2002]

I did some debugging. The warning message is correct, in that something wasn't found in JNDI. If you turn on trace logging for org.apache.activemq.artemis.ra.inflow.ActiveMQActivation, the log file will show you a line like this nearby:

2019-08-29 09:11:40,263 DEBUG [org.apache.activemq.artemis.ra.inflow.ActiveMQActivation] (default-threads - 1) Retrieving <queue-type> "<queue-name>" from JNDI

In my case, the warning is because I have some MDBs that don't have properly defined activation specs. What's troublesome is that the activation says it's creating one (and I can see some of that in the log), but it doesn't find it the next time around.

[marcanthony]

Yes, with debug enabled I got to the bottom of this

java:/jms/queue/ExpiryQueue is the jndi in standalone

in my mdb I have

java:jboss/jms/queue/ExpiryQueue

Weird thing is that in Wildfly 10 it never complained.

So is there an issue in the logic reporting the problem? or is everything good?

[peter.printzen]

I have that warning every 2 seconds. Running 7.2.4. Any workaround appreciated.

[ehugonnet]

AS jaikiran wrote could you please fill a Jira and attach a reproducer.