You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Michael Marth (JIRA)" <ji...@apache.org> on 2008/02/14 11:19:08 UTC

[jira] Commented: (JCR-464) Prevent out of memory errors

    [ https://issues.apache.org/jira/browse/JCR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568859#action_12568859 ] 

Michael Marth commented on JCR-464:
-----------------------------------

This problem affects me in more ways than is described above. If I create a large node with many sub nodes I cannot copy the node anymore (because I run out of memory). Also, I cannot delete the node anymore (same reason).

Both problems might be worked around on a programmatic layer, but for a user that uses a GUI this problem he can hardly get around. I suggest to increase the severity of this problem and to treat it as a bug rather than an improvement.

Some test code below. This results in an out of mem exception on my JVM. (Obviously, this depends on the heap size one uses)

			for (int i = 0; i < 20; i++) {
				
				Node n = mynode.addNode("node" + i);
				n.setProperty("property" + i, "property" + i);
				session.save();

				for (int j = 0; j < 2000; j++) {
					Node n2 = n.addNode("node" + j);
					n2.setProperty("property" + j, "property" + j);		
				}
				session.save();
			}
			session.save();
			
			
			Workspace workspace = session.getWorkspace();
			workspace.copy(mynode.getPath(), myOtherNode.getPath());
			


> Prevent out of memory errors
> ----------------------------
>
>                 Key: JCR-464
>                 URL: https://issues.apache.org/jira/browse/JCR-464
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 0.9, 1.0, 1.0.1
>            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.
-
You can reply to this email to add a comment to the issue online.