Random App Server pool maxing out.

[techjohnny]

When our app servers max out, "No More Available App Servers," it was told by support that we could locate the culprit by identifying the PID generated in very large DBI files.

Will any of these files provide any evidence on what is causing our system to "crash?"

procore
protrace.xxxxx
lbiaxxxxx
DBIxxxxx0xxxxx
srtx00000

The support staff for our software that uses Progress suggested taking the PID from the end of the largest DBI files and cross referencing with the log files to identify the PID. I've done this, but the PID ends up being associated with many of the users using the MRP software.

Last resort. Can somebody recommend a consultant that could identify the underlying cause of our crashes? The MRP company thinks it's in one of the customized queries we run.

--tj

 

[rstanciu]

DBI files are linked to large TEMP-TABLES/DATASETS.

Large DBI files is normal in OE 10.x You can try to reduce the block-size.
of the DBI file use the client startup parameter -tmpbsize set to 1.

file: $DLC/properties/ubroker.properties
srvrStartupParam= - tmpbsize 1

another problem can occurs is the RAM needs of AppServers if you can add this variable
to the appServer configuration (ubroker.properties) each broker runs with minimum 64Mb RAM.

jvmArgs=-Xms64m

 

[TomBascom]

What version of Progress on what platform?

In general there is no reliable relationship between DBI file names and PIDs. You have to use a tool like fuser, lsof or the sysinternals stuff to figure out who it belongs too.

Also, DBI files are not directly related to queries -- they are related to temp-tables. So it wouldn't be the query so much as it would be the code surrounding it. (SQL queries also create DBI files for joins and so forth.)

Reducing the tmpbsize may help, increasing -Bt may also help.

And, as a consultant, I'd be happy to help

 

[techjohnny]

Our current -Bt is set 1024. What would you recommend that we try?

 

[TomBascom]

That depends entirely on how large your DBI files grow and why.

BTW -- size of DBI files isn't directly related to app server availability. So you may be looking at the wrong problem.