KeyMgtGetNextValueConcurrent(), Server Container, PX Job
Posted: Thu Nov 17, 2005 2:18 pm
Hi,
I am primary keying records with the KeyMgtGetNextValueConcurrent() routine from within a Server Container that I am using inside of a Parallel job. It has worked in the past and I do not know what variable has caused it not work now.
Recently I have been getting the following error message in the Director log (and the job aborts):
"PKeySrvrContainer,0: dspipe_wait(2535514): Writer timed out waiting for Reader to connect."
I also got one from the other process which as I understand, is also run on the conductor node since the object is a server object:
"PKeySrvrContainer,1: dspipe_wait(2416800): Writer timed out waiting for Reader to connect."
Another thing that seems to be happening is that when the job is run by hand, it works just fine but when a sequencer runs it, I see the symptoms described above.
What might be the problem, and what might I do to troubleshoot it/solve it?
Thanks in advance.
I am primary keying records with the KeyMgtGetNextValueConcurrent() routine from within a Server Container that I am using inside of a Parallel job. It has worked in the past and I do not know what variable has caused it not work now.
Recently I have been getting the following error message in the Director log (and the job aborts):
"PKeySrvrContainer,0: dspipe_wait(2535514): Writer timed out waiting for Reader to connect."
I also got one from the other process which as I understand, is also run on the conductor node since the object is a server object:
"PKeySrvrContainer,1: dspipe_wait(2416800): Writer timed out waiting for Reader to connect."
Another thing that seems to be happening is that when the job is run by hand, it works just fine but when a sequencer runs it, I see the symptoms described above.
What might be the problem, and what might I do to troubleshoot it/solve it?
Thanks in advance.