subject:"ERROR Impossibly large object"

Re: ERROR Impossibly large object

2019-07-04 Thread Mikael Pesonen




Ok good to know.

On 04/07/2019 14:12, Andy Seaborne wrote:

>>> upgrade from Jena 3.5 to 3.12

There have been problems in the past - long fixed.
The database gets silently broken when running the old version and the 
fault remains in the database. Upgrade does not fix it.


    Andy

On 04/07/2019 11:35, Mikael Pesonen wrote:


Thanks. What does the first one mean? We are using Fuseki 
:3030/ds endpoint for POSTing data and queries.


On 04/07/2019 13:26, Rob Vesse wrote:

There are several possible culprits:

- Past non-transactional use of the database
- Multiple JVMs using the database at the same time
- Actual disk corruption (i.e. failing disk, bad sectors etc)

Rob

On 04/07/2019, 11:04, "Mikael Pesonen"  
wrote:


 Ok. Is it possible to guess what could cause this?
 On 04/07/2019 12:18, Rob Vesse wrote:
 > Impossibly Large Object means the database has been corrupted 
(more specifically the Node Table).  This is non-recoverable 
although it may not affect the entire database i.e. any query that 
tries to access the affected portion of the node table will fail but 
other queries may continue to succeed.

 >
 > 
https://jena.apache.org/documentation/tdb/faqs.html#impossibly-large-object 


 >
 > To recover you would need to reload the database from a known 
good backup/dump.

 >
 > Rob
 >
 > On 04/07/2019, 10:06, "Mikael Pesonen" 
 wrote:

 >
 >
 >  Any idea how to fix this? upgrade from Jena 3.5 to 3.12 
didn't help.

 >
 >  On 02/07/2019 15:01, Mikael Pesonen wrote:
 >  >
 >  > We have had the service running for few months without 
issues but now
 >  > got this. So there is exception and also weird #011 
happening in log...

 >  > This same error happens now every time with this query.
 >  >
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 
07:59:37]

 >  > Fuseki INFO  [3457647] POST http://localhost:3030/ds
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 
07:59:37]
 >  > Fuseki INFO  [3457647] POST /ds :: '' :: 
[application/sparql-query] ?
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 
07:59:37]

 >  > Fuseki INFO  [3457647] Query = PREFIX
 >  > xsd:#011#011  PREFIX
 >  > dc:#011#011  PREFIX
 >  > dcterms:#011  PREFIX
 >  > dctype:#011  PREFIX
 >  > dcat:#011  PREFIX
 >  > skos:#011  PREFIX
 >  > skosxl:#011  PREFIX
 >  > isothes:#011 PREFIX
 >  > rdfs:#011  PREFIX
 >  > 
rdf:#011#011 PREFIX
 >  > 
lsrm:#011 PREFIX
 >  > ls:#011#011 
PREFIX

 >  > lsr:#011#011  PREFIX
 >  > lsext:#011  PREFIX
 >  > foaf:#011  PREFIX
 >  > 
nfo:#011#011

 >  > PREFIX
 >  > 
nmo:#011#011

 >  > PREFIX
 >  > 
nie:#011#011

 >  > PREFIX
 >  > 
nco:#011#011

 >  > PREFIX org:#011#011  PREFIX
 >  > 
cp:#011#011 


 >  > PREFIX mime:#011  PREFIX
 >  > 
cdm:#011#011 PREFIX
 >  > 
cmr:#011#011 PREFIX

 >  > owl:#011#011  PREFIX
 >  > frbr:#011  PREFIX jupo:
 >  > #011 PREFIX jupo-meta:
 >  >  PREFIX
 >  > v:#011#011  PREFIX
 >  > vcard:#011  PREFIX
 >  > lvont:#011  PREFIX
 >  > lexvo:#011 PREFIX
 >  > dcterms:#011  PREFIX
 >  > dctype:#011  PREFIX
 >  > foaf:#011    SELECT * 
