Long Running Processes - Busy Servers

Yahoo Archive
1
If there's a fix and you've got an SCR or an old call or something that we can reference this with, you would be my friend forever............
2

Of late we have begun to see the 'no servers available' error message had I have done the recommened changes (increase servers/decrease lease time etc) One thing I continue to see is long running (busy) servers as in days busy without activity (Last Changed date/time has not changed). I've checked the currently executing tasks and the PIDs of the long running tasks don't match anything that I can find. I've found some reference of the PID's in the log but it doesn't really give me an idea of what they are doing/were doing. I assume they are hung or otherwise locked but they don't showup as locked just busy.

 

Is it safe to cancel the PID's? Can someone shed some light on how to get rid of them or find out what they are?

 

Thanks,

 

Tim Mattson


3
my Rule-of-Thumb is that if the process has been running over a day .. you can kill it.
4
I'm having the same problem, but I can match up the PIDs to tasks in the history tab of the system monitor.  They are always task types of report.  Status on the MfgSys803 AppServer shows the PIDs as locked.  It could be any report, any user.  The user can print the same report 10 times without a locked task and the next one will cause a locked task even though the report printed without a problem.  I have been killing these tasks to keep my server alive and haven't had any problems as a result.

This started about a month ago and I haven't been able to track down a cause.  Some days I get just a couple, and other days I see 30 of them.

Steven G.


On Tuesday, July 29, 2014 5:53 PM, "tmattson57@... [vantage]" <vantage@yahoogroups.com> wrote:


  
<div id="ygrps-yiv-1347120549yiv5855250299ygrp-text" class="ygrps-yiv-1347120549" style="">
  
  
  <div class="ygrps-yiv-1347120549" style=""><span class="ygrps-yiv-1347120549" style="">Of late we have begun to see the &#39;no servers available&#39; error message had I have&nbsp;done the recommened&nbsp;changes&nbsp;(increase servers/decrease lease time etc) One thing I continue to see is long running (busy) servers as in days busy without activity (Last Changed date/time has not changed). I&#39;ve checked the currently executing tasks and the&nbsp;PIDs of the long running tasks&nbsp;don&#39;t match anything that I can find. I&#39;ve found some reference of the PID&#39;s in the log but it doesn&#39;t really&nbsp;give me an idea of what they are doing/were doing. I assume they are hung or otherwise locked but&nbsp;they don&#39;t showup as locked just busy.</span></div>
 
Is it safe to cancel the PID's? Can someone shed some light on how to get rid of them or find out what they are?
 
Thanks,
 
Tim Mattson

</div>
 


