Home/ Questions/Q 7868097
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T00:53:42+00:00

I’m using spring integration to communicate via active mq. I’ve got the following config.

  • 0

I’m using spring integration to communicate via active mq. I’ve got the following config.

<integration:channel id="riskApprovalRequestChannel"/>
    <integration:channel id="riskApprovalResponseChannel"/>

    <jms:outbound-gateway id="riskApprovalServiceGateway"
                          request-destination-name="${risk.approval.queue.request}"
                          reply-destination-name="${risk.approval.queue.response}"
                          request-channel="riskApprovalRequestChannel"
                          reply-channel="riskApprovalResponseChannel"
                          connection-factory="jmsConnectionFactory"
                          receive-timeout="1000"/>

    <integration:gateway id="riskApprovalService" service-interface="com.my.ServiceInterface"
                         default-request-channel="riskApprovalRequestChannel"
                         default-reply-channel="riskApprovalResponseChannel"/>

This works well except for the 1st request, which is slow. I always hit the 1 second timeout on the 1st request. There’s obviously some lazy loading going on somewhere.

My question is, how do I do a full initialisation at start up to avoid the 1st request always timing out?

Cheers,

Peter

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It is probably connection establishment that’s the issue.

    One thing you can do is wrap the vendor ConnectionFactory in a Spring CachingConnectionFactory (good idea to do this anyway, for performance reasons), and call createConnection() during initialization.

    There are a number of ways to do that – including injecting the connection factory into some other bean, with an init-method, @PostConstruct method, or an InitializingBean with afterPropertiesSet(); it will be called during context initialization.

    This will cause the cache’s connection to be eagerly connected.

    You might want to do it in a try block, to avoid the application context failing to initialize because the JMS broker is not available (of course messaging will still fail, but the app will be up and ready to connect when the broker is available).

    • 0