WHERE { #011GRAPH
 >  >   #011{ 
#011#011VALUES ?s {

 >  >

Re: ERROR Impossibly large object

2019-07-04 Thread Andy Seaborne


>>> upgrade from Jena 3.5 to 3.12

There have been problems in the past - long fixed.
The database gets silently broken when running the old version and the 
fault remains in the database. Upgrade does not fix it.


Andy

On 04/07/2019 11:35, Mikael Pesonen wrote:


Thanks. What does the first one mean? We are using Fuseki 
:3030/ds endpoint for POSTing data and queries.


On 04/07/2019 13:26, Rob Vesse wrote:

There are several possible culprits:

- Past non-transactional use of the database
- Multiple JVMs using the database at the same time
- Actual disk corruption (i.e. failing disk, bad sectors etc)

Rob

On 04/07/2019, 11:04, "Mikael Pesonen"  
wrote:


 Ok. Is it possible to guess what could cause this?
 On 04/07/2019 12:18, Rob Vesse wrote:
 > Impossibly Large Object means the database has been corrupted 
(more specifically the Node Table).  This is non-recoverable although 
it may not affect the entire database i.e. any query that tries to 
access the affected portion of the node table will fail but other 
queries may continue to succeed.

 >
 > 
https://jena.apache.org/documentation/tdb/faqs.html#impossibly-large-object 


 >
 > To recover you would need to reload the database from a known 
good backup/dump.

 >
 > Rob
 >
 > On 04/07/2019, 10:06, "Mikael Pesonen" 
 wrote:

 >
 >
 >  Any idea how to fix this? upgrade from Jena 3.5 to 3.12 
didn't help.

 >
 >  On 02/07/2019 15:01, Mikael Pesonen wrote:
 >  >
 >  > We have had the service running for few months without 
issues but now
 >  > got this. So there is exception and also weird #011 
happening in log...

 >  > This same error happens now every time with this query.
 >  >
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 
07:59:37]

 >  > Fuseki INFO  [3457647] POST http://localhost:3030/ds
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 
07:59:37]
 >  > Fuseki INFO  [3457647] POST /ds :: '' :: 
[application/sparql-query] ?
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 
07:59:37]

 >  > Fuseki INFO  [3457647] Query =   PREFIX
 >  > xsd:#011#011  PREFIX
 >  > dc:#011#011  PREFIX
 >  > dcterms:#011  PREFIX
 >  > dctype:#011  PREFIX
 >  > dcat:#011  PREFIX
 >  > skos:#011  PREFIX
 >  > skosxl:#011  PREFIX
 >  > isothes:#011  PREFIX
 >  > rdfs:#011  PREFIX
 >  > 
rdf:#011#011 PREFIX
 >  > 
lsrm:#011 PREFIX

 >  > ls:#011#011 PREFIX
 >  > lsr:#011#011  PREFIX
 >  > lsext:#011  PREFIX
 >  > foaf:#011  PREFIX
 >  > 
nfo:#011#011

 >  > PREFIX
 >  > 
nmo:#011#011

 >  > PREFIX
 >  > 
nie:#011#011

 >  > PREFIX
 >  > 
nco:#011#011

 >  > PREFIX org:#011#011  PREFIX
 >  > 
cp:#011#011 


 >  > PREFIX mime:#011  PREFIX
 >  > 
cdm:#011#011 PREFIX
 >  > 
