This content has been marked as final. Show 3 replies
it is very difficult to help without any code for the dequeue part. Could you give some more informations ? What about
the dequeue options ?
I asked the question on the SOA board as well and it was answered. I forgot to come over here to close the question.
SOA does not use any code to dequeue, it is an adapter that listens on a queue. It turns out that the SOA environment was not set up with XA drivers, but the AQ adapter in SOA was defined using the xADataSourceName. When the setup for the adapter was changed to use the generic DataSourceName, the message dequeued correctly and was deleted from the table.