In load balanced or clustered J2EE web applications, are there any issues with embedding jBPM in each application and sharing the same database? The idea is ensure that there is a single "task list" for a user while a single business process may span multiple J2EE applications. Would there by any reason to establish a standalone jBPM server?
No you can embed jBPM in your applications and use one database. But you have to be careful: either use pessimistic locking (the easiest solution and the one we recommend) or use optimistic locking (requires database changes to include the version field).