Re: [Condor-users] Condor-g and GT42 in Condor v7.1.3

[Martin Feller <feller@xxxxxxxxxxx>]

I debugged a little bit, maybe a starting point:

NotificationConsumerProvider.notify() (NotificationConsumerProvider is in wsrf_core.jar)
is the method being invoked when a notification message comes in.
After adding some logging statements to that class and swapping the wsrf_core.jar in the
condor installation I can see that this method is called, so notification are received, but
the callback is null. That's why deliver() is not called on the NotifyCallback.
I can't tell why the callback is null though.

See around line 153 on http://tinyurl.com/6zcod4

Martin

Jaime Frey wrote:
> On Oct 24, 2008, at 12:45 PM, Martin Feller wrote:
>
> > I'm currently testing ws-gram v4.2 support in condor-g from 7.1.3.
> >
> > It seems that job state change notification messages are not  
> > processed on the client-side,
> > because, according to the output of condor_q, jobs change their  
> > state only when the client
> > polls for state (GRIDMANAGER_JOB_PROBE_INTERVAL==300).
>
>
> I'm seeing the same problem in my own testing.
>
> The GAHP server's NotifyCallback.deliver() is not being called for the  
> messages. I don't know anything more than that so far. I'm continuing  
> to investigate.
>
> Thanks and regards,
> Jaime Frey
> UW-Madison Condor Team
>
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/