manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bisonti Mario <>
Subject R: Job in aborting status
Date Tue, 12 Jun 2018 13:25:48 GMT
No, I am testing on the /example directory so I am using local HSQLDB
I copied script from the /usr/share/manifoldcf/multiprocess-file-example to
the /usr/share/manifoldcf/example to try to clean-up my situation, but perhaps the script
isn’t good for me because I am using jetty on the example directory?


Da: Karl Wright <>
Inviato: martedì 12 giugno 2018 15:23
Oggetto: Re: Job in aborting status

Hi Mario,

It appears you are trying to use embedded HSQLDB in a multiprocess environment.  That is not

In a multiprocess environment, you have the following choices:

(1) standalone HSQLDB
(2) postgresql
(3) mysql


On Tue, Jun 12, 2018 at 9:06 AM Bisonti Mario <<>>
Thanks Karl.
I tried to execute lock-clean from my example directory after I stop manifoldcf but I obtain:

administrator@sslrvivv01:/usr/share/manifoldcf/example$ sudo -E ./
Configuration file successfully read
Synchronization storage cleaned up
2018-06-12 15:03:35,395 Shutdown thread FATAL Unable to register shutdown hook because JVM
is shutting down. java.lang.IllegalStateException: Cannot add new shutdown hook as this is
not started. Current state: STOPPED
        at org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.addShutdownCallback(
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.addShutdownCallback(
        at org.apache.logging.log4j.core.LoggerContext.setUpShutdownHook(
        at org.apache.logging.log4j.core.LoggerContext.start(
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(
        at org.apache.logging.log4j.LogManager.getContext(
        at org.apache.log4j.Logger$PrivateManager.getContext(
        at org.apache.log4j.Logger.getLogger(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.hsqldb.lib.FrameworkLogger.<init>(Unknown Source)
        at org.hsqldb.lib.FrameworkLogger.getLog(Unknown Source)
        at org.hsqldb.lib.FrameworkLogger.getLog(Unknown Source)
        at org.hsqldb.persist.Logger.getEventLogger(Unknown Source)
        at org.hsqldb.persist.Logger.logInfoEvent(Unknown Source)
        at org.hsqldb.persist.DataFileCache.logInfoEvent(Unknown Source)
        at Source)
        at org.hsqldb.persist.Log.getCache(Unknown Source)
        at org.hsqldb.persist.Logger.getCache(Unknown Source)
        at org.hsqldb.persist.Logger.newStore(Unknown Source)
        at org.hsqldb.persist.PersistentStoreCollectionDatabase.getStore(Unknown Source)
        at org.hsqldb.Table.getRowStore(Unknown Source)
        at org.hsqldb.TableBase.isEmpty(Unknown Source)
        at org.hsqldb.TableWorks.addIndex(Unknown Source)
        at org.hsqldb.StatementSchema.getResult(Unknown Source)
        at org.hsqldb.StatementSchema.execute(Unknown Source)
        at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
       at org.hsqldb.scriptio.ScriptReaderText.readDDL(Unknown Source)
        at org.hsqldb.scriptio.ScriptReaderBase.readAll(Unknown Source)
        at org.hsqldb.persist.Log.processScript(Unknown Source)
        at Source)
        at Source)
        at org.hsqldb.Database.reopen(Unknown Source)
        at Source)
        at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)
        at org.hsqldb.DatabaseManager.newSession(Unknown Source)
        at org.hsqldb.jdbc.JDBCConnection.<init>(Unknown Source)
        at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source)
        at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
        at java.sql.DriverManager.getConnection(
        at java.sql.DriverManager.getConnection(
        at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.closeDatabase(
        at org.apache.manifoldcf.core.system.ManifoldCF$DatabaseShutdown.closeDatabase(
        at org.apache.manifoldcf.core.system.ManifoldCF$DatabaseShutdown.doCleanup(
        at org.apache.manifoldcf.core.system.ManifoldCF.cleanUpEnvironment(
        at org.apache.manifoldcf.core.system.ManifoldCF$

What could I do?

Thank you very very much for your help.


Da: Karl Wright <<>>
Inviato: martedì 12 giugno 2018 14:26
Oggetto: Re: Job in aborting status

Hi Mario,

Two things you should know.  First, if you have very large jobs, it can take a while to abort
them.  This is because the documents need to have their document priority cleared, and that
can take a while for a large job.  Second, what you describe sounds like you may have stuck
locks.  This can happen if you are using a multiprocess setup and are using file-based synchronization
and you kill jobs with kill -9.  To clean this up, you need to perform the lock-clean procedure:

(1) Shut down all manifoldcf processes
(2) Execute the lock-clean script
(3) Start up the manifoldcf processes


On Tue, Jun 12, 2018 at 7:11 AM Bisonti Mario <<>>

I have jobs in aborting status and it hangs.
I tried to restart manifoldcf, I restarted the machine, but the job hangs in aborting status.

Now, I am not able to start every job because they stay in starting status

How could I solve it?

View raw message