Unfortunately this is not a case of dependency order and it can also not
be solved by some form of initial delay. Upon startup our application
server analyzes certain metadata and may decide that it can not start in
normal production mode but that an upgrade process needs to be
performed, causing it to start in what we call upgrade mode. In that
mode the application server can only service the upgrade process which
is a special client app that must be run manually by an admin user.
After that process finishes the server may proceed in normal production
mode.
It is only in this state that we get JMS messages in while message
handlers can not (yet) process them. So we need to postpone all JMS
activity until the application server goes into production mode, however
long that may take.
Thanks for pointing out that this may be something we need to control
through the Wildfly management layer instead. I will look into that.
Kind regards,
Silvio
On 13-11-2024 18:16, Justin Bertram wrote:
From what I recall WildFly itself has a pretty rich set of dependency
features to enable things to start in the "right" order. My guess is that
you simply don't have your dependencies set up properly to enable this. For
example, I believe if you inject a reference to a JMS queue in your
application the broker will wait until that queue is deployed before it
deploys the application.
Regarding the broker itself, the TCP-based Netty acceptor supports a
parameter named autoStart [1] which determines whether an acceptor will
start automatically when the broker is started. However, I don't believe
WildFly has any direct support for this feature. Furthermore, since WildFly
has its own management layer on top of the broker I'm not sure you could
start the acceptor via JMX like would be possible with a standalone broker.
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html#configuring-netty-tcp
On Wed, Nov 13, 2024 at 7:26 AM Bisil <bi...@idfix.nl> wrote:
We have an ActiveMQ server with a number of queues configured in our
Wildfly configuration. We would like to start Wildfly with a suspended
ActiveMQ and at a later stage activate ActiveMQ through JMX. The reason
for this is that we are receiving JMS messages before our application is
in the proper state to handle them.
Is this in any way possible? Or can this only be done by setting up the
whole ActiveMQ and queues programmatically once we are ready for the
messages?
A bit of context: The JMS messages originate from our own application.
Due to the durability of the messages that have been sent during an
earlier run they are being delivered after a restart. Unfortunately our
application is at that point not yet able to handle them properly.
Thanks.
Silvio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
For additional commands, e-mail: users-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
For additional commands, e-mail: users-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
