IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
Back to discussions
Expand all | Collapse all

Mercserv initialising a thread for every tux call

  • 1.  Mercserv initialising a thread for every tux call

    Posted 10/20/04 01:32 AM

    Originally posted by: SystemAdmin


    When a tux call is made from a map a tread is initialised like it should..... and then goes to sleep. The next call to the map (requiring another tux call) initiates another tread and the next call initiates another tread..... and so it carries on.

    The problem is that the old treads are never terminated, it stays in sleep mode. You have to shutdown the mercserv to terminate those threads. With the creation of a new tread every time without terminating the old ones we get to the max threads limit set on OS level, then no other process are allowed to fork.

    Why are the treads just going into sleep mode? Is it waiting for something to happen which we are not aware of? How do we get around this problem? Is there some configuration setting we must change?
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


Related Content