[jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup?
Michael Musgrove (JIRA)
issues at jboss.org
Thu Dec 18 05:34:29 EST 2014
[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028600#comment-13028600 ]
Michael Musgrove commented on JBTM-2318:
----------------------------------------
I suspect it is historical. The messages were there when Tom ported the source from svn back in 2012 but I agree they do look like debug/trace messages to me.
Another separate conversation would be to instrument our environment beans so that these ports are available via the tooling.
> 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)
More information about the jbossts-issues
mailing list