Hi,
we run a simple performance test on our sling prototype and face
severe problems: About 50% of the requests failed with a status
message 500.
The exceptions differ a lot but it seems that the "sling include"
somehow fails when accessed concurrently.
Our tests were run with JMeter (and failed). To make it easier to
reproduce the problem we wrote a small bashscript using curl and run
it against the slingbuck example:
#!/bin/bash
for i in {1..10}
do
curl http://localhost:8080/content/slingbucks/public/orders.html
> out$i.log &
done
It simply calls the same URL 10 times in parallel. When grepping
through the outX.log files we found a lot of exceptions/partial page
renderings, wrongly assembled pages etc.
A short excerpt:
- NPE exception and TypeError: Cannot read property "jcr:title" from
undefined error.
- javax.jcr.PathNotFoundException: test:name
- TypeError: Cannot call method "XXX" of undefined
- Wrapped javax.jcr.InvalidItemStateException:
0a1cf798-1ada-48cc-a65b-f9ba17904467: the item does not exist anymore
- Wrapped javax.jcr.RepositoryException: this session has been closed
- 404 No Servlet to handle request
- Resource resolver is already closed
I am really concerned. I can't imagine that sling has such a huge
problem but I can't explain the exceptions we see either.
Any ideas?
Markus
