lookups for non-existent objects from the l1, should affect the l1 instead of
the l2
------------------------------------------------------------------------------------
Key: CDV-434
URL: https://jira.terracotta.org/jira//browse/CDV-434
Project: Community Development
Issue Type: New Feature
Components: DSO:L1
Affects Versions: 2.4.3
Reporter: Fiona O'Shea
Assignee: Issue Review Board
Fix For: 2.4.4
Currently we dont differentiate a lookup from the client or a server in the
ObjectManager. When we receive a lookup for a non-existent object in the
server, we consider it as a bug in the system (which it is) and throw an
AssertionError which inturn crashes the server.
Instead we should propagate that error to the client that requested it. That
way only the misbehaving client will crash and the assertion will be closer to
the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
