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
Some client TransactionalMap
operations deserializes on server side
#11885
Labels
Milestone
Comments
Update: Transactional read operations also fail for objects that are written before transaction begins. Reproducer (
|
sertugkaya
changed the title
Some client Dec 5, 2017
TransactionalMap#values()
deserializes each value before returning them to the callerTransactionalMap
operations deserializes on server side
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 11, 2017
Two issues found was txnMap.values and txnMap.get on an entry put before transaction started. Added tests for all transactional map methods. fixes hazelcast#11885
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 11, 2017
Two issues found was txnMap.values and txnMap.get on an entry put before transaction started. Added tests for all transactional map methods. fixes hazelcast#11885
This was referenced Dec 11, 2017
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 12, 2017
Two issues found was txnMap.values and txnMap.get on an entry put before transaction started. Added tests for all transactional map methods. fixes hazelcast#11885
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 12, 2017
Two issues found was txnMap.values and txnMap.get on an entry put before transaction started. Added tests for all transactional map methods. fixes hazelcast#11885
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 12, 2017
Two issues found was txnMap.values and txnMap.get on an entry put before transaction started. Added tests for all transactional map methods. fixes hazelcast#11885
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 12, 2017
Two issues found was txnMap.values and txnMap.get on an entry put before transaction started. Added tests for all transactional map methods. fixes hazelcast#11885
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
While
IMap#values()
does not do so. This causes serialization exceptions on a client-member setup when members doesn't have the serialization info (ex: in case of using Portables).The text was updated successfully, but these errors were encountered: