Pergunta

I'm connecting to a Websphere MQ topic with a durable subscription using Spring:

<jms:message-driven-channel-adapter
    channel="springChannel"
    destination-name="wmqTopic"
    connection-factory="connectionFactory"
    destination-resolver="destinationResolver"
    subscription-durable="true"
    durable-subscription-name="myDurableSubscriptionName" />

Since this is a durable subscription, I'm concious that whilst the application is not subscribed to the topic in WMQ the messages for next time I connect are piling up either on disk or in memory. I'm concerned that as a result WMQ will run out of either memory or disk space unless a timeout is specified somewhere.

Does anyone know what my options are for specifying the timeout? Should it be in the message-driven-channel-adapter or WMQ, or should it be an expiry set on the message before publication?

Foi útil?

Solução

or should it be an expiry set on the message before publication?

Yes.

Licenciado em: CC-BY-SA com atribuição
Não afiliado a StackOverflow
scroll top