Sorry missed the link [1]. [1]https://issues.apache.org/jira/browse/AIRAVATA-418
Lahiru On Tue, May 22, 2012 at 2:27 PM, Lahiru Gunathilake <[email protected]>wrote: > Hi Ning, > > I have created an issue[1] for this and will work on this and update the > deployment once I am done. > > Thanks for pointing this out. Right now AFAIK this is no supported in ogce > version too. > > Lahiru > > > On Tue, May 22, 2012 at 1:28 PM, Lahiru Gunathilake <[email protected]>wrote: > >> Which node is failing ? Is it continuously failing ? >> >> Lahiru >> >> >> On Tue, May 22, 2012 at 12:44 PM, Shen, Ning <[email protected]>wrote: >> >>> Hi, >>> >>> We have error catching in script where the script does "exit 1" whenever >>> abnormal termination of the program such as charmm or gaussian fails. This >>> error somehow is not properly caught by the avirata and not propagated to >>> the gui which should show the error , turn red and stop the workflow. In >>> the old xbaya, we see a huge popup message showing the error and occupies >>> the screen, this has been solved in avirata but the error message is not >>> caught consistently. >>> >>> Ning >>> >>> ------------------------------ >>> *From:* Suresh Marru [[email protected]] >>> *Sent:* Tuesday, May 22, 2012 11:03 AM >>> *To:* Shen, Ning >>> *Cc:* [email protected]; Suresh Marru; Lahiru >>> Gunathilake; [email protected]; Sudhakar Pamidighantam >>> *Subject:* Re: avirata running problems >>> >>> On May 22, 2012, at 11:51 AM, Shen, Ning wrote: >>> >>> Hi, >>> We encounter two problems using avirata: >>> >>> 1. large log file of avirata >>> -rwx------+ 1 Administrators None 1046609834 jackrabbit.log_IS_UNDEFINED >>> >>> When the avirata workflow runs, the above file is generated and can grow >>> too large, i think this should be turned off as it will occupy unnecessary >>> disk space. >>> >>> >>> 2. we get runtime exception and a popup shows up: >>> >>> org.apache.airavata.xbaya.XBayaException: Empty Output Generated >>> at >>> org.apache.airavata.xbaya.util.InterpreterUtil.findInputFromPort(InterpreterUtil.java:213) >>> at >>> org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.handleWSComponent(WorkflowInterpreter.java:979) >>> at >>> org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.executeDynamically(WorkflowInterpreter.java:719) >>> at >>> org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.scheduleDynamically(WorkflowInterpreter.java:357) >>> at >>> org.apache.airavata.xbaya.graph.dynamic.gui.DynamicWorkflowRunnerWindow$3.run(DynamicWorkflowRunnerWindow.java:389) >>> >>> what will be the reason for this? >>> >>> >>> Hi Ning, >>> >>> As Chathura explained in a different email yesterday, these correspond >>> to application error. The error handling on Airavata should be improved to >>> clearly indicate it. Did you check your application logs and see if the >>> application failed? >>> >>> Suresh >>> >>> >>> thanks >>> >>> Ning >>> >>> >>> >> >> >> -- >> System Analyst Programmer >> PTI Lab >> Indiana University >> >> > > > -- > System Analyst Programmer > PTI Lab > Indiana University > > -- System Analyst Programmer PTI Lab Indiana University
