Not that I know of. I didn't notice the error right when it happened. It occurred about 40 minutes after I released the system to users (all two at that time of morning). I was done with everything on the server and finishing up some documentation so I don't know what the resources looked like a that moment.
Now that I had a change to look again I was wrong about the progression being the same. It was stack limit -> DB connection error (different than Victor's DB update timeout) -> AR terminated. Wed Nov 28 04:23:19 2012 390635 : Approaching physical stack limit. (ARERR8749) Wed Nov 28 04:23:19 2012 390635 : Unable to connect to the SQL database. ( ARERR 551) Wed Nov 28 04:23:19 2012 Stop server Wed Nov 28 04:23:19 2012: AR System server terminated — fatal error occurred in ARSERVER (ARNOTE 21) Wed Nov 28 04:23:20 2012 : Action Request System(R) Server x64 Version 7.6.04 SP4 201209051922 (c) Copyright 1991-2011 BMC Software, Inc. I don't want to steal the thread about his DMT issue. It seemed odd this being the first time I have seen the physical stack limit error and Victor happens to mention days later. Jason On Sun, Dec 2, 2012 at 2:24 PM, Tauf Chowdhury <taufc...@gmail.com> wrote: > ** > Jason, was there a spike in arserver process memory usage? > > Sent from my iPhone > > On Dec 2, 2012, at 5:09 PM, Jason Miller <jason.mil...@gmail.com> wrote: > > ** > > I saw the "Approaching physical stack limit" error for the first time > Tuesday night after upgrading production from 7.5 to 7.6.04 64-bit. It was > the same progression you observed, DB timeout -> stack limit -> AR > terminated. I have only seen it once so far. > > Jason > On Dec 2, 2012 1:30 AM, "Victor" <vico...@gmail.com> wrote: > >> Hi Adhwari, >> >> Unfortunately I didn't get past creating the first job. After logging >> back in >> I could not find the job created in job console. >> >> Thanks for your time. >> >> Regards, >> Victor. >> >> On Sunday 02 Dec 2012 08:06:20 Kulkarni, Adhwari wrote: >> > Hi Victor, >> > This kind of error is usually observed when you are creating the first >> job >> > using the 'job console'. That is the time when the UDM engine builds the >> > complete dependency data required for UDM to work which takes a lot of >> > resources. Do you see the same error while creating all the jobs? >> > Also, can you please check if the job is created by logging back in. >> > >> > Regards, >> > Adhwari >> > >> > >> >> >> _______________________________________________________________________________ >> 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_ > > _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"
