Intermittent error - JCSMPErrorResponseException: 503: No Subscription Match [Subcode:70]

PubSub+ Event Broker
1

I am using Camel and Spring with Solace Pub Sub. The camel route is transacted, I am seeing the below exception while publishing to a topic intermittently - com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: No Subscription Match [Subcode:70]

So when the process starts, the initial events are published, but after some time, the below error is seen:

Detail log is as follows:

2024-07-05 09:05:12,367 [er[NPP.LSR.AU.IN.01]] WARN .c.s.s.TransactionErrorHandler - LSP6000013127952 - requestId - camel.messageId - direct://interceptFromEndpoint_NPP_LSR_AU_REQ_MQ - Transaction rollback (0x3059dc1e) redelivered(false) for (MessageId: ID:100.123.55.7695951908223c4140:5 on ExchangeId: DC3D5BB749E04C7-0000000000000000) caught: Heuristic completion: outcome state is mixed; nested exception is org.springframework.transaction.UnexpectedRollbackException: JMS transaction rolled back; nested exception is javax.jms.TransactionRolledBackException: Error committing - transaction rolled back (Transaction commit failed: (TransactedSessionId:7477, Name:c35b57bb7ec44cf0ae67aad5b5d033f2, CorrelationId:9, downgrade:false) (((Client name: psp-npp-lumpsumreportingservice-/1/00510002/lZ44LyKoTs Local addr: 100.123.68.248 Local port: 39276 Remote addr: dsole07l.unixtest.anz Remote port: 55443) - ) com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: No Subscription Match [Subcode:70]))

2

Hi @Sud ,

It seems like you probably have the “Reject Message to Sender on No Subscription Match” setting enabled in your client-profile. This is not the default setting, so someone might have enabled it on purpose? If your app isn’t going to respond to those events and make a decision to not publish events that aren’t being consumed then it’s probably best to disable it to have events in your design continue to flow and be available for future or intermittent consumers of those events.

Hope that helps,

Marc