[JBoss JIRA] (JBTM-2545) Use consistent naming scheme for ORB jbossts-properties files in the repo
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2545?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2545:
--------------------------------
Description:
This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb.
Plus the fact that narayana-jacorb module has narayana-idlj file in (which is an error IMO) - and the converse is also true.
was:This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb.
> Use consistent naming scheme for ORB jbossts-properties files in the repo
> -------------------------------------------------------------------------
>
> Key: JBTM-2545
> URL: https://issues.jboss.org/browse/JBTM-2545
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Build System, Testing
> Reporter: Tom Jenkinson
> Priority: Minor
> Fix For: 5.next
>
>
> This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb.
> Plus the fact that narayana-jacorb module has narayana-idlj file in (which is an error IMO) - and the converse is also true.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2545) Use consistent naming scheme for ORB jbossts-properties files in the repo
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-2545:
-----------------------------------
Summary: Use consistent naming scheme for ORB jbossts-properties files in the repo
Key: JBTM-2545
URL: https://issues.jboss.org/browse/JBTM-2545
Project: JBoss Transaction Manager
Issue Type: Task
Components: Build System, Testing
Reporter: Tom Jenkinson
Priority: Minor
Fix For: 5.next
This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-2544:
----------------------------------
Steps to Reproduce:
Add "<jts/>" to the transaction subsystem configuration in standalone/configuration/standalone-rts.xml
>From Narayana code base execute the following:
{code}
./build.sh -f rts/at/bridge/pom.xml clean test -Parq -Dtest=InboundBridgeRecoveryTestCase#testCrashBeforeCommit
{code}
> RTS inbound bridge recovery does not work with JTS
> --------------------------------------------------
>
> Key: JBTM-2544
> URL: https://issues.jboss.org/browse/JBTM-2544
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: REST
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> If JTS is enabled, crash scenario when system fails just before the commit does not complete correctly. Instead of being committed, resource is rolled back by XARecoveryModule.
> In JTA case, XARecoveryModule does not find any XAResourceRecords and bridge recovery is handled by InboundBridgeRecoveryModule.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-2544:
-------------------------------------
Summary: RTS inbound bridge recovery does not work with JTS
Key: JBTM-2544
URL: https://issues.jboss.org/browse/JBTM-2544
Project: JBoss Transaction Manager
Issue Type: Bug
Components: REST
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.next
If JTS is enabled, crash scenario when system fails just before the commit does not complete correctly. Instead of being committed, resource is rolled back by XARecoveryModule.
In JTA case, XARecoveryModule does not find any XAResourceRecords and bridge recovery is handled by InboundBridgeRecoveryModule.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2534:
-------------------------------------
I agree - my understanding is Resource should be free to cleanup after commit unless it was a heuristic.
> 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)
9 years, 1 month
[JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2534:
----------------------------------------
I debugged CrashRecovery05_1_Test01 but all the failures seem to be similar.
Client starts a txn, calls a server which enlists 2 resources one of which crashes during 2PC.
During recovery the resource is recovered. BasicAciont#phase2Commit calls BasicAction#doForget after successfully committing the resource.
When running with JacORB the resource CORBA object is destroyed after commit so the forget call is not processed (BasicAction#doForget processing receives org.omg.CORBA.OBJECT_NOT_EXIST).
When running with JdkORB the resource CORBA object is not destroyed after commit so the forget call is processed.
The actual test maintains a trace of the last call the resource processed which should be commit. But since the forget call reaches the resource in the JdkORB case the trace is unexpected.
My interpretation of the problem is that the resource trace in ResourceImpl02#forget, for example, in the default case should not be updating the resource trace - ie the resource test code is wrong. JacORB only works because the remote resource corba object never received the forget() call.
> 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)
9 years, 1 month
[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 edited comment on JBTM-2318 at 10/27/15 6:21 AM:
---------------------------------------------------------------
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:
{code}
-Djava.util.logging.SimpleFormatter.format="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n"
{code}
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.
was (Author: tomjenkinson):
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)
9 years, 1 month