Symptoms 

Calls return 500, and Glassfish logs are full of messages like this: 

javax.ejb.EJBException: Unable to complete container-managed transaction.; nested exception is: javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5022: Unexpected exception [com.sun.jts.CosTransactions.LogException: Log exception at point 14: 
LOG-003: Read failure] from log.  vmcid: 0x0  minor code: 0  completed: No javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5022: Unexpected exception [com.sun.jts.CosTransactions.LogException: Log exception at point 14: 
LOG-003: Read failure] from log.  vmcid: 0x0  minor code: 0  completed: No
  

Possible cause 

Glassfish has previously been started as another user (e.g. root), and when restarted as another user (e.g. vidispine), files have the wrong permissions. 

Fix 

Stop Glassfish and use chown -R to set the right permissions of the glassfish tree. That is done with chown -R {user} {glassfish-dir} where {glassfish-dir} is the path of the GlassFish directory, and {user} is the correct user to run GlassFish (typically vidispine),  

Possible cause 

In case of a full disk or other file system problem, the transaction log in Glassfish can become corrupted. 

Fix 

Stop Glassfish and remove (or move) the directory domain/*/logs/server/tx. Start Glassfish. The directory should be recreated automatically.     In both these cases, it makes sense to do a reindex afterwards.