[JBoss JIRA] Assigned: (JBAS-1402) Transaction Recovery
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ]
Dimitris Andreadis reassigned JBAS-1402:
----------------------------------------
Assignee: Adrian Brock
Adrian, can we close this whole task & subtasks out-of-date, or do we keep the JCA tasks as still current?
> Transaction Recovery
> --------------------
>
> Key: JBAS-1402
> URL: http://jira.jboss.com/jira/browse/JBAS-1402
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Transaction Manager
> Affects Versions: JBossAS-4.0.1 Final
> Reporter: Adrian Brock
> Assigned To: Adrian Brock
>
> Implement optional transaction recovery
> The simplest mechanism is to do this is with a local database
> using the last resource gambit where during its "prepare" it logs the XID in a table.
> If this last resource fails to commit, recovery will not find the transaction
> in the table which means it will rollback the whole transaction.
> This has limitations where a different local resource is required within the transaction
> but not this local database used as the recovery log.
> Another implementation is a local file. Though more complicated it should give superior
> performance.
> But, it does not work well with the last resource gambit, e.g. you cannot tell
> whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation
> before the result is returned from the db.
> The other work required:
> 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier.
> Currently the RARs need the transaction manager at deployment time. The
> recovery service needs to be an external service depending upon both the
> tm and the managed connection factories.
> At least this will require a GUID for the XID so we can avoid duplicates between
> unrecovered XIDs and any new XIDs created before recovery is complete.
> 2) JBossMQ needs to implement XAResource.recover()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 9 months
[JBoss JIRA] Commented: (JBAS-1292) SFSB session replication
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1292?page=comments#action_12383478 ]
Dimitris Andreadis commented on JBAS-1292:
------------------------------------------
Is this issue still current, or outdated?
> SFSB session replication
> ------------------------
>
> Key: JBAS-1292
> URL: http://jira.jboss.com/jira/browse/JBAS-1292
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Bela Ban
> Assigned To: Jason T. Greene
> Original Estimate: 10 weeks
> Remaining Estimate: 10 weeks
>
> - Issues: who instrument the user-specified object? Can it be done transparently?
> - SFSB has states defined already and user declared it as "clusterable", can we
> declare the fields object as "advisable" at runtime. Meaning, deployer will know
> this bean is clusterable and it will "delegate" it to JBossAop to declare all
> the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor
> at run time. Check with Bill on this feature.
> - Check modified field and do fine-grained replication only
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 9 months