cmr:#011#011 PREFIX

 >  > owl:#011#011  PREFIX
 >  > frbr:#011  PREFIX jupo:
 >  > #011  PREFIX jupo-meta:
 >  >   PREFIX
 >  > v:#011#011  PREFIX
 >  > vcard:#011  PREFIX
 >  > lvont:#011  PREFIX
 >  > lexvo:#011    PREFIX
 >  > dcterms:#011  PREFIX
 >  > dctype:#011  PREFIX
 >  > foaf:#011    SELECT * WHERE  
{ #011GRAPH
 >  >   #011{ 
#011#011VALUES ?s {

 >  >   > Jul  2 07:59:37 insight-kaupk

Re: ERROR Impossibly large object

2019-07-04 Thread Mikael Pesonen




Thanks. What does the first one mean? We are using Fuseki 
:3030/ds endpoint for POSTing data and queries.


On 04/07/2019 13:26, Rob Vesse wrote:

There are several possible culprits:

- Past non-transactional use of the database
- Multiple JVMs using the database at the same time
- Actual disk corruption (i.e. failing disk, bad sectors etc)

Rob

On 04/07/2019, 11:04, "Mikael Pesonen"  wrote:

 
 Ok. Is it possible to guess what could cause this?
 
 On 04/07/2019 12:18, Rob Vesse wrote:

 > Impossibly Large Object means the database has been corrupted (more 
specifically the Node Table).  This is non-recoverable although it may not affect 
the entire database i.e. any query that tries to access the affected portion of 
the node table will fail but other queries may continue to succeed.
 >
 > 
https://jena.apache.org/documentation/tdb/faqs.html#impossibly-large-object
 >
 > To recover you would need to reload the database from a known good 
backup/dump.
 >
 > Rob
 >
 > On 04/07/2019, 10:06, "Mikael Pesonen"  
wrote:
 >
 >
 >  Any idea how to fix this? upgrade from Jena 3.5 to 3.12 didn't help.
 >
 >  On 02/07/2019 15:01, Mikael Pesonen wrote:
 >  >
 >  > We have had the service running for few months without issues but 
now
 >  > got this. So there is exception and also weird #011 happening in 
log...
 >  > This same error happens now every time with this query.
 >  >
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 >  > Fuseki INFO  [3457647] POST http://localhost:3030/ds
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 >  > Fuseki INFO  [3457647] POST /ds :: '' :: 
[application/sparql-query] ?
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 >  > Fuseki INFO  [3457647] Query =   PREFIX
 >  > xsd:#011#011  PREFIX
 >  > dc:#011#011  PREFIX
 >  > dcterms:#011  PREFIX
 >  > dctype:#011  PREFIX
 >  > dcat:#011  PREFIX
 >  > skos:#011  PREFIX
 >  > skosxl:#011  PREFIX
 >  > isothes:#011  PREFIX
 >  > rdfs:#011  PREFIX
 >  > rdf:#011#011 PREFIX
 >  > lsrm:#011 PREFIX
 >  > ls:#011#011 PREFIX
 >  > lsr:#011#011  PREFIX
 >  > lsext:#011  PREFIX
 >  > foaf:#011  PREFIX
 >  > 
nfo:#011#011
 >  > PREFIX
 >  > 
nmo:#011#011
 >  > PREFIX
 >  > 
nie:#011#011
 >  > PREFIX
 >  > 
nco:#011#011
 >  > PREFIX org:#011#011  PREFIX
 >  > 
cp:#011#011
 >  > PREFIX mime:#011  PREFIX
 >  > cdm:#011#011 PREFIX
 >  > cmr:#011#011 
PREFIX
 >  > owl:#011#011  PREFIX
 >  > frbr:#011  PREFIX jupo:
 >  > #011  PREFIX jupo-meta:
 >  >   PREFIX
 >  > v:#011#011  PREFIX
 >  > vcard:#011  PREFIX
 >  > lvont:#011  PREFIX
 >  > lexvo:#011PREFIX
 >  > dcterms:#011  PREFIX
 >  > dctype:#011  PREFIX
 >  > foaf:#011SELECT * WHERE  { 
#011GRAPH
 >  >   #011{ #011#011VALUES 
?s {
 >  >   > Jul  2 07:59:37 insight-kaupk java[1043]:
 >  > ngsoft.fi/2b7f1869-b956-47d2-9e9e-455bedb15ba0> }  #011#011?s a
 >  > foaf:OnlineAccount .  #011#011?s ?p ?o .  #011}  }
 >  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 >  > Fuseki INFO  [3457647] 200 OK (5 ms)

Re: ERROR Impossibly large object

2019-07-04 Thread Rob Vesse

There are several possible culprits:

- Past non-transactional use of the database
- Multiple JVMs using the database at the same time
- Actual disk corruption (i.e. failing disk, bad sectors etc)

Rob

On 04/07/2019, 11:04, "Mikael Pesonen"  wrote:


Ok. Is it possible to guess what could cause this?

On 04/07/2019 12:18, Rob Vesse wrote:
> Impossibly Large Object means the database has been corrupted (more 
specifically the Node Table).  This is non-recoverable although it may not 
affect the entire database i.e. any query that tries to access the affected 
portion of the node table will fail but other queries may continue to succeed.
>
> 
https://jena.apache.org/documentation/tdb/faqs.html#impossibly-large-object
>
> To recover you would need to reload the database from a known good 
backup/dump.
>
> Rob
>
> On 04/07/2019, 10:06, "Mikael Pesonen"  
wrote:
>
>  
>  Any idea how to fix this? upgrade from Jena 3.5 to 3.12 didn't help.
>  
>  On 02/07/2019 15:01, Mikael Pesonen wrote:
>  >
>  > We have had the service running for few months without issues but 
now
>  > got this. So there is exception and also weird #011 happening in 
log...
>  > This same error happens now every time with this query.
>  >
>  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
>  > Fuseki INFO  [3457647] POST http://localhost:3030/ds
>  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
>  > Fuseki INFO  [3457647] POST /ds :: '' :: 
[application/sparql-query] ?
>  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
>  > Fuseki INFO  [3457647] Query =   PREFIX
>  > xsd:#011#011  PREFIX
>  > dc:#011#011  PREFIX
>  > dcterms:#011  PREFIX
>  > dctype:#011  PREFIX
>  > dcat:#011  PREFIX
>  > skos:#011  PREFIX
>  > skosxl:#011  PREFIX
>  > isothes:#011  PREFIX
>  > rdfs:#011  PREFIX
>  > rdf:#011#011 PREFIX
>  > lsrm:#011 PREFIX
>  > ls:#011#011 PREFIX
>  > lsr:#011#011  PREFIX
>  > lsext:#011  PREFIX
>  > foaf:#011  PREFIX
>  > 
nfo:#011#011
>  > PREFIX
>  > 
nmo:#011#011
>  > PREFIX
>  > 
nie:#011#011
>  > PREFIX
>  > 
nco:#011#011
>  > PREFIX org:#011#011  PREFIX
>  > 
cp:#011#011
>  > PREFIX mime:#011  PREFIX
>  > cdm:#011#011 PREFIX
>  > cmr:#011#011 
PREFIX
>  > owl:#011#011  PREFIX
>  > frbr:#011  PREFIX jupo:
>  > #011  PREFIX jupo-meta:
>  >   PREFIX
>  > v:#011#011  PREFIX
>  > vcard:#011  PREFIX
>  > lvont:#011  PREFIX
>  > lexvo:#011PREFIX
>  > dcterms:#011  PREFIX
>  > dctype:#011  PREFIX
>  > foaf:#011SELECT * WHERE  { 
#011GRAPH
>  >   #011{ #011#011VALUES 
?s {
>  >   > Jul  2 07:59:37 insight-kaupk java[1043]:
>  > ngsoft.fi/2b7f1869-b956-47d2-9e9e-455bedb15ba0> }  #011#011?s a
>  > foaf:OnlineAccount .  #011#011?s ?p ?o .  #011}  }
>  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
>  > Fuseki INFO  [3457647] 200 OK (5 ms)
>  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
>  > Fuseki INFO  [3457648] POST http://localhost:3030/ds
>  > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02

Re: ERROR Impossibly large object

2019-07-04 Thread Mikael Pesonen




Ok. Is it possible to guess what could cause this?

On 04/07/2019 12:18, Rob Vesse wrote:

Impossibly Large Object means the database has been corrupted (more 
specifically the Node Table).  This is non-recoverable although it may not 
affect the entire database i.e. any query that tries to access the affected 
portion of the node table will fail but other queries may continue to succeed.

https://jena.apache.org/documentation/tdb/faqs.html#impossibly-large-object

To recover you would need to reload the database from a known good backup/dump.

Rob

On 04/07/2019, 10:06, "Mikael Pesonen"  wrote:

 
 Any idea how to fix this? upgrade from Jena 3.5 to 3.12 didn't help.
 
 On 02/07/2019 15:01, Mikael Pesonen wrote:

 >
 > We have had the service running for few months without issues but now
 > got this. So there is exception and also weird #011 happening in log...
 > This same error happens now every time with this query.
 >
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457647] POST http://localhost:3030/ds
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457647] POST /ds :: '' :: [application/sparql-query] ?
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457647] Query =   PREFIX
 > xsd:#011#011  PREFIX
 > dc:#011#011  PREFIX
 > dcterms:#011  PREFIX
 > dctype:#011  PREFIX
 > dcat:#011  PREFIX
 > skos:#011  PREFIX
 > skosxl:#011  PREFIX
 > isothes:#011  PREFIX
 > rdfs:#011  PREFIX
 > rdf:#011#011 PREFIX
 > lsrm:#011 PREFIX
 > ls:#011#011 PREFIX
 > lsr:#011#011  PREFIX
 > lsext:#011  PREFIX
 > foaf:#011  PREFIX
 > nfo:#011#011
 > PREFIX
 > nmo:#011#011
 > PREFIX
 > nie:#011#011
 > PREFIX
 > nco:#011#011
 > PREFIX org:#011#011  PREFIX
 > 
