Omnivore errors : Omnivore Support

Requires dev

If the jobs fails with one of these errors it's very likely a bug in the Omnivore code and it needs a dev to fix it.

java.lang.NullPointerException

Explanation: Omnivore is written in Groovy that is on top on Java. The code is attempting to use a null object.

groovy.lang.MissingPropertyException

Eg: https://support.omnivore.com.au/a/tickets/143724

Explanation: Omnivore is written in Groovy. The code is attempting to use a variable or property that doesn't exist.

A variation of the above slightly different text:

No such property <insert word here> for class: com.machinehelix.omnivore.<more words here>

Eg:

error: No such property: site for class: com.machinehelix.omnivore.account.AccountService

org.springframework.dao.DataIntegrityViolationException

Explanation: we try to save in the database a value that doesn't satisfy the database constraints. usually it's either too long or it's a null value.

If the jobs fails with an error like this it's not an Omnivore issue. The word "remote" means it is the other system where the error occurs.

com.machinehelix.omnivore.net.RemoteException

com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!

Explanation: Happens when the Tomcat server is restarted.

org.springframework.dao.CannotAcquireLockException

org.hibernate.exception.LockAcquisitionException

com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction

This might happen sometimes or even often. Unless it happens always, it can be ignored:

org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction

~~~

Also see