[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2318: ------------------------------------- Yeah, I haven't upgraded the logging for the component. The only thing I can think is that maybe the default used to be WARN or something? {code} 2014-12-18 16:30:49,755 [main] INFO (ats.arjuna :88 ) - ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 51214 2014-12-18 16:30:49,765 [main] INFO (ats.arjuna :327 ) - ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 51214 2014-12-18 16:30:49,765 [main] INFO (ats.arjuna :138 ) - ARJUNA012170: TransactionStatusManager started on port 51214 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService {code} I am happy for those statements to move down to debug but the reason they are info is the default option seems to be to choose a random port so it might be the case then that people would all enable debug just to get at that. I can see why with multiple processes on the same machine why electing a port dynamically has some advantages but I know that WFLY at least configure a default of 4713. (4712 for recovery port). Why don't we use those defaults and only then log the statement at INFO if the user changes the port to 0? -- This message was sent by Atlassian JIRA (v6.3.11#6341)