Just a thought from someone who knows nothing more than the contents of this
thread about the issue.
Would it make sense to only cache classes within a jar? i.e. empty the cache
when moving on to scan the next jar?
Possibly one might get enough performance benefit from intra-jar class
Peter peterdni...@yahoo.com wrote:
Thanks for the response Mark - it is consistent with both observations
that i noted in the original email (heap post startup was near 0, and
disabling scanning resolves). I looked in the changelog in 26/27 and
did not see anything in there that fits this? If
2012/4/13 ma...@apache.org:
The specification requires that every class and its hierarchy is scanned for
annotations when the web app start. It was the Spring folks complaining about
the slow start time when we didn't cache anything during the scan process.
As I have said before:
- If
Thanks for the response Mark - it is consistent with both observations that i
noted in the original email (heap post startup was near 0, and disabling
scanning resolves). I looked in the changelog in 26/27 and did not see anything
in there that fits this? If your hypothesis is correct , I
On 11/04/2012 03:47, Peter wrote:
hey Christopher,
the app I used that uncovered the issue is one I use exclusively to validate
tomcat releases;) it is a hello world style app using spring/servlet3.0. it
has simple spring aop point cutting via jamon , simple spring jms (active mq)
simple
Pid p...@pidster.com wrote:
On 11/04/2012 03:47, Peter wrote:
hey Christopher,
the app I used that uncovered the issue is one I use exclusively to
validate tomcat releases;) it is a hello world style app using
spring/servlet3.0. it has simple spring aop point cutting via jamon ,
simple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 4/10/12 12:45 PM, peter nightingale wrote:
I recently updated from 7.0.25. I was able to start with -Xmx32m.
After getting 7.0.27 - I ended up needing to go all the way to
-Xmx512m. Note that the OOM only occured on startup. After
hey Christopher,
the app I used that uncovered the issue is one I use exclusively to validate
tomcat releases;) it is a hello world style app using spring/servlet3.0. it
has simple spring aop point cutting via jamon , simple spring jms (active mq)
simple spring jaxrs, simple spring jaxws,
