[JBoss JIRA] (JBTM-2031) Intermittant RESTAT testListTransactionsWhenNoActiveTxns failure
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2031?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2031:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
PR passed
> Intermittant RESTAT testListTransactionsWhenNoActiveTxns failure
> ----------------------------------------------------------------
>
> Key: JBTM-2031
> URL: https://issues.jboss.org/browse/JBTM-2031
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Affects Versions: 5.0.0.CR1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.CR2
>
>
> testListTransactionsWhenNoActiveTxns socket read times out waiting for coordinator to respond. The test, http server and coordinator are all running in the same VM.
> Surefire test result:
> -------------------------------------------------------------------------------
> Test set: org.jboss.jbossts.star.test.TxSupportTest
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.277 sec <<< FAILURE!
> testListTransactionsWhenNoActiveTxns(org.jboss.jbossts.star.test.TxSupportTest) Time elapsed: 5.665 sec <<< ERROR!
> org.jboss.jbossts.star.provider.HttpResponseException: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:477)
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:466)
> at org.jboss.jbossts.star.util.TxSupport.getTransactions(TxSupport.java:143)
> at org.jboss.jbossts.star.util.TxSupport.getTransactions(TxSupport.java:139)
> at org.jboss.jbossts.star.test.TxSupportTest.testListTransactionsWhenNoActiveTxns(TxSupportTest.java:38)
> and test output was:
> log4j:WARN No appenders could be found for logger (org.jboss.logging).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> Nov 15, 2013 10:55:16 AM com.sun.grizzly.Controller logVersion
> INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.59 - 11/15/13 10:55 AM
> Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.PackagesResourceConfig init
> INFO: Scanning for root resource and provider classes in the packages:
> org.jboss.jbossts.star.service
> org.jboss.jbossts.star.provider
> org.jboss.jbossts.star.test
> Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses
> INFO: Root resource classes found:
> class org.jboss.jbossts.star.service.Coordinator
> class org.jboss.jbossts.star.test.BaseTest$TransactionalResource
> Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses
> INFO: Provider classes found:
> class org.jboss.jbossts.star.provider.TransactionStatusMapper
> class org.jboss.jbossts.star.provider.TMUnavailableMapper
> class org.jboss.jbossts.star.provider.NotFoundMapper
> class org.jboss.jbossts.star.provider.HttpResponseMapper
> Nov 15, 2013 10:55:17 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.9.1 09/14/2011 02:05 PM'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2031) Intermittant RESTAT testListTransactionsWhenNoActiveTxns failure
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2031?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2031:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/537
> Intermittant RESTAT testListTransactionsWhenNoActiveTxns failure
> ----------------------------------------------------------------
>
> Key: JBTM-2031
> URL: https://issues.jboss.org/browse/JBTM-2031
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Affects Versions: 5.0.0.CR1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.CR2
>
>
> testListTransactionsWhenNoActiveTxns socket read times out waiting for coordinator to respond. The test, http server and coordinator are all running in the same VM.
> Surefire test result:
> -------------------------------------------------------------------------------
> Test set: org.jboss.jbossts.star.test.TxSupportTest
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.277 sec <<< FAILURE!
> testListTransactionsWhenNoActiveTxns(org.jboss.jbossts.star.test.TxSupportTest) Time elapsed: 5.665 sec <<< ERROR!
> org.jboss.jbossts.star.provider.HttpResponseException: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:477)
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:466)
> at org.jboss.jbossts.star.util.TxSupport.getTransactions(TxSupport.java:143)
> at org.jboss.jbossts.star.util.TxSupport.getTransactions(TxSupport.java:139)
> at org.jboss.jbossts.star.test.TxSupportTest.testListTransactionsWhenNoActiveTxns(TxSupportTest.java:38)
> and test output was:
> log4j:WARN No appenders could be found for logger (org.jboss.logging).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> Nov 15, 2013 10:55:16 AM com.sun.grizzly.Controller logVersion
> INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.59 - 11/15/13 10:55 AM
> Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.PackagesResourceConfig init
> INFO: Scanning for root resource and provider classes in the packages:
> org.jboss.jbossts.star.service
> org.jboss.jbossts.star.provider
> org.jboss.jbossts.star.test
> Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses
> INFO: Root resource classes found:
> class org.jboss.jbossts.star.service.Coordinator
> class org.jboss.jbossts.star.test.BaseTest$TransactionalResource
> Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses
> INFO: Provider classes found:
> class org.jboss.jbossts.star.provider.TransactionStatusMapper
> class org.jboss.jbossts.star.provider.TMUnavailableMapper
> class org.jboss.jbossts.star.provider.NotFoundMapper
> class org.jboss.jbossts.star.provider.HttpResponseMapper
> Nov 15, 2013 10:55:17 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.9.1 09/14/2011 02:05 PM'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2020) org.jboss.jbossts.star.test.SpecTest#testHeuristic
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2020?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2020:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/537
> org.jboss.jbossts.star.test.SpecTest#testHeuristic
> --------------------------------------------------
>
> Key: JBTM-2020
> URL: https://issues.jboss.org/browse/JBTM-2020
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 4.17.17
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61-jdbcobjectst...
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.jbossts.star.test.SpecTest
> -------------------------------------------------------------------------------
> Tests run: 14, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 47.599 sec <<< FAILURE!
> testHeuristic(org.jboss.jbossts.star.test.SpecTest) Time elapsed: 6.446 sec <<< ERROR!
> org.jboss.jbossts.star.provider.HttpResponseException: java.net.SocketTimeoutException: Read timed out
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:507)
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:462)
> at org.jboss.jbossts.star.util.TxSupport.commitTx(TxSupport.java:176)
> at org.jboss.jbossts.star.test.SpecTest.testHeuristic(SpecTest.java:269)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
> at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:78)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:690)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
> at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:473)
> ... 33 more
> {code}
> {code}
> log4j:WARN No appenders could be found for logger (org.jboss.logging).
> log4j:WARN Please initialize the log4j system properly.
> Nov 11, 2013 5:28:56 PM com.sun.grizzly.Controller logVersion
> INFO: Starting Grizzly Framework 1.9.18-i - Mon Nov 11 17:28:56 GMT 2013
> Nov 11, 2013 5:29:00 PM com.sun.jersey.api.core.PackagesResourceConfig init
> INFO: Scanning for root resource and provider classes in the packages:
> org.jboss.jbossts.star.service
> org.jboss.jbossts.star.provider
> org.jboss.jbossts.star.test
> Nov 11, 2013 5:29:00 PM com.sun.jersey.api.core.ScanningResourceConfig logClasses
> INFO: Root resource classes found:
> class org.jboss.jbossts.star.test.BaseTest$TransactionalResource
> class org.jboss.jbossts.star.service.Coordinator
> Nov 11, 2013 5:29:00 PM com.sun.jersey.api.core.ScanningResourceConfig logClasses
> INFO: Provider classes found:
> class org.jboss.jbossts.star.provider.HttpResponseMapper
> class org.jboss.jbossts.star.provider.NotFoundMapper
> class org.jboss.jbossts.star.provider.TransactionStatusMapper
> class org.jboss.jbossts.star.provider.TMUnavailableMapper
> Nov 11, 2013 5:29:00 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.5 01/14/2011 12:36 PM'
> 17:29:02,706 {hread(0)} () [INFO ,arjuna ] ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 42379
> 17:29:02,708 {hread(0)} () [INFO ,arjuna ] ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 42379
> 17:29:05,415 {hread(0)} () [INFO ,arjuna ] ARJUNA012170: TransactionStatusManager started on port 42379 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> 17:29:09,234 {n Reaper} () [WARN ,arjuna ] ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffac118314:de42:528113d8:b in state RUN
> 17:29:09,235 {Worker 0} () [WARN ,arjuna ] ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,10,Grizzly] successfully canceled TX 0:ffffac118314:de42:528113d8:b
> 17:29:35,502 {hread(2)} () [WARN ,arjuna ] ARJUNA012073: BasicAction.End() - prepare phase of action-id 0:ffffac118314:de42:528113d8:33 failed.
> 17:29:35,502 {hread(2)} () [WARN ,arjuna ] ARJUNA012075: Action Aborting
> 17:29:35,509 {hread(2)} () [WARN ,arjuna ] ARJUNA012091: Top-level abort of action 0:ffffac118314:de42:528113d8:33 received TwoPhaseOutcome.FINISH_ERROR from com.arjuna.ats.arjuna.coordinator.AbstractRecord
> 17:29:39,975 {hread(0)} () [WARN ,arjuna ] ARJUNA012073: BasicAction.End() - prepare phase of action-id 0:ffffac118314:de42:528113d8:3d failed.
> 17:29:39,976 {hread(0)} () [WARN ,arjuna ] ARJUNA012075: Action Aborting
> 17:29:39,982 {hread(0)} () [WARN ,arjuna ] ARJUNA012091: Top-level abort of action 0:ffffac118314:de42:528113d8:3d received TwoPhaseOutcome.FINISH_ERROR from com.arjuna.ats.arjuna.coordinator.AbstractRecord
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2031) Intermittant RESTAT testListTransactionsWhenNoActiveTxns failure
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2031:
--------------------------------------
Summary: Intermittant RESTAT testListTransactionsWhenNoActiveTxns failure
Key: JBTM-2031
URL: https://issues.jboss.org/browse/JBTM-2031
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: REST
Affects Versions: 5.0.0.CR1
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.0.0.CR2
testListTransactionsWhenNoActiveTxns socket read times out waiting for coordinator to respond. The test, http server and coordinator are all running in the same VM.
Surefire test result:
-------------------------------------------------------------------------------
Test set: org.jboss.jbossts.star.test.TxSupportTest
-------------------------------------------------------------------------------
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.277 sec <<< FAILURE!
testListTransactionsWhenNoActiveTxns(org.jboss.jbossts.star.test.TxSupportTest) Time elapsed: 5.665 sec <<< ERROR!
org.jboss.jbossts.star.provider.HttpResponseException: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:477)
at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:466)
at org.jboss.jbossts.star.util.TxSupport.getTransactions(TxSupport.java:143)
at org.jboss.jbossts.star.util.TxSupport.getTransactions(TxSupport.java:139)
at org.jboss.jbossts.star.test.TxSupportTest.testListTransactionsWhenNoActiveTxns(TxSupportTest.java:38)
and test output was:
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Nov 15, 2013 10:55:16 AM com.sun.grizzly.Controller logVersion
INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.59 - 11/15/13 10:55 AM
Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.PackagesResourceConfig init
INFO: Scanning for root resource and provider classes in the packages:
org.jboss.jbossts.star.service
org.jboss.jbossts.star.provider
org.jboss.jbossts.star.test
Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses
INFO: Root resource classes found:
class org.jboss.jbossts.star.service.Coordinator
class org.jboss.jbossts.star.test.BaseTest$TransactionalResource
Nov 15, 2013 10:55:17 AM com.sun.jersey.api.core.ScanningResourceConfig logClasses
INFO: Provider classes found:
class org.jboss.jbossts.star.provider.TransactionStatusMapper
class org.jboss.jbossts.star.provider.TMUnavailableMapper
class org.jboss.jbossts.star.provider.NotFoundMapper
class org.jboss.jbossts.star.provider.HttpResponseMapper
Nov 15, 2013 10:55:17 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.9.1 09/14/2011 02:05 PM'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2030) Cannot import into Eclipse
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-2030:
-----------------------------------
Summary: Cannot import into Eclipse
Key: JBTM-2030
URL: https://issues.jboss.org/browse/JBTM-2030
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.CR2
If I remove 4bd2060c37642dc66a3cd6c451c68cf764f6736d (JBTM-2015) then it will import OK again
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2016) Cannot stop WildFly recovery manager when configured with volatile store
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2016?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2016:
--------------------------------
Fix Version/s: 5.0.0.CR2
> Cannot stop WildFly recovery manager when configured with volatile store
> ------------------------------------------------------------------------
>
> Key: JBTM-2016
> URL: https://issues.jboss.org/browse/JBTM-2016
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Configuration
> Affects Versions: 5.0.0.CR1
> Reporter: gui borland
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.CR2
>
>
> When using jboss 5, i was able to configure a 'Volatile' action store. I understand it's not the most robust store, but in my case performance is more important than tx consistency.
> I tried to configure the Volatile store in AS 7.1.3 as well (using a custom jbossts-properties.xml file defined via the com.arjuna.ats.arjuna.common.propertiesFile systemsetting ), but doing that breaks the recovery thread. It prints out a warning message (Volatile storage does not support recovery blablabla...). That would be fine, but this recovery issue also prevents jboss from shutting down cleanly. I have to kill it to stop it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2016) Cannot stop WildFly recovery manager when configured with volatile store
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2016?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2016:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Cannot stop WildFly recovery manager when configured with volatile store
> ------------------------------------------------------------------------
>
> Key: JBTM-2016
> URL: https://issues.jboss.org/browse/JBTM-2016
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Configuration
> Affects Versions: 5.0.0.CR1
> Reporter: gui borland
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.CR2
>
>
> When using jboss 5, i was able to configure a 'Volatile' action store. I understand it's not the most robust store, but in my case performance is more important than tx consistency.
> I tried to configure the Volatile store in AS 7.1.3 as well (using a custom jbossts-properties.xml file defined via the com.arjuna.ats.arjuna.common.propertiesFile systemsetting ), but doing that breaks the recovery thread. It prints out a warning message (Volatile storage does not support recovery blablabla...). That would be fine, but this recovery issue also prevents jboss from shutting down cleanly. I have to kill it to stop it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (JBTM-2021) Make sure that REST-AT bridge recovery tests clear object store after execution
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2021?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2021:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Make sure that REST-AT bridge recovery tests clear object store after execution
> -------------------------------------------------------------------------------
>
> Key: JBTM-2021
> URL: https://issues.jboss.org/browse/JBTM-2021
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 5.0.0.CR2
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/338/PROFILE=MAIN,...
> Currently REST-AT bridge recovery tests clear object store before their execution. However, as in provided URL, there is a possibility that there are some junk in it which can be harmful for the upcoming tests. As in the URL, regular REST-AT bridge test's resource received additional request from the coordinator. It happened because both recovery and regular tests use same resources (i.e. same URLs).
> See two terminateParticipant(txstatus=TransactionCommitted) invocations at the bottom.
> {code}
> [0m[0m00:51:57,834 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-2) LoggingRestATResource.resetInvocations()
> [0m[33m00:51:58,440 WARN [org.jboss.narayana.rest.integration.RecoveryManager] (default task-5) Inbound bridge is not available.: org.jboss.narayana.rest.integration.api.ParticipantException: Inbound bridge is not available.
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeParticipant.startBridge(InboundBridgeParticipant.java:137) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeParticipant.rollback(InboundBridgeParticipant.java:122) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:184) [restat-integration-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:133) [restat-integration-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:54) [restat-integration-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:73) [restat-integration-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.<init>(InboundBridgeManager.java:64) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:52) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeFilter.startBridge(InboundBridgeFilter.java:83) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeFilter.filter(InboundBridgeFilter.java:63) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:248) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:234) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:221) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.5.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:59) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:218) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:205) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:134) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:138) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:622) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> [0m[0m00:51:58,485 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-5) LoggingXAResource.start
> [0m[0m00:51:58,502 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-10) LoggingXAResource.end
> [0m[0m00:51:58,502 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-10) LoggingXAResource.prepare
> [0m[0m00:51:58,510 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://localhost:8080/rest-tx-bridge-test/logging-participant-resource/te...
> [0m[0m00:51:58,510 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffffac118321:b4a8:52817b30:17
> [0m[31m00:51:58,514 ERROR [io.undertow.request] (default task-11) Servlet request failed HttpServerExchange{ PUT /rest-at-participant/0:ffffac118321:b4a8:52817b30:17}: org.jboss.resteasy.spi.UnhandledException: org.jboss.narayana.rest.integration.api.ParticipantException: Inbound bridge is not available.
> at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:76) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:212) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:149) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:372) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.5.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:59) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:218) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:205) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:134) [undertow-servlet-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:138) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:622) [undertow-core-1.0.0.Beta20.jar:1.0.0.Beta20]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: org.jboss.narayana.rest.integration.api.ParticipantException: Inbound bridge is not available.
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeParticipant.startBridge(InboundBridgeParticipant.java:137) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.bridge.inbound.InboundBridgeParticipant.commit(InboundBridgeParticipant.java:83) [restat-bridge-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.integration.ParticipantResource.commit(ParticipantResource.java:211) [restat-integration-5.0.0.CR2-SNAPSHOT.jar:]
> at org.jboss.narayana.rest.integration.ParticipantResource.terminate(ParticipantResource.java:118) [restat-integration-5.0.0.CR2-SNAPSHOT.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:280) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:234) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:221) [resteasy-jaxrs-3.0.5.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.5.Final.jar:]
> ... 24 more
> [0m[31m00:51:58,519 ERROR [io.undertow.request] (default task-11) Blocking request failed HttpServerExchange{ PUT /rest-at-participant/0:ffffac118321:b4a8:52817b30:17}: java.lang.NullPointerException
> at io.undertow.servlet.handlers.ServletDebugPageHandler.escapeBodyText(ServletDebugPageHandler.java:102)
> at io.undertow.servlet.handlers.ServletDebugPageHandler.writeLabel(ServletDebugPageHandler.java:95)
> at io.undertow.servlet.handlers.ServletDebugPageHandler.handleRequest(ServletDebugPageHandler.java:78)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:205)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:134)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:138)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:622)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> [0m[0m00:51:58,534 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-12) LoggingRestATResource.terminateParticipant(txstatus=TransactionCommitted)
> [0m[0m00:51:58,650 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-13) LoggingRestATResource.terminateParticipant(txstatus=TransactionPrepared)
> [0m[0m00:51:58,699 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-14) LoggingRestATResource.terminateParticipant(txstatus=TransactionCommitted)
> [0m[0m00:51:58,702 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-15) LoggingXAResource.commit
> [0m[0m00:51:58,734 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-16) LoggingRestATResource.getInvocations()
> {code}
> To fix it, just invoke clearObjectStore() at the beginning of org.jboss.narayana.rest.bridge.inbound.test.integration.AbstractTestCase#stopContainer()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months