PaaS Partner Community

Handle locked rows by DB Adapters for distributed Polling technologies in OSB 12c by Chris Laurente

Juergen Kress
PaaS Partner Adoption


In this post, we will learn some ways to handle a database row that is locked by a Database Adapter with Distributed polling capablity in OSB 12c. There we go:


Sometimes, when we work with Database adapters with distributed polling we are struggling to update the same polled row in the respective pipeline because, basically, the polled row is locked with the option “FOR UPDATE SKIP LOCKED” and it will be released when the process finishes or if an error occurs. But, what happen if we want to update the same polled row, let see for example the status description of the process or some error messages. So, I would like to show you some ways to handle these cases.

1.- Using JMS resources

If we could handle more resources like for example Topics or queues then we would be able to send the polled row to these resources and process them after the poller was released, so it would be useful if we want to release the polled row as soon as we want.

In this case we will create a topic and we will specify the Messaging request as the request of the DB Poller, the column to read and write is called POLLER_READ from 0(READY) to 1(DONE). Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.