[JBoss JIRA] (JBTM-2318) Too verbose startup?
by Michael Musgrove (JIRA)
[ 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)
9 years, 11 months
- 1
- 0
[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTM-2308:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from POST to MODIFIED
> New JTS record types are not showing up in the tooling
> ------------------------------------------------------
>
> Key: JBTM-2308
> URL: https://issues.jboss.org/browse/JBTM-2308
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Tooling
> Affects Versions: 4.17.23, 5.0.3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 4.17.27, 5.0.5
>
>
> When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record.
> I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it).
> What is missing is instrumentation for new types:
> {code}
> AssumedCompleteHeuristicTransaction
> AssumedCompleteHeuristicServerTransaction
> AssumedCompleteTransaction
> AssumedCompleteServerTransaction
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
- 1
- 0