cp:#011#011
 > PREFIX mime:#011  PREFIX
 > cdm:#011#011 PREFIX
 > cmr:#011#011 PREFIX
 > owl:#011#011  PREFIX
 > frbr:#011  PREFIX jupo:
 > #011  PREFIX jupo-meta:
 >   PREFIX
 > v:#011#011  PREFIX
 > vcard:#011  PREFIX
 > lvont:#011  PREFIX
 > lexvo:#011PREFIX
 > dcterms:#011  PREFIX
 > dctype:#011  PREFIX
 > foaf:#011SELECT * WHERE  { #011GRAPH
 >   #011{ #011#011VALUES ?s {
 >  Jul  2 07:59:37 insight-kaupk java[1043]:
 > ngsoft.fi/2b7f1869-b956-47d2-9e9e-455bedb15ba0> }  #011#011?s a
 > foaf:OnlineAccount .  #011#011?s ?p ?o .  #011}  }
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457647] 200 OK (5 ms)
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457648] POST http://localhost:3030/ds
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457648] POST /ds :: '' :: [application/sparql-query] ?
 > Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
 > Fuseki INFO  [3457648] Query =   PREFIX
 > xsd:#011#011  PREFIX
 > dc:#011#011  PREFIX
 > dcterms:#011  PREFIX
 > dctype:#011  PREFIX
 > dcat:#011  PREFIX
 > skos:#011  PREFIX
 > skosxl:#011  PREFIX
 > isothes:#011  PREFIX
 >

