Details
Description
When using the JMSTopicAppender or JMSQueueAppender calls to append result in JMSTopicManager calling send twice.
I can see that the code was refactored to support cleanup after exceptions, however the original call to send was not removed after a try/catch was introduced.
Index: core/src/main/java/org/apache/logging/log4j/core/net/JMSTopicManager.java =================================================================== --- core/src/main/java/org/apache/logging/log4j/core/net/JMSTopicManager.java (revision 1516828) +++ core/src/main/java/org/apache/logging/log4j/core/net/JMSTopicManager.java (revision ) @@ -104,7 +104,7 @@ if (info == null) { info = connect(context, factoryBindingName, topicBindingName, userName, password, false); } - super.send(object, info.session, info.publisher); + try { super.send(object, info.session, info.publisher); } catch (final Exception ex) {