<div style="color:#fff;height:0;" class="ygrps-yiv-1347120549"></div></div>
#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299 -- #ygrps-yiv-1347120549yiv5855250299ygrp-mkp { border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mkp hr {
border:1px solid #d8d8d8;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mkp #ygrps-yiv-1347120549yiv5855250299hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mkp #ygrps-yiv-1347120549yiv5855250299ads {
margin-bottom:10px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mkp .ygrps-yiv-1347120549yiv5855250299ad {
padding:0 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mkp .ygrps-yiv-1347120549yiv5855250299ad p {
margin:0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mkp .ygrps-yiv-1347120549yiv5855250299ad a {
color:#0000ff;text-decoration:none;}
#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-sponsor #ygrps-yiv-1347120549yiv5855250299ygrp-lc {
font-family:Arial;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-sponsor #ygrps-yiv-1347120549yiv5855250299ygrp-lc #ygrps-yiv-1347120549yiv5855250299hd {
margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-sponsor #ygrps-yiv-1347120549yiv5855250299ygrp-lc .ygrps-yiv-1347120549yiv5855250299ad {
margin-bottom:10px;padding:0 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299activity span {
font-weight:700;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299activity span:first-child {
text-transform:uppercase;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299activity span a {
color:#5085b6;text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299activity span span {
color:#ff7900;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299activity span .ygrps-yiv-1347120549yiv5855250299underline {
text-decoration:underline;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299attach div a {
text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299attach img {
border:none;padding-right:5px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299attach label {
display:block;margin-bottom:5px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299attach label a {
text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 blockquote {
margin:0 0 0 4px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299bold {
font-family:Arial;font-size:13px;font-weight:700;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299bold a {
text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 dd.ygrps-yiv-1347120549yiv5855250299last p a {
font-family:Verdana;font-weight:700;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 dd.ygrps-yiv-1347120549yiv5855250299last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 dd.ygrps-yiv-1347120549yiv5855250299last p span.ygrps-yiv-1347120549yiv5855250299yshortcuts {
margin-right:0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299attach-table div div a {
text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299attach-table {
width:400px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299file-title a, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299file-title a:active, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299file-title a:hover, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299file-title a:visited {
text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299photo-title a, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299photo-title a:active, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299photo-title a:hover, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div.ygrps-yiv-1347120549yiv5855250299photo-title a:visited {
text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 div#ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg #ygrps-yiv-1347120549yiv5855250299ygrp-msg p a span.ygrps-yiv-1347120549yiv5855250299yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299green {
color:#628c2a;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299MsoNormal {
margin:0 0 0 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 o {
font-size:0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299photos div {
float:left;width:72px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299photos div div {
border:1px solid #666666;height:62px;overflow:hidden;width:62px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299reco-category {
font-size:77%;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299reco-desc {
font-size:77%;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 .ygrps-yiv-1347120549yiv5855250299replbq {
margin:4px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg table {
font-size:inherit;font:100%;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg select, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 input, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg pre, #ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 code {
font:115% monospace;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg * {
line-height:1.22em;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-mlmsg #ygrps-yiv-1347120549yiv5855250299logo {
padding-bottom:10px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-msg p a {
font-family:Verdana;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-msg p#ygrps-yiv-1347120549yiv5855250299attach-count span {
color:#1E66AE;font-weight:700;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-reco #ygrps-yiv-1347120549yiv5855250299reco-head {
color:#ff7900;font-weight:700;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-reco {
margin-bottom:20px;padding:0px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-sponsor #ygrps-yiv-1347120549yiv5855250299ov li a {
font-size:130%;text-decoration:none;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-sponsor #ygrps-yiv-1347120549yiv5855250299ov li {
font-size:77%;list-style-type:square;padding:6px 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-sponsor #ygrps-yiv-1347120549yiv5855250299ov ul {
margin:0;padding:0 0 0 8px;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-text {
font-family:Georgia;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-text p {
margin:0 0 1em 0;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-text tt {
font-size:120%;}

#ygrps-yiv-1347120549 #ygrps-yiv-1347120549yiv5855250299 #ygrps-yiv-1347120549yiv5855250299ygrp-vital ul li:last-child {
border-right:none !important;}
#ygrps-yiv-1347120549



5
I would also check out the E9 Performance Diagnostic Tool to process the server logs to see what the running process is.
We have BAQs that get hung up for some reason. I use this tool to make sure it’s the BAQ before killing the processes.





Joe Rojas | Director of Information Technology | Mats Inc
dir: 781-573-0291 | cell: 781-408-9278 | fax: 781-232-5191

addr: 37 Shuman Ave | Stoughton | Ma | 02072-3734
jrojas@... | www.matsinc.com
Ask us about our clean, green and beautiful matting and flooring

[cid:fc47e2.png@d05a26dc.42aee9e0]
This message is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 29, 2014 5:54 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Long Running Processes - Busy Servers



Of late we have begun to see the 'no servers available' error message had I have done the recommened changes (increase servers/decrease lease time etc) One thing I continue to see is long running (busy) servers as in days busy without activity (Last Changed date/time has not changed). I've checked the currently executing tasks and the PIDs of the long running tasks don't match anything that I can find. I've found some reference of the PID's in the log but it doesn't really give me an idea of what they are doing/were doing. I assume they are hung or otherwise locked but they don't showup as locked just busy.



Is it safe to cancel the PID's? Can someone shed some light on how to get rid of them or find out what they are?



Thanks,



Tim Mattson





[Non-text portions of this message have been removed]
6
We have BAQs that get stuck too on 9.05.702A. Didn't occur in .700C.

I'd love to get a resolution to this because while it happens regularly, I can't force it to happen.

We've got a process now that alerts us if there are two many busy processes for too long so we can go in and deal, but I'd much rather not have to sort this out manually...sometimes if finance runs a process that is legitimately long running, I can't differentiate between it unless they tell me ahead of time.

For what it's worth though, we just kill them and the appservers usually spin up another one.
7

If there is a task that is running and it started at the same time your appserver started, then it is usually the global alerts, or any other task you have setup on a startup schedule.

 

Also, just because the last changed date/time is old doesn’t mean there is no activity on it, that date/time is when the action is it executing was initiated, not the last time it actively did something.

 

If you are running verbose logs, then it should always give you some idea as to what it was or is doing, most entries for a single task will have 4 total entries with the PID, one of them will include a “program” that it is running as it’s process, as well as another line which will tell you what computer the request was initiated from, if it is a terminal server then you will also need to use the session number to determine the actual user, but not everyone logs that on terminal servers so it can be more difficult to narrow it down.

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 29, 2014 5:54 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Long Running Processes - Busy Servers

 




Of late we have begun to see the 'no servers available' error message had I have done the recommened changes (increase servers/decrease lease time etc) One thing I continue to see is long running (busy) servers as in days busy without activity (Last Changed date/time has not changed). I've checked the currently executing tasks and the PIDs of the long running tasks don't match anything that I can find. I've found some reference of the PID's in the log but it doesn't really give me an idea of what they are doing/were doing. I assume they are hung or otherwise locked but they don't showup as locked just busy.

 

Is it safe to cancel the PID's? Can someone shed some light on how to get rid of them or find out what they are?

 

Thanks,

 

Tim Mattson

 




8

I am also now seeing this in 702A and have not found the answers. I have been able to find the users to begin gathering data to send to support.

 

In the Openedge admin I keep a tab open for Server Pool Control and AppServer Client Connections then click the List All button.

 

The PID of the hung process from the server pool is in the list of client connections. This will get you the user that is hung or closed their session.

 

Server logs in verbose mode will give you some idea of what the pid was used for last. I use a log viewer, so I can always have the log open and search thru it. I do 10 logs of 100 MB each, so I have almost two days’ worth of logs to search. I search from the end of the file for the pid and you can see a pattern from the pid.

 

Complete Call:

[14/07/24@05:47:12.102-0400] P-034280 T-070912 1 AS -- (Procedure: 'as/activate.p' Line:490) Incoming call

from DRSEXT1-PC:1

[14/07/24@05:47:12.102-0400] P-034280 T-070912 2 AS AS -- TRACE: SINGLE-RUN Procedure

'bo/ReportMonitor/Sink.p:GetRowsKeepIdleTime' START (14244)

[14/07/24@05:47:12.150-0400] P-034280 T-070912 3 AS AS -- TRACE: SINGLE-RUN Procedure END SUCCESS. (14265)

 

Hung Process:

[14/07/24@05:47:13.406-0400] P-034280 T-070912 1 AS -- (Procedure: 'as/activate.p' Line:490) Incoming call

from OSMITH-PC:1

[14/07/24@05:47:13.406-0400] P-034280 T-070912 2 AS AS -- TRACE: SINGLE-RUN Procedure

'bo/IssueReturn/Sink.p:PrePerformMaterialMovement' START (14244)

[14/07/24@05:47:13.426-0400] P-034280 T-070912 1 AS BAQ        Parameterized execution of '' query on behalf

of osmi01 user is started.

 

Nothing is in the log after this for the pid I killed.

 

In my case I am seeing a BAQ finish and then another one is started that never makes the BAQ file. You can find the BAQs for this process id in the folder set by the –T parameter in the mfgsys.pf file. Mine is EpicorTemp. The baq is named with the process id and I assume a timestamp.

baq3428021114158.p is from the first process in the chart I sent to support below.

 

In the baq there is a section that will reference a table. In my case it is not what attempted to run and died, but gives me a good idea of the screen the user was in.  Unfortunately, there was no smoking gun.

 

PROCEDURE InitFields:

def input param hsrc as handle no-undo.

def input param hRes as handle no-undo.

 

  hbConstants = hSrc:buffer-field("Constants").

  hbConstants = hbConstants:buffer-value.

  hbttUD01 = hSrc:buffer-field("ttUD01").

  hbttUD01 = hbttUD01:buffer-value.

  hCalcField-1 = hres:buffer-field("CalcField-1").

END PROCEDURE.

 

 

pid

user

date

time

table

34280

o smith

24

5:47

[14/07/24@05:47:13.426-0400] P-034280 T-070912 1 AS BAQ        Parameterized execution of '' query on behalf

ud01

of osmi01 user is started.

42484

o smith

24

7:02

14/07/24@07:02:35.488-0400] P-042484 T-006088 1 AS BAQ        Parameterized execution of '' query on behalf

ttIssueReturn

of osmi01 user is started.

40216

m graham

24

14:44

14/07/24@14:44:02.811-0400] P-040216 T-051180 1 AS BAQ        Parameterized execution of '' query on behalf

ttShipHead

of mgra01 user is started.

14624

o smith

25

6:24

[14/07/25@06:24:55.612-0400] P-014624 T-037060 1 AS BAQ        Parameterized execution of '' query on behalf

ttPORel

of osmi01 user is started.

29084

j rol02

25

10:53

[14/07/25@10:53:34.920-0400] P-029084 T-049128 1 AS BAQ        Parameterized execution of '' query on behalf

ttIssueReturn

of jrol02 user is started.

84720

l estling

25

11:14

14/07/25@11:14:31.259-0400] P-084720 T-033768 1 AS BAQ        Parameterized execution of '' query on behalf

ttOrderHed

of lest01 user is started.

73548

t richards

25

12:08

[14/07/25@12:08:47.671-0400] P-073548 T-039040 1 AS BAQ        Parameterized execution of '' query on behalf

ttOrderHed

of tric01 user is started.

 

 

 

Support has asked me to recycle my appservers nightly to keep ahead of the processes, but I would rather not have to kick third shift off each night and get a lot of erroneous system down messages.

 

HTH

 

Greg Payne

 

 

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 29, 2014 5:54 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Long Running Processes - Busy Servers

 

 

Of late we have begun to see the 'no servers available' error message had I have done the recommened changes (increase servers/decrease lease time etc) One thing I continue to see is long running (busy) servers as in days busy without activity (Last Changed date/time has not changed). I've checked the currently executing tasks and the PIDs of the long running tasks don't match anything that I can find. I've found some reference of the PID's in the log but it doesn't really give me an idea of what they are doing/were doing. I assume they are hung or otherwise locked but they don't showup as locked just busy.

 

Is it safe to cancel the PID's? Can someone shed some light on how to get rid of them or find out what they are?

 

Thanks,

 

Tim Mattson

 


CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
9

Jason:

 

How and where does this alert run? I would love to not have to keep checking the admin server.

 

Thanks

 

Greg

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 30, 2014 11:09 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Long Running Processes - Busy Servers

 

 

We have BAQs that get stuck too on 9.05.702A. Didn't occur in .700C.

 

I'd love to get a resolution to this because while it happens regularly, I can't force it to happen.

 

We've got a process now that alerts us if there are two many busy processes for too long so we can go in and deal, but I'd much rather not have to sort this out manually...sometimes if finance runs a process that is legitimately long running, I can't differentiate between it unless they tell me ahead of time.

 

For what it's worth though, we just kill them and the appservers usually spin up another one.


CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
10
I have nagios rigged with a batch file that runs every few minutes that queries and monitors the appserver status to return a count of how many busy servers there are. Once it gets above a certain threshold I get alerts. It's not particularly pretty but it certainly makes my life easier.

If anyone anywhere has an actual fix to this problem, I'm all ears.
11
I believe this is a known bug in 702A, and a fix for this is available from Epicor.

You might be able to tell if this is the problem by looking in your epicortemp folder. When it happened we saw tens of thousands of little temporary files.

Cheers!

Chris Heins
Enterprise Programmer/Analyst
PNY Technologies, Inc.
[Description: Description: cid:image001.jpg@01CA473E.14A061C0]
p: 973.560.5370
m: 908.256.3662
e: cheins@...<mailto:cheins@...>
w: www.pny.com<http://www.pny.com/>

_________________________________________________________________________________________________________
NOT INTENDED AS A SUBSTITUTE FOR A WRITING
NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO, SHALL CONSTITUTE A BINDING CONTRACT, OR ANY CONTRACTUAL OBLIGATION BY PNY, OR ANY INTENT TO ENTER INTO ANY BINDING OBLIGATIONS, NOTWITHSTANDING ANY ENACTMENT OF THE UNIFORM ELECTRONIC TRANSACTIONS ACT, THE FEDERAL E-SIGN ACT, OR ANY OTHER STATE OR FEDERAL LAW OF SIMILAR SUBSTANCE OR EFFECT. THIS EMAIL MESSAGE, ITS CONTENTS AND ATTACHMENTS ARE NOT INTENDED TO REPRESENT AN OFFER OR ACCEPTANCE OF AN OFFER TO ENTER INTO A CONTRACT. NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO SHALL ALTER THIS DISCLAIMER.
This e-mail message from PNY Technologies, Inc. (http://www.pny.com) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


[Non-text portions of this message have been removed]
12

I have read about nagios, but we don’t have it or anything similar.

 

thanks

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 30, 2014 3:33 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Long Running Processes - Busy Servers

 

 

I have nagios rigged with a batch file that runs every few minutes that queries and monitors the appserver status to return a count of how many busy servers there are. Once it gets above a certain threshold I get alerts. It's not particularly pretty but it certainly makes my life easier.

 

If anyone anywhere has an actual fix to this problem, I'm all ears.


CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
13

I deleted over 100K of them last week. do you have any specifics on the known issue? I have worked with two different support reps and it has not been found as a known problem.

 

thanks for any help

 

Greg

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 30, 2014 3:36 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Long Running Processes - Busy Servers

 

 

I believe this is a known bug in 702A, and a fix for this is available from Epicor.

You might be able to tell if this is the problem by looking in your epicortemp folder. When it happened we saw tens of thousands of little temporary files.

Cheers!

Chris Heins
Enterprise Programmer/Analyst
PNY Technologies, Inc.
[Description: Description: cid:image001.jpg@01CA473E.14A061C0]
p: 973.560.5370
m: 908.256.3662
e: cheins@...<mailto:cheins@...>
w: www.pny.com<http://www.pny.com/>

__________________________________________________________
NOT INTENDED AS A SUBSTITUTE FOR A WRITING
NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO, SHALL CONSTITUTE A BINDING CONTRACT, OR ANY CONTRACTUAL OBLIGATION BY PNY, OR ANY INTENT TO ENTER INTO ANY BINDING OBLIGATIONS, NOTWITHSTANDING ANY ENACTMENT OF THE UNIFORM ELECTRONIC TRANSACTIONS ACT, THE FEDERAL E-SIGN ACT, OR ANY OTHER STATE OR FEDERAL LAW OF SIMILAR SUBSTANCE OR EFFECT. THIS EMAIL MESSAGE, ITS CONTENTS AND ATTACHMENTS ARE NOT INTENDED TO REPRESENT AN OFFER OR ACCEPTANCE OF AN OFFER TO ENTER INTO A CONTRACT. NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO SHALL ALTER THIS DISCLAIMER.
This e-mail message from PNY Technologies, Inc. (http://www.pny.com) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

[Non-text portions of this message have been removed]


CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."