WebSphere Commerce suite - Re: Commerce 5.6 Scheduled Commands Deadlock With User-Initiated<br> Commands

Author

Re: Commerce 5.6 Scheduled Commands Deadlock With User-Initiated<br> Commands

2005-05-04, 7:50 am

I actually did something quite similar to that. The issue is that I need to empty stale carts every 15 minutes, so I can't have the scheduler wait until late at night. So, what I did was use non-transactional JDBC in a session bean to manipulate the LASTU
PDATE of an order as well as a flag I created called MARKEDFORDELETE. Essentially, if the scheduler starts and sees that according to the order's LASTUPDATE the cart doesn't need to be emptied, it will skip it; otherwise, it will set the MARKEDFORDELETE f
lag and reap the order. On the other side, if a user performs a cart function, it checks for MARKEDFORDELETE before continuing and only updates LASTUPDATE if the command is allowed to run. Working so far...