JMS Adaptor Notifications and Context Management

We are using the webMethods JMS adapter with IBM’s MQ Series (with a JMS plugin) as the JMS provider (no webMethods Broker running, just IS). It seems like there are a lot of issues with transaction management. When a service is invoked by a notifier, it seems you cannot use explicit transaction management (I’m guessing the notifier has its own transaction context already started when it invokes the service). Although we are being careful not to mix explicit and implict transaction management, we still see significant issues. For example, a notifier triggers a service that simply makes a call to an adapter service to translate the JMS message into a document (the JMS connection is set to use LOCAL_TRANSACTION), and all of the transaction context handling is implicit. Although this service returns successfully (we even hard-coded in an EXIT with success to test if we were missing something), the adapter thinks something has crapped out and attempts to rollback the transaction. Has anyone else run into this? We can’t use the MQSeries adapter, so that won’t be the solution. (BTW - this all works fine with transaction type set to NO_TRANSACTION, but we don’t want that).

Thanks for any help…