You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2016/02/10 20:56:18 UTC
[jira] [Resolved] (JENA-1138) java.lang.OutOfMemoryError: GC
overhead limit exceeded
[ https://issues.apache.org/jira/browse/JENA-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-1138.
---------------------------------
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.1.0
Workaround: set environment variable JVM_ARGS (it can be set to a string of one space, not an empty string which the shell script considers unset via $\{JVM_ARGS:-....}).
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> ------------------------------------------------------
>
> Key: JENA-1138
> URL: https://issues.apache.org/jira/browse/JENA-1138
> Project: Apache Jena
> Issue Type: Bug
> Components: Cmd line tools
> Affects Versions: Jena 3.0.1
> Environment: Oracle JDK 1.8.0, Windows 7 64bit
> Reporter: Giovanni Mels
> Assignee: Andy Seaborne
> Labels: performance
> Fix For: Jena 3.1.0
>
> Attachments: sample-data.zip
>
>
> Since 3.0.1 we get {{java.lang.OutOfMemoryError: GC overhead limit exceeded}} exceptions when using the {{sparql}} command line tool, even on relative small datasets (~1.6 million triples).
> The issue occurs when the dataset is loaded in memory, so before the actual query execution.
> {code}
> sparql --query empty.rq --data sample-data.ttl
> {code}
> Where {{empty.rq}} contains:
> {noformat}
> SELECT * WHERE {}
> {noformat}
> This query takes ~20 seconds using Jena 2.13.0 and Jena 3.0.0, it fails with 3.0.1 after ~4 minutes with {{java.lang.OutOfMemoryError: GC overhead limit exceeded}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)