Well, this morning, I redid my Process file to assign PooledActors to tasks instead of just Actors. I was able to get the newly-created tasks to show up fine in the Group menu, but unfortunately, I'm still experiencing the same two problems I had before: the task can be assigned, but doing so sets ISCANCELLED, ISSUSPENDED, ISOPEN, ISSIGNALLING, and ISBLOCKING all to TRUE, which causes it to not be displayed in the user's task list, and both task lists are not being updated until I redeploy the application. As before, the data appears committed to the database, so I assume the transaction is working somewhat correctly, if not entirely. While those five boolean flags are being set incorrectly, the task's ACTORID column is still updated to show the current user. How does JBPM/Hibernate actually decide when to query the database? That is, when I call getTaskInstances(userId), does it use cached data somewhere? I suppose it must, because the same data shows up in my UI even after I've changed it at the database level. Can I force it to hit up the database every time that method is called, perhaps as a setting in the hibernate.cfg.xml? On the upshot, I was mistaken about how PooledActors work, so kudos for helping me clear that much up! If anyone has any further suggestions on my issues, I'd greatly appreciate it. Thanks in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157983#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...