Re: ERROR Impossibly large object

2019-07-04 Thread Rob Vesse

Impossibly Large Object means the database has been corrupted (more 
specifically the Node Table).  This is non-recoverable although it may not 
affect the entire database i.e. any query that tries to access the affected 
portion of the node table will fail but other queries may continue to succeed.

https://jena.apache.org/documentation/tdb/faqs.html#impossibly-large-object

To recover you would need to reload the database from a known good backup/dump.

Rob

On 04/07/2019, 10:06, "Mikael Pesonen"  wrote:


Any idea how to fix this? upgrade from Jena 3.5 to 3.12 didn't help.

On 02/07/2019 15:01, Mikael Pesonen wrote:
>
> We have had the service running for few months without issues but now 
> got this. So there is exception and also weird #011 happening in log...
> This same error happens now every time with this query.
>
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457647] POST http://localhost:3030/ds
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457647] POST /ds :: '' :: [application/sparql-query] ?
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457647] Query =   PREFIX 
> xsd:#011#011  PREFIX 
> dc:#011#011  PREFIX 
> dcterms:#011  PREFIX 
> dctype:#011  PREFIX 
> dcat:#011  PREFIX 
> skos:#011  PREFIX 
> skosxl:#011  PREFIX 
> isothes:#011  PREFIX 
> rdfs:#011  PREFIX 
> rdf:#011#011 PREFIX 
> lsrm:#011 PREFIX 
> ls:#011#011 PREFIX 
> lsr:#011#011  PREFIX 
> lsext:#011  PREFIX 
> foaf:#011  PREFIX 
> nfo:#011#011 
> PREFIX 
> nmo:#011#011 
> PREFIX 
> nie:#011#011 
> PREFIX 
> nco:#011#011 
> PREFIX org:#011#011  PREFIX 
> 
cp:#011#011
 
