soa - prior blogpost-1

Issue: Recently I was working on Oracle SOA Orchestration Process and hit an issue where the instance of the process is was vanishing.

Resolution: The resolution was simple to just put the checkpoint() in the BPEL process make the idempotent activity to false at the Partnerlink. What this will do forcefully de-hydrate the instance so even if the failure occurs, partial success can still be viewed. All that need to happen is that the dehydration happens before the failure point.

However, when I digged deep, I figure out that it is happening because of the way Oracle SOA BPEL engine handles Transactions.

Most Oracle BPEL process starts with a new transaction and close out the transaction at the end of the process. However if there is a forceful dehydration, initial transaction get closed out and new transaction is started.

Observation / Question: With this thought and above explanation I noticed that it seems that the instance of the process won't appear in case the process has potential to be successful,  if the transaction timeout at the server / database level is less that response time of the BPEL process.

Any comments on this Observation / Question will be helpful.

Comments

Post a Comment

Popular posts from this blog

http vs https - prior blog

HTTP is an application layer protocol in the Internet Protocol Suite to transfer application data between client  and server.. It relies on the transport layer protocol primarily TCP but can use UDP as well to manage host - host communication. HTTP Client establishes a session with the server on a particular port which is usually 80. HTTP supports authentication schemes like Basic Authentication (cleartext username / password) and Digest Access Authentication (challenge response mechanisms) where server identifies and issues a challenge to the client before issuing the requested content. HTTP 1.1 additions: - Keep Alive parameter so that connection can be reused for more than one request. This lead to persistent connection, reduce latency as TCP 3-way handshake is not needed. - Chunked Transfer Encoding was introduced which allowed persistent connection to be streamed rather than buffered. - HTTP Pipelining: Allows client to send multiple requests before waiting for ...
Read more

service bus - prior blog

Overview In an ever evolving Integration Landspace, which started with CORBA / RPC based connectivity, then EAI tools which are more geared towards the Broker based centralised  controller, then with the advent of SOAP protocol and Service Oriented Architecture, ESBs enabled edge integrations. As REST got more popular and APIs enabling the responsive web front end, Mobile and cloud enabled applications, the role of esb has evolved to provide integration with the gateway layer and provide a framework for security & analytics around those APIs. Application Architecture Product: MULE  - Mule Application follows an event driven architecture enabled by connector layer in the form of message sources. - End To End Transaction processing is not possible as event messages are managed through difference resources in different scenarios like sequential queue processing, Servlets, async mail messages etc - Flows are composed of pre-packaged units of functionalities in the fo...
Read more