[
https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2318:
----------------------------------------
Can we also add the following to the list of messages (relating to recovery) that should
be demoted to debug level:
{code}
ARJUNA012324: Start RecoveryActivators
ARJUNA012343: RecoveryManagerImple is ready. Socket listener is turned off.
ARJUNA012296: ExpiredEntryMonitor running at {0}
ARJUNA012332: Failed to establish connection to server
ARJUNA012304: Removing old transaction status manager item {0}
{code}
Too verbose startup?
--------------------
Key: JBTM-2318
URL:
https://issues.jboss.org/browse/JBTM-2318
Project: JBoss Transaction Manager
Issue Type: Task
Components: Transaction Core
Affects Versions: 5.0.4
Reporter: Mark Little
Assignee: Tom Jenkinson
Priority: Minor
At startup of the most basic example we see ...
Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager
addService
INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService
on port 52185
Dec 17, 2014 8:23:50 PM
com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185
Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1
with service com.arjuna.ats.arjuna.recovery.ActionStatusService
There's a separate conversation to be had about whether the INFO should be there
(DEBUG maybe?) but ignoring those why do we print the other lines at all?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)