> PREFIX mime:#011  PREFIX 
> cdm:#011#011 PREFIX 
> cmr:#011#011 PREFIX 
> owl:#011#011  PREFIX 
> frbr:#011  PREFIX jupo: 
> #011  PREFIX jupo-meta: 
>   PREFIX 
> v:#011#011  PREFIX 
> vcard:#011  PREFIX 
> lvont:#011  PREFIX 
> lexvo:#011PREFIX 
> dcterms:#011  PREFIX 
> dctype:#011  PREFIX 
> foaf:#011SELECT * WHERE  { #011GRAPH 
>   #011{ #011#011VALUES ?s { 
>  Jul  2 07:59:37 insight-kaupk java[1043]: 
> ngsoft.fi/2b7f1869-b956-47d2-9e9e-455bedb15ba0> }  #011#011?s a 
> foaf:OnlineAccount .  #011#011?s ?p ?o .  #011}  }
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457647] 200 OK (5 ms)
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457648] POST http://localhost:3030/ds
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457648] POST /ds :: '' :: [application/sparql-query] ?
> Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
> Fuseki INFO  [3457648] Query =   PREFIX 
> xsd:#011#011  PREFIX 
> dc:#011#011  PREFIX 
> dcterms:#011  PREFIX 
> dctype:#011  PREFIX 
> dcat:#011  PREFIX 
> skos:#011  PREFIX 
> skosxl:#011  PREFIX 
> isothes:#011  PREFIX 
> rdfs:#011  PREFIX 
>

Re: ERROR Impossibly large object

2019-07-04 Thread Mikael Pesonen




Any idea how to fix this? upgrade from Jena 3.5 to 3.12 didn't help.

On 02/07/2019 15:01, Mikael Pesonen wrote:


We have had the service running for few months without issues but now 
got this. So there is exception and also weird #011 happening in log...

This same error happens now every time with this query.

Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] POST http://localhost:3030/ds
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] POST /ds :: '' :: [application/sparql-query] ?
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] Query =   PREFIX 
xsd:#011#011  PREFIX 
dc:#011#011  PREFIX 
dcterms:#011  PREFIX 
dctype:#011  PREFIX 
dcat:#011  PREFIX 
skos:#011  PREFIX 
skosxl:#011  PREFIX 
isothes:#011  PREFIX 
rdfs:#011  PREFIX 
rdf:#011#011 PREFIX 
lsrm:#011 PREFIX 
ls:#011#011 PREFIX 
lsr:#011#011  PREFIX 
lsext:#011  PREFIX 
foaf:#011  PREFIX 
nfo:#011#011 
PREFIX 
nmo:#011#011 
PREFIX 
nie:#011#011 
PREFIX 
nco:#011#011 
PREFIX org:#011#011  PREFIX 
cp:#011#011 
PREFIX mime:#011  PREFIX 
cdm:#011#011 PREFIX 
cmr:#011#011 PREFIX 
owl:#011#011  PREFIX 
frbr:#011  PREFIX jupo: 
#011  PREFIX jupo-meta: 
  PREFIX 
v:#011#011  PREFIX 
vcard:#011  PREFIX 
lvont:#011  PREFIX 
lexvo:#011    PREFIX 
dcterms:#011  PREFIX 
dctype:#011  PREFIX 
foaf:#011    SELECT * WHERE  { #011GRAPH 
  #011{ #011#011VALUES ?s { 
 }  #011#011?s a 
foaf:OnlineAccount .  #011#011?s ?p ?o .  #011}  }
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] 200 OK (5 ms)
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457648] POST http://localhost:3030/ds
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457648] POST /ds :: '' :: [application/sparql-query] ?
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457648] Query =   PREFIX 
xsd:#011#011  PREFIX 
dc:#011#011  PREFIX 
dcterms:#011  PREFIX 
dctype:#011  PREFIX 
dcat:#011  PREFIX 
skos:#011  PREFIX 
skosxl:#011  PREFIX 
isothes:#011  PREFIX 
rdfs:#011  PREFIX 
rdf:#011#011 PREFIX 
lsrm:#011 PREFIX 
ls:#011#011 PREFIX 
lsr:#011#011  PREFIX 
lsext:#011  PREFIX 
foaf:#011  PREFIX 
nfo:#011#011 
PREFIX 
nmo:#011#011 
PREFIX 
nie:#011#011 
PREFIX 
nco:#011#011 
PREFIX org:#011#011  PREFIX 
cp:#011#011 
PREFIX mime:#011  PREFIX 
cdm:#011#011 PREFIX 
cmr:#011#011 PREFIX

Re: ERROR Impossibly large object

