SAP Knowledge Base Article - Preview

2858931 - 'The number of messages in the transaction exceeds the limit' using JMS adapter in SAP Cloud Integration

Symptom

You are using SAP Cloud Integration with Enterprise Messaging capabilities enabled. When triggering an Integration Flow with a JMS Adapter configured, you get the error below:

  • org.springframework.transaction.UnexpectedRollbackException: JMS transaction rolled back; nested exception is javax.jms.TransactionRolledBackException: Error committing - transaction rolled back (Transaction '1749' unexpectedly rolled back during commit attempt. (((Client name: vsa7698153/54172/#841e0652 Local addr: <IP>:<port> Remote addr: <hostname>:<port>) - ) com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: Transaction Failure: The number of messages in the transaction exceeds the limit [Subcode:49])), cause: ((Client name: vsa7698153/54172/#841e0652 Local addr: <IP>:<port> Remote addr: <hostname>:<port>) - ) com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: Transaction Failure: The number of messages in the transaction exceeds the limit [Subcode:49] 


Read more...

Environment

  • Cloud Integration
  • SAP Integration Suite

Product

SAP Integration Suite all versions

Keywords

SAP Cloud Integration, SAP CPI, tenant, IFlow, Integration Flow, deployment, HCI tooling, message flow, Global account, Subaccount, sub account, entitlement, JMS, Resources, Limit, Size, Queue, Adapter, Broker, 503 , KBA , LOD-HCI-PI-OPS , Cloud Operations , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.