[JBoss JIRA] (JBTM-2318) Too verbose startup?
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2318:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/932
The pull request is to demote some of the log messages.
To actually change the format of the logger users can configure the JDK logger however they would normally do so. For example I found this useful: -Djava.util.logging.SimpleFormatter.format="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n"
Alternatively they could replace the entire default JAVA_HOME/lib/logging.properties file with java.util.logging.config.file.
I am reluctant to make our scripts do the former as it would seem to override their system defaults.
> 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
> Fix For: 5.next
>
>
> 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.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner.
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1860:
-------------------------------------
AtomicActionExpiryScanner is described here: http://narayana.io/docs/product/index.html#d0e1211
Please consider filing an issue on the product docs if the documentation is missing from there.
> Please document TransactionStatusManager scanner.
> -------------------------------------------------
>
> Key: JBTM-1860
> URL: https://issues.jboss.org/browse/JBTM-1860
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Documentation
> Environment: JBoss EAP 5.x and 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them.
> Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner.
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-1860.
-------------------------------
Fix Version/s: (was: 5.next)
Resolution: Rejected
> Please document TransactionStatusManager scanner.
> -------------------------------------------------
>
> Key: JBTM-1860
> URL: https://issues.jboss.org/browse/JBTM-1860
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Documentation
> Environment: JBoss EAP 5.x and 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them.
> Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris reassigned JBTM-2534:
-------------------------------------
Assignee: Michael Musgrove (was: Gytis Trikleris)
> HQStore crashrec failures on QA_JTS_JDKORB
> ------------------------------------------
>
> Key: JBTM-2534
> URL: https://issues.jboss.org/browse/JBTM-2534
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Priority: Critical
> Fix For: 5.next
>
>
> Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/...
> Normally run to completion but lots of crash rec failures:
> {quote}
> Total time: 525 minutes 19 seconds
> Test Failures:
> crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s)
> crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s)
> crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s)
> crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s)
> crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s)
> crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s)
> crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s)
> crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s)
> crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s)
> crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s)
> crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s)
> crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s)
> crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s)
> crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s)
> crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s)
> crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s)
> crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s)
> crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s)
> crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s)
> crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s)
> crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s)
> crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s)
> crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s)
> crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s)
> crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s)
> crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s)
> crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s)
> crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s)
> crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s)
> crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s)
> crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s)
> crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s)
> crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s)
> crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s)
> crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s)
> crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s)
> crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s)
> crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s)
> crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s)
> crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s)
> crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s)
> crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s)
> crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s)
> crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s)
> crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s)
> crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s)
> crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s)
> crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s)
> crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s)
> crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s)
> crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s)
> crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s)
> crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s)
> crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s)
> crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s)
> crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s)
> crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s)
> crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s)
> crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s)
> crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s)
> crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s)
> crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s)
> crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s)
> crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s)
> crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s)
> crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s)
> crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s)
> crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s)
> crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s)
> crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s)
> crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s)
> crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s)
> crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s)
> crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s)
> crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s)
> crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s)
> crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s)
> crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s)
> crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s)
> crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s)
> crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s)
> crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s)
> crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s)
> crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s)
> crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s)
> crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s)
> crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s)
> crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s)
> Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2542:
--------------------------------------
Summary: Migrate performance tests to the performance repo
Key: JBTM-2542
URL: https://issues.jboss.org/browse/JBTM-2542
Project: JBoss Transaction Manager
Issue Type: Task
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.later
We still have lots of performance related unit tests that need migrating:
rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java
ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java
ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java
ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java
ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java
ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java
ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java
ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java
ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java
ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java
ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance1.java
ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance2.java
ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance3.java
ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java
ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java
ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java
ArjunaJTA/jta/tests/classes/io/narayana/perf/product/Product.java
ArjunaJTA/jta/tests/classes/io/narayana/perf/product/ProductWorker.java
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created JBTM-2541:
--------------------------------------
Summary: Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store
Key: JBTM-2541
URL: https://issues.jboss.org/browse/JBTM-2541
Project: JBoss Transaction Manager
Issue Type: Bug
Affects Versions: 5.2.5.Final
Reporter: Ondřej Chaloupka
Priority: Minor
Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like
{{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}.
If HornetQ object store is not really used the log messages should be changed to correspond to current state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-2541?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka updated JBTM-2541:
-----------------------------------
Description:
Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like
{{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}.
If HornetQ object store is not really used the log messages should be changed to correspond to the state.
was:
Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like
{{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}.
If HornetQ object store is not really used the log messages should be changed to correspond to current state.
> Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store
> --------------------------------------------------------------------------------------------
>
> Key: JBTM-2541
> URL: https://issues.jboss.org/browse/JBTM-2541
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 5.2.5.Final
> Reporter: Ondřej Chaloupka
> Priority: Minor
>
> Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like
> {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}.
> If HornetQ object store is not really used the log messages should be changed to correspond to the state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months