Broadleaf Commerce Discussion Forums

Ah ha; that makes sense. I was under the impression based on your initial post that you were getting this problem running on AWS rather than locally with Jrebel (which you actually further clarified in a later post). It looks like this was actually resolved by a commit made a few weeks ago: http://jira.broadleafcommerce.org/browse/BLC-694. This commit is not in a GA release yet but you can get it by running against Broadleaf 2.0.2-SNAPSHOT. I've also updated the Jira ticket to include your example stack trace to make this easier to find when using Google or just plain old Jira search.

Sorry for the frustration; not a fun problem to have to solve. While Jrebel is a fantastic tool that I feel crippled without, when it causes problems they're pretty tricky to hunt down.