Re: [ptp-dev] Fwd: Re: submitting Jobs

[Greg Watson <g.watson@xxxxxxxxxxxx>]

Al,

The launch plugin is where everything gets started when you click on the run button. The AbstractProxyRuntimeClient code is not called until long after that.  If you want to trace it, set a breakpoint in org.eclipse.ptp.launch.AbstractParallelLaunchConfigurationDelegate#submitJob.

Cheers,
Greg

On Apr 6, 2010, at 4:49 PM, Albert L. Rossi wrote:

> Greg,
> 
> So I think the problem may be that AbstractParallelLaunchConfigurationDelegate is not in the execution path.  I think that for the resource managers, the submission is being handled by the submitJob method in the org.eclipse.ptp.proxy.runtime.client.AbstractProxyRuntimeClient; the former seems specific to the debug plugins.  
> 
> Is this not supposed to be the case? I see IBM, PEP and SLURM using this branch of the class hierarchy.
> 
> Thanks, Al
> 
> 
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> "History does not repeat itself, but often it rhymes." (attr. Mark Twain)
> 
> ----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
>> Al,
>> 
>> There are no other submission errors that I'm aware of. If the job is submitted successfully to the job scheduler then this event should never be raised. The proxy must do nothing until the job scheduler has acknowledged that the submission either succeeds or fails, at which point it sends a new job event or raises a submit job error event respectively. Once a job has been created, the proxy should indicate errors using the job status attribute.
>> 
>> Greg
>> 
>> On Apr 6, 2010, at 4:31 PM, Albert L. Rossi wrote:
>> 
>>> Roland,
>>> 
>>> Is this what you mean?  Or are you sending back an this event after submission from the client completes (i.e., the call to submit returns from the proxy, but the proxy then discovers something wrong with the submit configuration)?
>>> 
>>> Greg,
>>> 
>>> I had thought that a submission error would be handled in the layers above the specific ResourceManager.  However, I also thought I would try the following:
>>> 
>>> - Make the PBSLaunchConfigurationTab implement IResourceManagerListener;
>>> - Add this to the passed in IResourceManager on initializeFrom
>>> - Implement an error message using the errorDialog methods in the org.eclipse.ptp.launch.PTPLaunchPlugin 
>>> 
>>> This is a bit kludgy, but I wanted to see if it captures the error Roland says is not being displayed.  
>>> 
>>> Al
>>> 
>>> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>>> "History does not repeat itself, but often it rhymes." (attr. Mark Twain)
>>> 
>>> ----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
>>>> Good question, but I think it's already dealt with. It looks like the event is eventually translated into an IResourceManagerSubmitJobErrorEvent that is handled by the launch system:
>>>> 
>>>> 1. First, IProxyRuntimeSubmitJobErrorEvent is translated into IRuntimeSubmitJobErrorEvent in org.eclipse.ptp.rtsystem.AbstractProxyRuntimeSystem#handleEvent.
>>>> 
>>>> 2. Next, IRuntimeSubmitJobErrorEvent is translated into IResourceManagerSubmitJobErrorEvent in org.eclipse.ptp.rmsystem.AbstractRuntimeResourceManager#handleEvent. 
>>>> 
>>>> 3. This event is then handled in org.eclipse.ptp.launch.AbstractParallelLaunchConfigurationDelegate.RMListener#handleEvent which set the status of the job. 
>>>> 
>>>> 4. Finally, org.eclipse.ptp.launch.AbstractParallelLaunchConfigurationDelegate#submitJob checks the submission status, and if the status is an error, it raises a CoreException. This will create a dialog containing the error message.
>>>> 
>>>> Note that this event is generated only if the job *submission* fails, so it is before the job is actually created in the model. Hence the job status icons can't be used to indicate the error. 
>>>> 
>>>> Regards,
>>>> Greg
>>>> 
>>>> On Apr 6, 2010, at 3:11 PM, Albert L. Rossi wrote:
>>>> 
>>>>> Greg,
>>>>> 
>>>>> I'm posting a question to the list because I think I need a little guidance.
>>>>> 
>>>>> We have a very basic, hard-coded version of the PBS Launch Tab working, and I'm trying to move now to the next step of implementing one which is not just a place-holder for testing.  
>>>>> 
>>>>> One of the issues which came up when Roland used the Run Configuration to launch against the PBS proxy was in terms of the propagation of an IProxyRuntimeSubmitJobErrorEvent and its eventual exposure to the user.  There are handlers implemented for intercepting job submission events in the AbstractRTSystem classes, but the final listener seems to be missing at that level which would do something (like an error message widget) with it.  Am I mistaken?
>>>>> 
>>>>> If it is missing, where should the listener reside (it's not really PBS-specific, I don't think), and I'm also a bit uncertain as to how to create hooks for adding the necessary listener to the RTSystem class from UI parts (the listener obviously should not live in the org.eclipse.ptp.rm.core plugin, since it is UI-specific).
>>>>> 
>>>>> Thanks for any help you can give here.
>>>>> 
>>>>> Al
>>>>> _______________________________________________
>>>>> ptp-dev mailing list
>>>>> ptp-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>> 
>>>> _______________________________________________
>>>> ptp-dev mailing list
>>>> ptp-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>>> 
>>> 
>>> _______________________________________________
>>> ptp-dev mailing list
>>> ptp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>> 
>> _______________________________________________
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>> 
> 
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev