Symptom
An integration flow using the AMQP sender adapter to consume messages from an SAP Event Mesh queue fails to deploy in SAP Integration Suite, Cloud Integration. The runtime status of the integration flow remains in error and message polling does not start. Messages produced by the source system (for example, S/4HANA Cloud) accumulate in the Event Mesh queue and are not consumed.
The Status Details view under Monitor Message Processing, Manage Integration Content shows the following deployment error:
[CONTENT][CONTENT_DEPLOY][InstanceError] : {"message":"POLL_FAILED",
"childMessageInstances":[{"message":"EXCEPTION",
"childMessageInstances":[{"message":"CAUSE",
"parameters":["org.apache.qpid.jms.provider.ProviderException:
invalid subscription target (<namespace>/<queue-name>) (220034)
[condition = amqp:not-allowed]"]}],
"parameters":["javax.jms.JMSException: invalid subscription target
(<namespace>/<queue-name>) (220034) [condition = amqp:not-allowed]"]}],
"parameters":["amqpwss://enterprise-messaging-messaging-gateway..."]}
Read more...
Environment
SAP Event Mesh
SAP Integration Suite
Product
Keywords
AMQP, AMQP sender adapter, SAP Event Mesh, Event Mesh, Solace, invalid subscription target, 220034, amqp:not-allowed, POLL_FAILED, ProviderException, JMSException, org.apache.qpid.jms.provider.ProviderException, javax.jms.JMSException, queue name , KBA , BC-CP-EM-MES , Event Mesh , 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.
SAP Knowledge Base Article - Preview