>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 > > >
