Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction Propagation #451

Closed
pveentjer opened this issue Mar 24, 2013 · 7 comments
Closed

Transaction Propagation #451

pveentjer opened this issue Mar 24, 2013 · 7 comments
Milestone

Comments

@pveentjer
Copy link
Contributor

Support for transaction propagation level like:
requires, requires new, etc etc.

Currently there is no support for transaction propagation which makes nesting of transactions problematic.

@enesakar enesakar added this to the 3.2+ milestone Mar 18, 2014
@bwzhang2011
Copy link

@pveentjer how does this going on ? would hazelcast support transaction propagation ?

@mmedenjak mmedenjak changed the title Transaction Propagation [transaction] Transaction Propagation Aug 3, 2017
@burakcelebi burakcelebi added Priority: Low Source: Internal PR or issue was opened by an employee labels Dec 28, 2017
@burakcelebi
Copy link
Member

Closed as internal request

@sbespalov
Copy link
Contributor

sbespalov commented Jul 24, 2018

@burakcelebi why is it closed?
In general the question is why Hazelcast don't support "nested" transactions?

The thing is that we really need PROPAGATION_REQUIRES_NEW in our Spring managed transactions, but HazelcastTransactionManager doesn't allow to use this propagation because

This transaction manager doesn't supports nested transactions, since Hazelcast doesn't support them either.

If I understand correctly "nesteed" means multiply transactions within same thread, why it's not possible?

Maybe you can give some direction for us so we can contribute PROPAGATION_REQUIRES_NEW support for HazelcastTransactionManager?

@manojgithup
Copy link

manojgithup commented Aug 2, 2018

Still i am getting this issue in hazelcast 3.9

java.lang.IllegalStateException: Transaction cannot span multiple threads!
        at com.hazelcast.client.proxy.txn.TransactionProxy.checkThread(TransactionProxy.java:134)
        at com.hazelcast.client.proxy.txn.TransactionProxy.begin(TransactionProxy.java:76)
        at com.hazelcast.client.proxy.txn.TransactionContextProxy.beginTransaction(TransactionContextProxy.java:78)
        at com.reno.imdg.servicesimpl.HZMapServiceImpl.writeOrUpdateProcessMapSpaceEntity(HZMapServiceImpl.java:278)

@mdogan
Copy link
Contributor

mdogan commented Aug 2, 2018

@sbespalov: Afaik this was closed since it was created by an Hazelcast employee and @burakcelebi created an internal issue to track that.

Hazelcast doesn't support nested transactions or configurable propagation levels yet.

@steve-todorov
Copy link

steve-todorov commented Aug 3, 2018

@mdogan do you know if there are any plans to have this implemented any time soon?

@mmedenjak
Copy link
Contributor

Hi @steve-todorov !
We have no plans to implement it as of yet. If there is much community interest, we shall consider it.

@mmedenjak mmedenjak changed the title [transaction] Transaction Propagation Transaction Propagation Aug 4, 2018
devOpsHazelcast pushed a commit that referenced this issue Jan 18, 2024
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
GitOrigin-RevId: 106b1d7ac8f77afb39285433652f6d9d8f25d5e1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants