How should I handle persistence in a Java MUD? OptimisticLockException handling
Posted
by Chase
on Stack Overflow
See other posts from Stack Overflow
or by Chase
Published on 2010-03-22T01:58:58Z
Indexed on
2010/03/22
2:01 UTC
Read the original article
Hit count: 545
I'm re-implementing a old BBS MUD game in Java with permission from the original developers. Currently I'm using Java EE 6 with EJB Session facades for the game logic and JPA for the persistence. A big reason I picked session beans is JTA.
I'm more experienced with web apps in which if you get an OptimisticLockException you just catch it and tell the user their data is stale and they need to re-apply/re-submit. Responding with "try again" all the time in a multi-user game would make for a horrible experience. Given that I'd expect several people to be targeting a single monster during a fight I think the chance of an OptimisticLockException would be high.
My view code, the part presenting a telnet CLI, is the EJB client. Should I be catching the PersistenceExceptions and TransactionRolledbackLocalExceptions and just retrying? How do you decide when to stop?
Should I switch to pessimistic locking?
Is persisting after every user command overkill? Should I be loading the entire world in RAM and dumping the state every couple of minutes?
Do I make my session facade a EJB 3.1 singleton which would function as a choke point and therefore eliminating the need to do any type of JPA locking? EJB 3.1 singletons function as a multiple reader/single writer design (you annotate the methods as readers and writers).
Basically, what is the best design and java persistence API for highly concurrent data changes in an application where it is not acceptable to present resubmit/retry prompts to the user?
© Stack Overflow or respective owner