Task #10910 (closed)
Opened 6 years ago
Closed 6 years ago
BUG: Stacktrace after non-targeted Move of MIF
| Reported by: | pwalczysko | Owned by: | jamoore |
|---|---|---|---|
| Priority: | blocker | Milestone: | 5.0.0-beta1 |
| Component: | Web | Version: | n.a. |
| Keywords: | alpha3 build | Cc: | ux@…, fs@…, mtbcarroll |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | FS Demo 4.3 |
Description (last modified by wmoore)
Build OMERO.web 5.0.0-alpha3-ice33-b3407 AND tested on develop.
Ran the server locally.
Workflow:
- Import Leica_LIF/fabrice/Rosier.liff - select all 3 images a the MIF
- try to Move them
- at the Move stage, do not select any target Project /Dataset (i.e. expecting the MIF to end up in Orphaned images in the target group)
- proceed with the Move
- Activities window pops up, after some activity a failure is reported in the Activities window
- see the report below
STEP ERR step: 2000, stacktrace: ome.services.graphs.GraphConstraintException(message=Image:517 improperly links to 1 objects at ome.services.chgrp.ChgrpValidation.action(ChgrpValidation.java:106) at ome.services.graphs.GraphState.execute(GraphState.java:351) at omero.cmd.graphs.ChgrpI.step(ChgrpI.java:157) at omero.cmd.basic.DoAllI$X.step(DoAllI.java:107) at omero.cmd.basic.DoAllI.step(DoAllI.java:319) at omero.cmd.HandleI.steps(HandleI.java:435) at omero.cmd.HandleI$1.doWork(HandleI.java:365) at omero.cmd.HandleI$1.doWork(HandleI.java:361) at sun.reflect.GeneratedMethodAccessor261.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at ome.services.util.Executor$Impl$Interceptor.invoke(Executor.java:518) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at ome.security.basic.EventHandler.invoke(EventHandler.java:154) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.orm.hibernate3.HibernateInterceptor.invoke(HibernateInterceptor.java:111) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:108) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at ome.tools.hibernate.ProxyCleanupFilter$Interceptor.invoke(ProxyCleanupFilter.java:241) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at ome.services.util.ServiceHandler.invoke(ServiceHandler.java:116) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) at $Proxy66.doWork(Unknown Source) at ome.services.util.Executor$Impl.execute(Executor.java:416) at omero.cmd.HandleI.run(HandleI.java:359) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at ome.services.util.Executor$Impl$1.call(Executor.java:447) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) , message: , GraphConstraintException: true, id: 254
Change History (7)
comment:1 Changed 6 years ago by pwalczysko
comment:2 Changed 6 years ago by pwalczysko
It does not matter whether you target the move into project / dataset or not - the stacktrace is always the same.
comment:3 Changed 6 years ago by jburel
- Sprint changed from FS demo 4.2 to FS Demo 4.3
Moved from sprint FS demo 4.2
comment:4 Changed 6 years ago by wmoore
- Description modified (diff)
- Owner changed from web-team@… to jamoore
I get the same error with Leica_LIF/fabrice/Rosier.lif on develop. Passing to Josh...
comment:5 Changed 6 years ago by jamoore
Starting to look into this.
comment:6 Changed 6 years ago by jamoore
This looks to be a very particular problem related to metadata:
2013-05-27 14:42:56,973 WARN [ ome.services.graphs.GraphStep] (3-thread-5) TransmittanceRange:5 improperly linked by ome.model.acquisition.Filter.transmittanceRange: 1
Looking into adding it into spec.xml now.
comment:7 Changed 6 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
Can't reproduce on today's build, nor on my branch for #11054. Closing.
Identical stacktrace occurs when modifying the above workflow so, that first only 1 image of the MIF is selected, and after a warning and rejection of the action the "Move All" button in Activities window is clicked.