NO-JIRA Log STOMP transaction starts with debug level instead of error

This commit is contained in:
Ville Skyttä 2018-10-08 23:08:21 +03:00 committed by Clebert Suconic
parent 202ae262d3
commit 74951d9221
2 changed files with 1 additions and 5 deletions

View File

@ -365,7 +365,7 @@ public class StompProtocolManager extends AbstractProtocolManager<StompFrame, St
}
public void beginTransaction(StompConnection connection, String txID) throws Exception {
ActiveMQServerLogger.LOGGER.stompBeginTX(txID);
ActiveMQServerLogger.LOGGER.debugf("-------------------------------Stomp begin tx: %s", txID);
if (transactedSessions.containsKey(txID)) {
ActiveMQServerLogger.LOGGER.stompErrorTXExists(txID);
throw new ActiveMQStompException(connection, "Transaction already started: " + txID);

View File

@ -1721,10 +1721,6 @@ public interface ActiveMQServerLogger extends BasicLogger {
@Message(id = 224030, value = "Could not cancel reference {0}", format = Message.Format.MESSAGE_FORMAT)
void errorCancellingRefOnBridge(@Cause Exception e, MessageReference ref2);
@LogMessage(level = Logger.Level.ERROR)
@Message(id = 224031, value = "-------------------------------Stomp begin tx: {0}", format = Message.Format.MESSAGE_FORMAT)
void stompBeginTX(String txID);
@LogMessage(level = Logger.Level.ERROR)
@Message(id = 224032, value = "Failed to pause bridge", format = Message.Format.MESSAGE_FORMAT)
void errorPausingBridge(@Cause Exception e);