Added try/catch block for annoying/meaningless exception thrown by grail...

Currently we get a stacktrace thrown at us in the catalina logs whenever we run up a portal:
 "Unable to use direct char[] access of java.lang.String
 java.lang.NoSuchFieldException: count "

 This is a known grails issue, that doesn't affect any functionality, see here:

http://stackoverflow.com/questions/14510805/grails-1-3-7-jav…

 I''ve wacked a try/empy catch around the code which causes this so our logs are a bit cleaner (with a comment explaining why we resorted to this bad practice)