"Memory pool exhausted" error when running PIPE command

[drealeed]

I'm experimenting with ways to identify whether a roxie service is really truly ready to run, with all files copied over to all roxie nodes.

I tried calling testsocket via a PIPE command with the intention of parsing the resulting xml, but get the following error:

Error: System error: 1301: Memory pool exhausted: pool id 4194304 (1216 pages) exhausted, requested 7068 active(1) heap(1/1216) (0, 0), 1301,

The xml coming back from the testsocket command is quite short, just a couple of dozen lines. Here's the ecl:

EXPORT RoxieFileCopyStatus(STRING roxienode) := PIPE('testsocket ' + roxienode + ' -lock \'<control:numfilestoprocess/>\'',{STRING hack});

OUTPUT(RoxieFileCopyStatus('10.173.22.201'));


And here's what's returned when I run the same command ssh'd to that cluster:

[leeddx@node010241100159 ~]$ testsocket 10.173.22.201 -lock '<control:numfilestoprocess/>'
<Control>
<Lock>5</Lock><NumServers>5</NumServers></Control>
<Control>
<Endpoint ep="10.173.22.201:9876">
<FilesToProcess value="0"/>
<Status>ok</Status>
</Endpoint>
<Endpoint ep="10.173.22.203:9876">
<FilesToProcess value="0"/>
<Status>ok</Status>
</Endpoint>
<Endpoint ep="10.173.22.202:9876">
<FilesToProcess value="0"/>
<Status>ok</Status>
</Endpoint>
<Endpoint ep="10.173.22.204:9876">
<FilesToProcess value="0"/>
<Status>ok</Status>
</Endpoint>
<Endpoint ep="10.173.22.205:9876">
<FilesToProcess value="0"/>
<Status>ok</Status>
</Endpoint>
</Control>

Any ideas what's causing that error?

[tlhumphrey2]

Drea,

Did you ever found out what was causing the "memory pool exhausted" error. I'm having the same problem.

Tim