malloc failed

[tcorum]

Can anyone give me an idea on what might be causing this error. When the error occurs it repeats it in the log several 100s of times then the server crashes. The first error that appears is:

125725.f2n17e0!PSQRYSRV.54872: LIBTUX_CAT:1527: ERROR: Memory allocation failure BEREALLOC - realloc failed
125743.f2n17e0!BBL.46206: LIBTUX_CAT:541: WARN: Server APPSRV/70 terminated
125743.f2n17e0!BBL.46206: LIBTUX_CAT:557: INFO: Server APPSRV/70 being restarted
125743.f2n17e0!PSQRYSRV.130234: 03202003: TUXEDO Version 6.5 AIX 2 4 007025954C00.
125743.f2n17e0!PSQRYSRV.130234: LIBTUX_CAT:262: INFO: Standard main starting
125744.f2n17e0!PSQRYSRV.130234: LIBTUX_CAT:476: WARN: Server 99/70: client process 109932: lost message
125744.f2n17e0!PSQRYSRV.130234: LIBTUX_CAT:477: WARN: SERVICE=SqlQuery MSG_ID=1128354386 REASON=server died
125746.f2n17e0!restartsrv.87900: 03202003: TUXEDO Version 6.5 AIX 2 4 007025954C00.
125746.f2n17e0!restartsrv.87900: server APPSRV/70: CMDTUX_CAT:580: INFO: A server process has restarted: 130234


After doing that a few times it begins repeating the following message and then the server fails.

141951.f2n17e0!WSH.39194: LIBTUX_CAT:1526: ERROR: Memory allocation failure BEMA
LLOC - malloc failed
141951.f2n17e0!WSH.39194: WSNAT_CAT:1026: ERROR: Handler received unexpected mes
sage

Any help would be great!!!

Thanks,

Tcorum

 

[psahai]

Did you get a resolution to the problem? I'm facing the same issue right now and don't know how to fix the problem. We're using Peoplesoft 8 with Tuxedo. I've already increased the "Service Timeout" parameter to a high value but it didn't seem to work.

Thanks.

Pari.

 

[AnimalMother]

No resolution yet ...

 

[cra]

I am sure you already read this, however I am including it here:

1526/1527 ERROR: Memory allocation failure error_info 
  Description 
 An attempt dynamically to allocate memory from the operating system failed while trying to tpalloc() a buffer. Additional information is printed with the message indicating the problem. 
 Action 
 Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

From the error messages I guess that this is clearly a bug in the PSQRYSRV server. It seems to allocate a huge tuxedo buffer, which is to large for the system and fails. This error is perhaps not handled correctly by the server, so it crashes afterwards.

The failure of WSH may have the same cause - it tries to allocate a buffer for transmission from/to the /WS-Client, and fails because the buffer is too big. However WSH seems to handle this error correctly and does *not* crash.

I know this may not help very much, but perhaps it points you in the right direction....