[ http://issues.apache.org/jira/browse/JCR-464?page=comments#action_12416581 ]
Jukka Zitting commented on JCR-464: ----------------------------------- I agree that this should be solved somehow, I've seen a real-life case where this caused the repository to run out of memory while importing a large (but not huge) XML document. A short term solution would be to make the maximum size of the transient space configurable. A longer term solution would be to make the transient space backed by temporary storage (e.g. by using a transient persistence manager) when it grows too large. In general I don't think it will be feasible or even preferable to prevent denial of service attacks on the JCR API level, so I wouldn't count that as a too high priority, but I think that there are legitimate use cases for working with transient spaces that might exceed the amount of available memory especially in a shared environment like a web server. > Prevent out of memory errors > ---------------------------- > > Key: JCR-464 > URL: http://issues.apache.org/jira/browse/JCR-464 > Project: Jackrabbit > Type: Improvement > Components: core > Reporter: Edgar Poce > Priority: Minor > > Even an anonymous session can kill the jvm, any session can perform write > actions untill it kills the process by causing an outofmemoryexception. > I think it would be good to add a configuration parameter to specify the max > size of the transient ISMs and the max number of sessions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
