red_flanked_bluetail
New Member
Is the app server still single threaded now, please?
MultiThreaded AppServer?
- Thread starter red_flanked_bluetail
- Start date
Rob Fitzpatrick
ProgressTalk.com Sponsor
Your question is only tangentially related to the original post. In situations like this, please create a new discussion thread.
Progress has two different app servers. The old one, called OpenEdge Application Server, is implemented in the _proapsv executable, instantiated by a java unified broker. Now it is sometimes called "Classic App Server". It was discontinued in OpenEdge 12.0. The new one, called Progress Application Server for OpenEdge (PASOE), is implemented in the_mproapsv executable, instantiated by a tomcat broker. It exists in OpenEdge 11.5 and later.
In either case, a call to the application server executes some unit of ABL logic; perhaps a web service or some WebSpeed code. And in either case, a single application server can have multiple such calls being handled simultaneously in separate ABL runtime (aka "AVM") instances, each in its own OS thread. The difference in threading is that with the old app server, there is one AVM thread per _proapsv process. A broker may spawn multiple _proapsv processes, and later add or trim others, depending on demand and configuration. And if load-balancing is in use, there may even be multiple brokers for one service, on one or many machines.
With PASOE, a single _mproapsv process (aka Multi-Session App Server or MSAS) may host one or many ABL applications, each of which may have multiple AVM threads. And again, that number of threads can vary depending on configuration and demand.
The answer depends on what you mean by "app server" and what you mean by "single threaded".
Progress has two different app servers. The old one, called OpenEdge Application Server, is implemented in the _proapsv executable, instantiated by a java unified broker. Now it is sometimes called "Classic App Server". It was discontinued in OpenEdge 12.0. The new one, called Progress Application Server for OpenEdge (PASOE), is implemented in the_mproapsv executable, instantiated by a tomcat broker. It exists in OpenEdge 11.5 and later.
In either case, a call to the application server executes some unit of ABL logic; perhaps a web service or some WebSpeed code. And in either case, a single application server can have multiple such calls being handled simultaneously in separate ABL runtime (aka "AVM") instances, each in its own OS thread. The difference in threading is that with the old app server, there is one AVM thread per _proapsv process. A broker may spawn multiple _proapsv processes, and later add or trim others, depending on demand and configuration. And if load-balancing is in use, there may even be multiple brokers for one service, on one or many machines.
With PASOE, a single _mproapsv process (aka Multi-Session App Server or MSAS) may host one or many ABL applications, each of which may have multiple AVM threads. And again, that number of threads can vary depending on configuration and demand.
Thanks Rob - I've split it out into a new thread.