This content has been marked as final. Show 2 replies
I'm having the same problem on version 3.0.6.
I start thinking it's a feature...
Can anybody explain me the reason for this behaviour?
Same thing here. Version 3.0.4. Can't find a solution. Going to use JNDI.