2019-07-02 Thread Mikael Pesonen




Ok that explains. Don't remember seeing it on stack trace before...

On 02/07/2019 15:33, Andy Seaborne wrote:



On 02/07/2019 13:01, Mikael Pesonen wrote:

weird #011


Which is a tab - octal 011 is decimal 9.


--
Lingsoft - 30 years of Leading Language Management

www.lingsoft.fi

Speech Applications - Language Management - Translation - Reader's and Writer's 
Tools - Text Tools - E-books and M-books

Mikael Pesonen
System Engineer

e-mail: mikael.peso...@lingsoft.fi
Tel. +358 2 279 3300

Time zone: GMT+2

Helsinki Office
Eteläranta 10
FI-00130 Helsinki
FINLAND

Turku Office
Kauppiaskatu 5 A
FI-20100 Turku
FINLAND

Re: ERROR Impossibly large object

2019-07-02 Thread Andy Seaborne





On 02/07/2019 13:01, Mikael Pesonen wrote:

weird #011


Which is a tab - octal 011 is decimal 9.

ERROR Impossibly large object

2019-07-02 Thread Mikael Pesonen




We have had the service running for few months without issues but now 
got this. So there is exception and also weird #011 happening in log...

This same error happens now every time with this query.

Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] POST http://localhost:3030/ds
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] POST /ds :: '' :: [application/sparql-query] ?
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] Query =   PREFIX 
xsd:#011#011  PREFIX 
dc:#011#011  PREFIX 
dcterms:#011  PREFIX 
dctype:#011  PREFIX 
dcat:#011  PREFIX 
skos:#011  PREFIX 
skosxl:#011  PREFIX 
isothes:#011  PREFIX 
rdfs:#011  PREFIX 
rdf:#011#011 PREFIX 
lsrm:#011 PREFIX 
ls:#011#011 PREFIX 
lsr:#011#011  PREFIX 
lsext:#011  PREFIX 
foaf:#011  PREFIX 
nfo:#011#011 
PREFIX 
nmo:#011#011 
PREFIX 
nie:#011#011 
PREFIX 
nco:#011#011 
PREFIX org:#011#011  PREFIX 
cp:#011#011 
PREFIX mime:#011  PREFIX 
cdm:#011#011 PREFIX 
cmr:#011#011 PREFIX 
owl:#011#011  PREFIX 
frbr:#011  PREFIX jupo: 
#011  PREFIX jupo-meta: 
  PREFIX 
v:#011#011  PREFIX 
vcard:#011  PREFIX 
lvont:#011  PREFIX 
lexvo:#011    PREFIX 
dcterms:#011  PREFIX 
dctype:#011  PREFIX 
foaf:#011    SELECT * WHERE  { #011GRAPH 
  #011{ #011#011VALUES ?s { 
 }  #011#011?s a 
foaf:OnlineAccount .  #011#011?s ?p ?o .  #011}  }
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457647] 200 OK (5 ms)
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457648] POST http://localhost:3030/ds
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457648] POST /ds :: '' :: [application/sparql-query] ?
Jul  2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37] 
Fuseki INFO  [3457648] Query =   PREFIX 
xsd:#011#011  PREFIX 
dc:#011#011  PREFIX 
dcterms:#011  PREFIX 
dctype:#011  PREFIX 
dcat:#011  PREFIX 
skos:#011  PREFIX 
skosxl:#011  PREFIX 
isothes:#011  PREFIX 
rdfs:#011  PREFIX 
rdf:#011#011 PREFIX 
lsrm:#011 PREFIX 
ls:#011#011 PREFIX 
lsr:#011#011  PREFIX 
lsext:#011  PREFIX 
foaf:#011  PREFIX 
nfo:#011#011 
PREFIX 
nmo:#011#011 
PREFIX 
nie:#011#011 
PREFIX 
nco:#011#011 
PREFIX org:#011#011  PREFIX 
cp:#011#011 
PREFIX mime:#011  PREFIX 
cdm:#011#011 PREFIX 
cmr:#011#011 PREFIX 
owl:#011#011  PREFIX 
frbr:#011  PREFIX jupo:

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

Re: ERROR Impossibly large object

ERROR Impossibly large object

10 matches

Site Navigation

Mail list logo

Footer information