[jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup?

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028763#comment-13028763 ] 

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?

>From looking at the log statements there looks to be three statements, its the way the log messages are formatted that is causing each of the statements to bridge two lines. The logging format looks to be the format generated by JDK logging rather than log4j so I guess this is in an IDE?

{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?

> 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)