August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1712: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> made a comment on [bug 968125|https://bugzilla.redhat.com/show_bug.cgi?id=968125] JBossTS/Narayana updated to 4.17.7 in 6.1.1 ER4 > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4, 5.0.0.M2 > Reporter: Jonathan Halliday > Assignee: Mark Little > Fix For: 4.17.6, 5.0.0.M3 > > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1712: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 968125|https://bugzilla.redhat.com/show_bug.cgi?id=968125] from POST to ON_QA > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4, 5.0.0.M2 > Reporter: Jonathan Halliday > Assignee: Mark Little > Fix For: 4.17.6, 5.0.0.M3 > > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1303) WS-AT client can return from commit before all participants have committed

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1303?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1303: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > WS-AT client can return from commit before all participants have committed > -------------------------------------------------------------------------- > > Key: JBTM-1303 > URL: https://issues.jboss.org/browse/JBTM-1303 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Priority: Minor > Fix For: 6.0.0.Final > > > Normally, when a WS-AT client calls commit, the coordinator will wait until all participants are committed before returning to the client. This ensures that the Client doesn't continue processing until all changes have been made permanent and visible. > If the participant takes longer than 30s to return the 'committed' message, the participant logs the fact and then returns to the client. The recovery mechanism will then handle the sending of the commit message to the participant. As WS-AT doesn't support heuristics, the participant is guaranteed to commit eventually, but after at least one recovery scan. This means that the client may think that the work done, in the transaction, is now visible when in actual fact it is not quite yet. > h3. Potential solutions > h4. Return CommittingException > As a JBoss only solution (it would break the standard), we could throw a CommittingException when the coordinator returns control to the client after delegating to the recovery manager to commit the outstanding participant(s). The client then know that the work will commit, but it's not completed yet. Handling of this exception could be to either ignore it, or poll the resource until the change is visible. This could work for both synchronous and asynchronous clients. > h4. Delay the return until participants really have committed. > This is unlikely to work for the (JBoss only) synchronous client as the connection is unlikely to stay open long enough. However, it could work for the asynchronous scenario, but would require the client to increase the timeout to include the amount of time it takes for the coordinator to give up waiting for committed and delegate to the recovery manager, plus enough time for the recovery scan to occur and receive the committed message. Also, the client endpoint information would need to be stored in the recovery log, so that the recovery manager can attempt notification (which would also need implementing). > h4. Document the issue for now > ... and implement a solution if/when we get a user with this problem. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1174) Add debug logging to TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1174?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1174. --------------------------------- Assignee: Paul Robinson Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Won't Fix Logging is adequate at the moment. We can increase as and when required. > Add debug logging to TXFramework > -------------------------------- > > Key: JBTM-1174 > URL: https://issues.jboss.org/browse/JBTM-1174 > 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.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-997) TXFramework fails to compile with certain versions of the Oracle JDK

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-997?page=com.atlassian.jira.plugin.s... ] Paul Robinson resolved JBTM-997. -------------------------------- Assignee: Paul Robinson Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Out of Date > TXFramework fails to compile with certain versions of the Oracle JDK > -------------------------------------------------------------------- > > Key: JBTM-997 > URL: https://issues.jboss.org/browse/JBTM-997 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > To reproduce: > {code} > cd /tmp > svn co http://anonsvn.jboss.org/repos/labs/labs/jbosstm/trunk/txframework/framework ./framework > cd framework > mvn clean install > {code} > Observe: > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project txframework: Compilation failure: Compilation failure: > [ERROR] /Users/paul/Dropbox/Redhat/backup/dev/JBOSSTS_TRUNK/narayana/txframework/framework/src/main/java/org/jboss/narayana/txframework/api/annotation/transaction/WSBA.java:[21,65] incompatible types > [ERROR] found : org.jboss.narayana.txframework.api.configuration.transaction.CompletionType > [ERROR] required: org.jboss.narayana.txframework.api.configuration.transaction.CompletionType > [ERROR] /Users/paul/Dropbox/Redhat/backup/dev/JBOSSTS_TRUNK/narayana/txframework/framework/src/main/java/org/jboss/narayana/txframework/api/annotation/service/ServiceRequest.java:[32,56] incompatible types > [ERROR] found : org.jboss.narayana.txframework.api.configuration.service.RequestType > [ERROR] required: org.jboss.narayana.txframework.api.configuration.service.RequestType > [ERROR] -> [Help 1] > {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1191) TXFramework enlists with invalid url if @Path is used on a service request method

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1191?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1191. --------------------------------- Assignee: Paul Robinson Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Out of Date Applies to AT support in REST-AT which is being dropped in favour of JTA bridging. > TXFramework enlists with invalid url if @Path is used on a service request method > --------------------------------------------------------------------------------- > > Key: JBTM-1191 > URL: https://issues.jboss.org/browse/JBTM-1191 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > For this interface: > {code} > @Path("/taxi") > public interface TaxiServiceAT { > @POST > @Produces("text/plain") > @Path("makeBooking") > public Response makeBooking(); > } > {code} > the following enlist url is created: > http://localhost:8080/test/taxi/makeBooking0_ffffc0a80068_2a160422_4fe205... > The addition of the '/makeBooking' fragment breaks the url pattern expected by the participant endpoint (@Path("{txid}/{pId}/terminate")) and messages from the coordinator are ignored. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1052) Support Web services with a webservices.xml present in TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1052?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1052: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Support Web services with a webservices.xml present in TXFramework > ------------------------------------------------------------------ > > Key: JBTM-1052 > URL: https://issues.jboss.org/browse/JBTM-1052 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TXFramework > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Priority: Minor > Fix For: 6.0.0.Final > > > See: https://community.jboss.org/message/714478#714478 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1398. --------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.Final) Resolution: Done > Review subsystem usage across Narayana > -------------------------------------- > > 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: Tom Jenkinson > Fix For: 5.0.0.M4 > > Original Estimate: 2 days > Time Spent: 1 day, 7 hours > Remaining Estimate: 2 days, 6 hours > > h2. Components and their subsystem requirements: > h5. Transactions > * To Investigate > > h5. XTS > * Bootstrap coordinator > * Setup WS endpoints for coordinator > * Setup WS endpoints for the participants > * Respond to configuration from standalone-xts.xml > h5. REST-TX > * Boostrap the coordinator > * Setup a REST endpoint for the coordinator > * Setup a REST endpoint for the participants > h5. Blacktie > * Register MDB > * Register MBean > h5. STM > * To Investigate > h5. TXF > * Modify the WS handler chain on application deployment > * Registers a CDI extension > h2. Notable Dependencies > h5. TXF > * Weld -> EJB3 -> Transactions (Could check that each link is valid. Check if subsys or regular dep) > * JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem. > h2. Subsystem Breakdown > Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems. > h5. Transactions > * All current stuff > * STM > * TXF (Unlikely to work due to dependency on Weld for loading a portable extension) > h5. XTS > * All Current Stuff > h5. RTS (new) > h5. Blacktie (new) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-987) Document Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-987: ------------------------------- Labels: Documentation, TXFramework (was: TXFramework) > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Priority: Optional > Labels: Documentation,, TXFramework > Fix For: 5.0.0.Final > > > Should cover all existing features and provide a skeleton for the final document. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-987) Document Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-987: ------------------------------- Summary: Document Compensations API (was: Create initial documentation for TXFramework) > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Priority: Optional > Labels: TXFramework > Fix For: 5.0.0.Final > > > Should cover all existing features and provide a skeleton for the final document. -- 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

12 years, 7 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 August 2013