PubretransmitTimedTask --- Executing timed publisher retransmission

Bruno Gong
Bruno Gong Member Posts: 1

Hi all,

My application meet some problem about sending message to solace server.

The actual production environment suddenly appeared, each message sent to different queue or topic in the same solace server frequently appeared in this log, and the message was retried to send many a time.The printed log is "PubretransmitTimedTask --- Executing timed publisher retransmission".

Firstly, I'm not sure the solace server some queue or topic is abnormal. But regarding the connection established by my application with solace server, is there a number of resending mechanisms to control this case? Because repeated resending consumes my appliction resources, so want has a threshold to control the number of times.

The lib version is


This is configure connect with solace serve simple code logic:

ConnectionFactory connectionFactory = SolJmsUtility.createConnectionFactory(url, username, password, vpn, null);
CachingConnectionFactory cachingConnectionFactory = new CachingConnectionFactory();
CachingConnectionFactory cachingConnectionFactory = (CachingConnectionFactory) context.getBean(cacheConnBeanName);
JmsTemplate jmstemplate = new JmsTemplate();

This is how a message is simple constructed to send to solace serve:

jmstemplate.send("queueName", session -> {
        TextMessage message = session.createTextMessage(body);
        return message;

Could someone please help me in this production case?




  • TomF
    TomF Member, Employee Posts: 406 Solace Employee

    Hi @Bruno Gong , do you have a support contract with Solace? If you need production support, that would be the best place to go.

    Generally I'd say a timed publisher re-transmit means that there was a temporary network problem to the broker.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 531 admin
    edited March 2022 #3

    Welcome to the forum! Timed publisher retransmit happens when the publisher is trying to send a Guaranteed message and has not yet received an acknowledgement from the broker within a specific period of time. (I believe it is 2 seconds). Due to message IDs that the API and broker use to keep in sync, it does not mean that your message will be double-published, so that's good.

    As Tom said, this can occur due to network problems (is it possible for you to check if any network issues during the timestamps you see), or maybe the CPU for your publisher app is very high and the API is getting starved and cannot process the broker's Guaranteed ACKs fast enough. It is also (maybe?) possible that the Solace broker is under heavy load during those times and not responding fast enough, but that is unlikely... but maybe something to check as well... CPU / network utilization of the broker during those times.

    Hope that helps!

    EDIT: BTW, it doesn't have anything to do with topics or queues... it's just the response/confirmation from the broker for your message isn't arriving fast enough.