MuleSoft · JMS Connector
JMS:PUBLISHING
Short answer
JMS:PUBLISHING means there was an error while publishing to the target queue or topic. Check the destination and the broker, then read the underlying cause with verbose logging on.
VerifiedLast verified
01Error text
Error type: JMS:PUBLISHING02Likely causes
- There is an error while publishing to the target queue or topic.
03How to fix it
- Check the destination name and type on the Publish operation.
- Check the broker's log for the rejected publish.
- Turn on verbose logging: in
log4j2.xmladd<AsyncLogger name="org.mule.extensions.jms" level="DEBUG"/>and<AsyncLogger name="org.mule.jms.commons" level="DEBUG"/>. Increase the logging level on the broker side as well. - Handle the failure with an error handler of type
JMS:PUBLISHING.
04Official documentation
→Related errors
- JMS:DESTINATION_NOT_FOUNDJMS:DESTINATION_NOT_FOUND means JMS Connector could not find or create the queue or topic. Check the destination name and that the connecting user is allowed to use or create it on the broker.
- JMS:ILLEGAL_BODYJMS:ILLEGAL_BODY means the message body is invalid or cannot be converted to a supported type. Transform the payload into a type the connector can publish before the Publish operation.
- JMS:CONNECTIVITYJMS:CONNECTIVITY means the JMS connection is no longer valid, and the connector disposes of it. Check the broker and configure a reconnection strategy so the app reconnects by itself.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer