[
http://issues.ops4j.org/jira/browse/PAXURL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11236
]
Evan Cowden commented on PAXURL-17:
-----------------------------------
Alin: yes, we can get around the OutOfMemoryError by increasing heap size, but
required VM arguments do nothing for usability. In this case, I believe we can
get around the requirement by simply rewriting one ten-line utility method to
avoid recursion.
Does anyone have existing contact with Peter Kriens or experience with
contributing to his bndlib library? If not, I would be happy to contact him on
my own - I just don't want to step on anyone's toes.
> OutOfMemoryError When Pax WAR Wraps a WAR with Large Libraries
> --------------------------------------------------------------
>
> Key: PAXURL-17
> URL: http://issues.ops4j.org/jira/browse/PAXURL-17
> Project: Pax URL
> Issue Type: Bug
> Components: war
> Affects Versions: 0.3.1
> Environment: Equinox running with Java 6 in Windows
> Reporter: Evan Cowden
> Assignee: Alin Dreghiciu
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When Pax WAR wraps a WAR file with a large library in the lib directory (10MB
> seems to do it), it will throw an OutOfMemoryError. This is caused by
> aQute.lib.osgi.EmbeddedResource.collect(), which uses recursion to read the
> library in 10K chunks, eventually blowing up the heap. I have confirmed that
> the problem can be fixed by reading the input stream in a loop rather than
> using recursion.
> Problem is: this is not an OPS4J library, but rather belongs to Peter Krien's
> bndlib. What is the process for integrating a fix?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
