Hi LJ, Yes, you are correct LJ. A malloc error is a symptom, not a cause and there are a lot of route causes for it. The info I gave referred to one route cause that may be fairly common. Any time you see them in the arerror.log or similar they are cause for concern as the server may appear to keep on working, but just be generating rollback after rollback on the biggest and most expensive transactions. As you say with 32bit servers there may not be a lot of memory around to play with so tuning memory use and the presence of any memory leaks are significant. The server log files can tell you a lot.
Rod On 13 March 2014 21:21, LJ LongWing <[email protected]> wrote: > ** > Malloc literally means Memory Allocation. Any time you get a Malloc > error, it means that your Application server attempted to do something that > required more memory than your OS had/was able to allocate. We used to > receive this error on a regular basis on our 32 Bit machines when our > Remedy tried to allocate more than 2GB of RAM to the ARServer process. To > figure this out you need to likely turn on more than Thread logging, and > see if you can capture some details about what your workflow is doing at > the time of the malloc error, and see if you can re-architect something to > prevent it from trying to do it 'all at once'...whatever it is. > > > On Thu, Mar 13, 2014 at 1:07 AM, shashidhar M S <[email protected] > > wrote: > >> Hello Experts, >> >> We are getting the Malloc failed on server error in our production >> environment daily. Below is the log trace. I am confused as what might be >> causing this issue. Please can someone help me out on this? >> >> hu Mar 13 01:52:02 2014 390620 : AR System server terminated when a >> signal/exception was received by the server (ARNOTE 20) >> Thu Mar 13 01:52:02 2014 >> Timestamp: 1394689922.4490 >> Thread Id: 29048 >> Version: 7.5.00 Patch 007 201009161400 Sep 16 2010 16:20:23 >> ServerName: arsprod >> Database: SQL -- Oracle >> Hardware: Intel Pentium >> OS: Windows Server 2003 >> RPC Id: 1186482 >> RPC Call: 121 (XMLGE) >> RPC Queue: 390620 >> Client: User BMCCTRLM from Webservice (protocol 14) at IP address >> 10.218.105.64 >> Logging On: Thread >> Code: c0000005 >> Operation: write >> Access Addr: 0x230 >> Stack Begin: >> Addr: 0083B692 >> Addr: 00515F1F >> Addr: 00523F7B >> Addr: 53214782 >> Stack End >> >> Thu Mar 13 01:52:02 2014 390620 : AR System server terminated when a >> signal/exception was received by the server (ARNOTE 20) >> Thu Mar 13 01:52:02 2014 0xc0000005 >> Thu Mar 13 01:52:02 2014 390620 : AR System server terminated -- fatal >> error encountered (ARNOTE 21) >> Thu Mar 13 01:55:10 2014 390620 : AR System server terminated when a >> signal/exception was received by the server (ARNOTE 20) >> Thu Mar 13 01:55:10 2014 >> Timestamp: 1394690110.8880 >> Thread Id: 61196 >> Version: 7.5.00 Patch 007 201009161400 Sep 16 2010 16:20:23 >> ServerName: arsprod >> Database: SQL -- Oracle >> Hardware: Intel Pentium >> OS: Windows Server 2003 >> RPC Id: 1202227 >> RPC Call: 121 (XMLGE) >> RPC Queue: 390620 >> Client: User POMEROY from Webservice (protocol 14) at IP address >> 10.218.88.229 >> Logging On: Thread >> Code: c0000005 >> Operation: write >> Access Addr: 0x230 >> Stack Begin: >> Addr: 0083B692 >> Addr: 00515F1F >> Addr: 00523F7B >> Addr: 5321483E >> Stack End >> >> Thu Mar 13 01:55:10 2014 390620 : AR System server terminated when a >> signal/exception was received by the server (ARNOTE 20) >> Thu Mar 13 01:55:10 2014 0xc0000005 >> Thu Mar 13 01:55:10 2014 390620 : AR System server terminated -- fatal >> error encountered (ARNOTE 21) >> Thu Mar 13 01:57:05 2014 390620 : AR System server terminated when a >> signal/exception was received by the server (ARNOTE 20) >> Thu Mar 13 01:57:05 2014 >> Timestamp: 1394690225.2890 >> Thread Id: 24020 >> Version: 7.5.00 Patch 007 201009161400 Sep 16 2010 16:20:23 >> ServerName: arsprod >> Database: SQL -- Oracle >> Hardware: Intel Pentium >> OS: Windows Server 2003 >> RPC Id: 1213519 >> RPC Call: 121 (XMLGE) >> RPC Queue: 390620 >> Client: User BMCCTRLM from Webservice (protocol 14) at IP address >> 10.218.105.64 >> Logging On: Thread >> Code: c0000005 >> Operation: write >> Access Addr: 0x230 >> Stack Begin: >> Addr: 0083B692 >> Addr: 00515F1F >> Addr: 00523F7B >> Addr: 532148B1 >> Stack End >> >> Thu Mar 13 01:57:05 2014 390620 : AR System server terminated when a >> signal/exception was received by the server (ARNOTE 20) >> Thu Mar 13 01:57:05 2014 0xc0000005 >> Thu Mar 13 01:57:05 2014 390620 : AR System server terminated -- fatal >> error encountered (ARNOTE 21) >> Thu Mar 13 01:57:34 2014 : Action Request System(R) Server Version 7.5.00 >> Patch 007 201009161400 >> (c) Copyright 1991-2009 BMC Software, Inc. >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
