Error Log page This option lists all the error logs related to Message Transfers and includes the ErrorSignalMessageId, ErrorDetail and Timestamp. The messages can be sorted by clicking on the up and down arrows which helps to search for specific messages. Queue Monitoring Domibus uses JMS queues to handle the messages: Destination JNDI name Comment Description type jms/domibus.internal.dispatch.queue No This queue is used for Queue redelivery because scheduling messages for redelivery of MSH sending via the MSH messages is handled via ebMS3/AS4 jms/domibus.internal.notification.unknown Notifications about received Queue messages (by the MSH) that do not match any backend routing criteria will be sent to this queue. In production environment this queue should be monitored in order to handle those messages manually Topic jms/domibus.internal.command This topic is used for sending commands to all nodes in a cluster. For example, it is used after a PMode was uploaded in order to notify all nodes to update their PMode cache (in case caching is enabled) jms/domibus.backend.jms.replyQueue This queue is used for Queue sending replies back to the sender of a message. Replies contain: a correlationId, ebMS3 messageId (if possible), error messages (if available) jms/domibus.backend.jms.outQueue Messages received by the Queue MSH (that match the routing criteria for the JMS plugin) will be sent to this queue
Error Log page This option lists all the error logs related to Message Transfers and includes the ErrorSignalMessageId, ErrorDetail and Timestamp. The messages can be sorted by clicking on the up and down arrows which helps to search for specific messages. Queue Monitoring Domibus uses JMS queues to handle the messages: Destination type JNDI name Comment Description Queue jms/domibus.internal.dispatch.queue No redelivery because redelivery of MSH messages is handled via ebMS3/AS4 This queue is used for scheduling messages for sending via the MSH Queue jms/domibus.internal.notification.unknown Notifications about received messages (by the MSH) that do not match any backend routing criteria will be sent to this queue. In production environment this queue should be monitored in order to handle those messages manually Topic jms/domibus.internal.command This topic is used for sending commands to all nodes in a cluster. For example, it is used after a PMode was uploaded in order to notify all nodes to update their PMode cache (in case caching is enabled) Queue jms/domibus.backend.jms.replyQueue This queue is used for sending replies back to the sender of a message. Replies contain: a correlationId, ebMS3 messageId (if possible), error messages (if available) Queue jms/domibus.backend.jms.outQueue Messages received by the MSH (that match the routing criteria for the JMS plugin) will be sent to this queue
Administration%20Guide%20v1.6_comments_2016-01-05-Cosmin.docx