The fact that your client is running on WildFly is an important detail
because it still uses the 1.x prefixes for JMS queues and topics (i.e.
"jms.queue." and "jms.topic" respectively). Therefore, you should try
adding this to your acceptor:
anycastPrefix=jms.queue.;multicastPrefix=jms.topic.
Let me know if that helps.
Justin
On Tue, Oct 10, 2023 at 6:28 AM Calle Andersson <calleanders...@hotmail.com>
wrote:
> Thanks for the reply,
>
> I'm using ActiveMQ Artemis 2.31.0 as well.
>
> Thanks for the suggestion on using the "consumer" and "producer" commands
> (I didn't know of them). However, when using the commands everything worked
> as expected (using my intended Artemis configuration).
>
> I assume my problem isn't the Artemis configuration but something in my
> JMS consumer code or it's server configuration.
>
> I still think it's strange that the consumer doesn't seem to detect the
> queue until I add the adjustements to my intended Artemis configuration (as
> mentioned in my first mail). Maybe this is considered off topic for this
> mailing list but my consumer is running on Wildfly Camel (Wildfly 20, Camel
> 3.4) and use a Camel consumer:
> from(jms("TEST.QUEUE.A")).transacted()
>
> The server configuration looks like this:
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:10.0">
> <server name="default">
> <remote-connector name="my-remote-artemis-connector"
> socket-binding="my-remote-artemis-connection-factory"/>
> <pooled-connection-factory name="my-remote-artemis-connection-factory"
> entries="java:/dummy/artemisConnectionFactory"
> connectors="my-remote-artemis-connector" ha="false" user="myUser"
> password="myPassword" min-pool-size="15" max-pool-size="30"
> statistics-enabled="true">
> <inbound-config rebalance-connections="true" setup-attempts="-1"
> setup-interval="5000"/>
> </pooled-connection-factory>
> // ...
>
> Any suggestions on where/how I could continue debugging?
>
> Regards,
> Calle
>
