[ 
https://issues.apache.org/jira/browse/JENA-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238148#comment-17238148
 ] 

Andy Seaborne edited comment on JENA-1987 at 11/24/20, 2:03 PM:
----------------------------------------------------------------

Occasional test failure, only seen on ASF Jenkins (i.e. can be heavily loaded). 
Looks like the test suite exits before the task is run. 

Personally, I don't like deploymentt code doing any kind of adaption to make 
tests work (e.g. semaphore signalling) because making the code more complicated 
can have other effects that don't easily get noticed.

{noformat}
[INFO] Running org.apache.jena.fuseki.TS_FusekiWebapp
08:24:38 ERROR Server     :: Exception in task 14 execution
org.apache.jena.dboe.transaction.txn.TransactionException: 
TransactionCoordinator has been shutdown
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.checkNotShutdown(TransactionCoordinator.java:345)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.checkActive(TransactionCoordinator.java:340)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.begin(TransactionCoordinator.java:515)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.begin(TransactionCoordinator.java:504)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionalBase.begin(TransactionalBase.java:110)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.storage.system.DatasetGraphStorage.begin(DatasetGraphStorage.java:59)
 ~[jena-dboe-storage-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.system.Txn.exec(Txn.java:76) 
~[jena-arq-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.system.Txn.executeRead(Txn.java:115) 
~[jena-arq-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.sys.CopyDSG.copy(CopyDSG.java:35) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.sys.DatabaseOps.compact(DatabaseOps.java:236) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.sys.DatabaseOps.compact(DatabaseOps.java:198) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.DatabaseMgr.compact(DatabaseMgr.java:62) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.fuseki.mgt.ActionCompact$CompactTask.run(ActionCompact.java:73) 
~[classes/:?]
        at 
org.apache.jena.fuseki.async.AsyncPool.lambda$submit$0(AsyncPool.java:66) 
~[jena-fuseki-core-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.fuseki.async.AsyncTask.call(AsyncTask.java:100) 
[jena-fuseki-core-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[?:1.8.0_252]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_252]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_252]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
[ERROR] Tests run: 189, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
79.542 s <<< FAILURE! - in org.apache.jena.fuseki.TS_FusekiWebapp
[ERROR] compact_01(org.apache.jena.fuseki.TestAdmin)  Time elapsed: 9.375 s  
<<< ERROR!
java.lang.NullPointerException
        at org.apache.jena.fuseki.TestAdmin.compact_01(TestAdmin.java:346)
{noformat}



was (Author: andy.seaborne):
Occasional test failure, only seen on ASF Jenkins (i.e. can be heavily loaded). 
Looks like the test suite exits before the task is run. 

Personally, I don't like deploymentt code doing any kind of adaption to make 
tests work (e.g. semanpire signalling) because making the code more complicated 
can have other effects that don't easily get noticed.

{noformat}
[INFO] Running org.apache.jena.fuseki.TS_FusekiWebapp
08:24:38 ERROR Server     :: Exception in task 14 execution
org.apache.jena.dboe.transaction.txn.TransactionException: 
TransactionCoordinator has been shutdown
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.checkNotShutdown(TransactionCoordinator.java:345)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.checkActive(TransactionCoordinator.java:340)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.begin(TransactionCoordinator.java:515)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionCoordinator.begin(TransactionCoordinator.java:504)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.transaction.txn.TransactionalBase.begin(TransactionalBase.java:110)
 ~[jena-dboe-transaction-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.dboe.storage.system.DatasetGraphStorage.begin(DatasetGraphStorage.java:59)
 ~[jena-dboe-storage-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.system.Txn.exec(Txn.java:76) 
~[jena-arq-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.system.Txn.executeRead(Txn.java:115) 
~[jena-arq-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.sys.CopyDSG.copy(CopyDSG.java:35) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.sys.DatabaseOps.compact(DatabaseOps.java:236) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.sys.DatabaseOps.compact(DatabaseOps.java:198) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.tdb2.DatabaseMgr.compact(DatabaseMgr.java:62) 
~[jena-tdb2-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at 
org.apache.jena.fuseki.mgt.ActionCompact$CompactTask.run(ActionCompact.java:73) 
~[classes/:?]
        at 
org.apache.jena.fuseki.async.AsyncPool.lambda$submit$0(AsyncPool.java:66) 
~[jena-fuseki-core-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at org.apache.jena.fuseki.async.AsyncTask.call(AsyncTask.java:100) 
[jena-fuseki-core-3.18.0-SNAPSHOT.jar:3.18.0-SNAPSHOT]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[?:1.8.0_252]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_252]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_252]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
[ERROR] Tests run: 189, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
79.542 s <<< FAILURE! - in org.apache.jena.fuseki.TS_FusekiWebapp
[ERROR] compact_01(org.apache.jena.fuseki.TestAdmin)  Time elapsed: 9.375 s  
<<< ERROR!
java.lang.NullPointerException
        at org.apache.jena.fuseki.TestAdmin.compact_01(TestAdmin.java:346)
{noformat}


> HTTP API for TDB compact AND/OR periodical compact
> --------------------------------------------------
>
>                 Key: JENA-1987
>                 URL: https://issues.apache.org/jira/browse/JENA-1987
>             Project: Apache Jena
>          Issue Type: New Feature
>          Components: Fuseki
>            Reporter: Martin Kopeček
>            Assignee: Rob Vesse
>            Priority: Major
>             Fix For: Jena 3.17.0
>
>         Attachments: log
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the 
> compacting of the database from a different node (after updating the data in 
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable 
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual 
> compacting is not an option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to