[Building Sakai] EntityEncodingException using Roster2 on large membership sites

[Adrian Fish]

As part of my investigations into Roster2's behaviour in large sites ( 5000
users ) I've uncovered a problem. Click on any of the views and you get
this exception:

INFO Could not process entity: /roster-membership (500)[null]:
EntityEncodingException: Unable to handle output request for format  json
for this path
(/roster-membership/f0c4d1a7-ce96-4bb2-b04e-0752b79891f0/get-membership.json)
for prefix (roster-membership) for entity (/roster-membership), request url
(/roster-membership/f0c4d1a7-ce96-4bb2-b04e-0752b79891f0/get-membership.json):
Failed to encode into output stream: /roster-membership
WARN Error sending http servlet error code (500) and message
(EntityEncodingException: Unable to handle output request for format  json
for this path
(/roster-membership/f0c4d1a7-ce96-4bb2-b04e-0752b79891f0/get-membership.json)
for prefix (roster-membership) for entity (/roster-membership), request url
(/roster-membership/f0c4d1a7-ce96-4bb2-b04e-0752b79891f0/get-membership.json):
Failed to encode into output stream: /roster-membership):
java.lang.IllegalStateException: Cannot call reset() after response has
been committed

If you have a site with less users, 500 say, the error becomes sporadic,
sometimes it happens, sometimes not, so it seems timing related, maybe
involving long return times from db calls. The error 'Cannot call reset()
after response has been committed' implies a mishandling of the servlet
response.

This is a show stopper for roster2 on large membership sites, so any ideas
will be very much welcome.

Cheers,
Adrian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131128/1a1868fe/attachment.html