Hi Jarett, Can you remove the entries of ls_snakemake in application catalog database as well? I believe Eroma was able to reproduce the issue and we will work on a fix. Sorry for the troubles.
Suresh > On Dec 28, 2016, at 5:13 PM, Jarett DeAngelis <[email protected]> wrote: > > So, I keep getting this popping up in my log, and whenever it does, the > middleware grinds to a halt and will not process any more jobs through: > > 2016-12-28 14:56:03,058 [pool-3-thread-49] ERROR > org.apache.airavata.api.server.handler.AiravataServerHandler - > ls_snakemake_003a47d0-0d2c-474a-b734-9f4bf2903a03 > org.apache.airavata.registry.cpi.AppCatalogException: > javax.persistence.NoResultException: Query "SELECT p FROM > ApplicationInterface p WHERE p.interfaceID =:param0" selected no result, but > expected unique result. > > This “ls_snakemake” job is months old and is associated with an interface, > module and deployment which no longer exist, which is why this error is > getting thrown. What I don’t understand is what is “reminding” Airavata of > this job and causing it to get hung up. Last week, I found references to it > in the experiment catalog database in the EXPERIMENT table, and deleting > these allowed Airavata to continue. Now it is happening again and the > references are gone. How do I eliminate all references to this job from all > of Airavata such that it stops getting hung up on this phantom job? > > Thanks, > Jarett
