WebMethods IS 601 Threads

[schung888]

Our Server Thread Pool settings is Minimum Threads 10, Maximum Threads 250.

When we start our I.S., the System Threads (Server -> Statistics) are around 181.

Once in a while, we will receive a large EDI files (that consists of ~60 X12 EDI Transactions). Oour processing rules will invoke a flow services (ASYNCHONROUS) to process each X12 transactions. As a result, the processing requires a maximum of ~60 service threads from webMethods I.S.

The above scenario will result in the System Threads (Server -> Statistics) increase to ~240 something. And the System threads will stay at ~240 even after all processings completed.

Depends on the X12 EDI transactions, these 'new' threads also consume certain amount of 'free' memory (Server -> Statistics -> Free Memory) and reduce the memory available.

Is there any way for webMethods to re-claim those threads ??? In addition, should we set the Min / Max System Thread pool no. to
something like 200/300 ?

[griffima]

Stephen,
Not sure what OS you are on but the server stats page is not incredibly accurate. esp thread usage. More than likely those threads are dead. The memory will get reclaimed as needed when the garbage collector runs which can be whenever. If you are on Solaris 8 you can bind the individual threads in java to the corresponding OS threads that actually run (LWP's in Solaris terms). You can then look at the OS level to see the actual number of threads in use.

Unless you are getting low thread warnings from webMethods and or running out of memory you should be okay. If you are then bumping up the threads and JVM size would be the next step.

You can use the java RunTime class to see how much memory is really being used if you want. A simple webMethods java service calling the Runtime methods totalMemory and freeMemory will let you see how you are doing.

markg
http://darth.homelinux.net