The problem is that the exception you have posted definitely wraps the causing exception. I just don’t know why it isn’t logged in your case. I think it has something to do with Mojarra logging exceptions not completely. So your only chance is to set a break point at this point to see what is happening.
Perhaps the scope of the bean is a problem. Could you set the scope to REQUEST for testing?
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.