Hi,

first of all I want to thank you. We had the same problem and primarily
your suggested fix helped but after approximately 24h the container
process pegged 100% of the CPU again, until we restart it. It is fully
functional but the system is slow. The only error message we found in
the logs is:
2009-01-25 22:01:29,820 ERROR container.ServiceThread
[ServiceThread-5370,run:297] Unexpected error during request processing
java.lang.NullPointerException
        at
org.globus.wsrf.container.GSIServiceThread.process(GSIServiceThread.java:151)
        at
org.globus.wsrf.container.ServiceThread.run(ServiceThread.java:291)
2009-01-25 22:01:33,139 ERROR container.ServiceThread
[ServiceThread-5353,run:297] Unexpected error during request processing
java.lang.NullPointerException
        at
org.globus.wsrf.container.GSIServiceThread.process(GSIServiceThread.java:151)
        at
org.globus.wsrf.container.ServiceThread.run(ServiceThread.java:291)

We tried to upgrade from 4.0.5 to 4.0.8 but it still persists.

Any ideas?

Cheers,

Kay

Patrick Armstrong wrote, on 16.01.2009 23:05:
> On 16-Jan-09, at 1:10 PM, Martin Feller wrote:
>> This sounds as if you are hitting
>> http://bugzilla.globus.org/globus/show_bug.cgi?id=6341
> 
> Yep! This was exactly the issue, as far as I can see. I patched the
> system as described in the bug, and I get a nice container error now!
> Much better than an infinite loop.
> 
> I made a patch, and if anyone is running into this issue, you can patch
> your system by running the following on your globus server:
> 
> wget -qO-
> https://particle.phys.uvic.ca/~patricka/globus-gram-local-proxy-tool.patch
> | patch $GLOBUS_LOCATION/libexec/globus-gram-local-proxy-tool
> 
> --patrick

-- 
Dipl.-Inform. Kay Dörnemann
Distributed Systems Group      | Information Systems Institute
University of Marburg, Germany | University of Siegen, Germany
Phone: +49-6421-28-21563       | +49-271-740-4075
Fax:   +49-6421-28-21573       | +49-271-740-2372

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to