[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor-g and GT42 in Condor v7.1.3
- Date: Fri, 24 Oct 2008 17:30:50 -0500
- From: Martin Feller <feller@xxxxxxxxxxx>
- Subject: Re: [Condor-users] Condor-g and GT42 in Condor v7.1.3
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
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
Thanks and regards,
UW-Madison Condor Team
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: