The adapter implementation typically uses Java Messaging Service (JMS) APIs and infrastructure. When an adapter is invoked, a JMS messsage gets sent to a JMS Queue. A Message Driven Bean (MDB) listening to this JMS Queue picks up the message, decodes it and exeutes the adapter. This method is inefficient and slow. Therefore, BP Server provides an option to overcome this limitation. If you select this option, then the adapter is executed in the same thread instead of using JMS infrastructure for adapter invocation.
