On 03/21/12 20:38, Conrad Dean wrote:
Not sure if this is the right place for this, but I wanted to start a
discussion about how the OpenGrok webapp deals with placing search queries
and navigates through results.
It's not possible to use OpenGrok with a large (200+) number of projects.
Because query variables are all encoded onto the URL of a GET request, I'm
hitting the limit of the query string.
I've made some changes to OpenGrok so that search queries, pagination, and
selecting different sort methods go through POST requests on the search
form(#sbox)-- but I'm not sure if this is the ideal solution.
Could we look into how to resolve this, or is my edgecase a little too
specific?
That's very interesting. I've been observing the same problem (combined
with Tomcat/Java running out of heap space) just yesterday on our
internal server which has cca 250 projects so this is definitely an
issue. Some all-project queries were returning HTTP error code 400
straight, some ended up with success (200) but with the
'java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
Java heap space' error displayed in OpenGrok page (instead of results).
The other thing is that the Tomcat process was burning the CPUs for a
long time (might be minutes, did not do proper measurements); it would
be handy to have an upper limit for how long a query can take.
v.
_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
