When the job status is unknown; I should be able to delete the job. I can't
right now and it throws an exception. So two things:
-Should be able to delete a job when status is unknown, unless there is a
compelling reason that we can't do that.
-Should display a decent message saying can;t delete the job instead of a stack
trace.
http://nema.lis.uiuc.edu:8080/diy/get/JobManager.jobDetail?id=164
Try deleting this you will get
java.lang.IllegalArgumentException: Cannot delete job 164 because it is still
running, scheduled or submitted.
at org.imirsel.nema.flowservice.NemaFlowService.deleteJob(NemaFlowService.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
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:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy25.deleteJob(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at o
Original issue reported on code.google.com by kumarami...@gmail.com on 28 Jun 2010 at 6:09
Original issue reported on code.google.com by
kumarami...@gmail.com
on 28 Jun 2010 at 6:09