January 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1396) TXBridge quickstart with three servers fails because of not enough PermGen space

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1396?page=com.atlassian.jira.plugin.... ] Paul Robinson reopened JBTM-1396: --------------------------------- > TXBridge quickstart with three servers fails because of not enough PermGen space > -------------------------------------------------------------------------------- > > Key: JBTM-1396 > URL: https://issues.jboss.org/browse/JBTM-1396 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > > See: > http://172.17.131.2/job/btny-narayana-quickstarts/166 > http://172.17.131.2/job/btny-narayana-quickstarts/167 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1396) TXBridge quickstart with three servers fails because of not enough PermGen space

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1396?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1396: ------------------------------------- I've had second thoughts about putting these memory settings on the quickstarts. The quickstarts act as documentation and advocate the right way to use our technology. Setting high memory settings in our quickstarts will tell the user that they need lots of memory to use JBossAS which is certainly not the case. It's fine us using these settings for our internal tests though as users won't see them. > TXBridge quickstart with three servers fails because of not enough PermGen space > -------------------------------------------------------------------------------- > > Key: JBTM-1396 > URL: https://issues.jboss.org/browse/JBTM-1396 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > > See: > http://172.17.131.2/job/btny-narayana-quickstarts/166 > http://172.17.131.2/job/btny-narayana-quickstarts/167 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1396) TXBridge quickstart with three servers fails because of not enough PermGen space

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1396?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1396: -------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > TXBridge quickstart with three servers fails because of not enough PermGen space > -------------------------------------------------------------------------------- > > Key: JBTM-1396 > URL: https://issues.jboss.org/browse/JBTM-1396 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > See: > http://172.17.131.2/job/btny-narayana-quickstarts/166 > http://172.17.131.2/job/btny-narayana-quickstarts/167 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Summary: Deploy REST-AT support as a JBossAS subsystem and module (was: Deploy REST-AT support as a JBossAS Subsystem) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS Subsystem

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Description: Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). The subsystem would need to: * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. * Deploy the coordinator endpoint. The module would need to contain the REST-AT coordinator code and the client libraries. h3. Open Issues Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. was: Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). The subsystem would need to: * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. * Deploy the coordinator endpoint. The module would need to contain the REST-AT coordinator code and the client libraries. > Deploy REST-AT support as a JBossAS Subsystem > --------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS Subsystem

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Description: Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). The subsystem would need to: * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. * Deploy the coordinator endpoint. The module would need to contain the REST-AT coordinator code and the client libraries. was: Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > Deploy REST-AT support as a JBossAS Subsystem > --------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS Subsystem

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1365: -------------------------------- Summary: Deploy REST-AT support as a JBossAS Subsystem (was: Deploy REST-AT support as a JBoss Module) > Deploy REST-AT support as a JBossAS Subsystem > --------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1398) Review TXFramework's subsystem usage (and change if required)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ] Work on JBTM-1398 started by Paul Robinson. > Review TXFramework's subsystem usage (and change if required) > ------------------------------------------------------------- > > Key: JBTM-1398 > URL: https://issues.jboss.org/browse/JBTM-1398 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > We need to review the various options for including TXFramework subsytem code in AS7. > 1. Create a new Subsytem > 2. Leave it in the XTS one > Also do we want all the subsytem code to live in the narayana codebase, rather than the AS7 one? > Pros: don't need to rebuild AS7 when changing it. Don't need to raise a pull req on AS7 when we want to change it. > Cons: We have to maintain it. In the past AS7 developers have made changes as the internals of AS7 change. We don't want to have to do this ourselves. > I suggest we look at how other projects are doing this before committing to a particular method. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1293) ATBridgeTest#testSimple counter isn't incremented

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1293?page=com.atlassian.jira.plugin.... ] Paul Robinson edited comment on JBTM-1293 at 1/8/13 3:09 AM: ------------------------------------------------------------- For now, I've increased the TRANSPORT_TIMEOUT from 30s to 60s which might help. I've also added some debug output to confirm that it is the TRANSPORT_TIMEOUT that is firing. These changes are now merged in. If this issue doesn't happen again before M2, close it as resolved. was (Author: paul.robinson): For now, I've increased the TRANSPORT_TIMEOUT from 30s to 60s which might help. I've also added some debug output to confirm that it is the TRNASPORT_TIMEOUT that is firing. > ATBridgeTest#testSimple counter isn't incremented > ------------------------------------------------- > > Key: JBTM-1293 > URL: https://issues.jboss.org/browse/JBTM-1293 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 3 days > Time Spent: 6 hours > Remaining Estimate: 2 days, 2 hours > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/21/... > {code} > @Test > public void testSimple() throws Exception > { > ut.begin(); > client.incrementCounter(1); > ut.commit(); > ut.begin(); > int counter = client.getCounter(); > ut.commit(); > Assert.assertEquals(1, counter); > } > {code} > Even though the first transaction should have committed an update to the counter, it is still set to zero in the second transaction. > This happens intermittently (once so far). It also happened on Beacon which is notorious for test failures caused by things going slowly. I would suspect that the bridged JTA transaction in the first transaction hasn't quite finished the commit when the second transaction is begun. > If the WS-AT coordinator sends an async commit to the participants and an async committed to the client, then this problem could happen if the client's 'committed' is received before the participant's 'commit' message. > To verify this we need to check that the coordinator sends an async (@OneWay) commit message to the participant. In which case the simplest solution is to add a 3sec delay between the two transactions. We should also look for other tests that may be affected. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1400) There is no transaction data associated with the thread in IndirectTXManagementTest

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1400?page=com.atlassian.jira.plugin.... ] Gytis Trikleris logged work on JBTM-1400: ----------------------------------------- Author: Gytis Trikleris Created on: 07/Jan/13 12:23 PM Start Date: 07/Jan/13 12:22 PM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Remaining Estimate: 1 day, 4 hours (was: 2 days) Time Spent: 4 hours Worklog Id: (was: 12428314) > There is no transaction data associated with the thread in IndirectTXManagementTest > ----------------------------------------------------------------------------------- > > Key: JBTM-1400 > URL: https://issues.jboss.org/browse/JBTM-1400 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 4 hours > Remaining Estimate: 1 day, 4 hours > > See: > http://172.17.131.2/job/jbossts-narayana-java7/100 > http://172.17.131.2/job/jbossts-narayana-java7/102 > http://172.17.131.2/job/jbossts-narayana-java7/103 > {noformat} > [0m[31m20:15:27,384 ERROR [org.jboss.as.ejb3.invocation] (http-/127.0.0.1:8080-14) JBAS014134: EJB Invocation failed on component Service2Impl for method public abstract javax.ws.rs.core.Response org.jboss.narayana.txframework.functional.rest.at.simpleEJB.Service2.someServiceRequest(java.lang.String) throws org.jboss.narayana.txframework.functional.common.SomeApplicationException: javax.ejb.EJBException: org.jboss.narayana.txframework.api.exception.TransactionDataUnavailableException: There is no transaction data associated with this thread > {noformat} -- 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2013