SOA/MULESOFT Middleware Practices

Hello Everyone , JBO Exception : JBO-28102 - A Request was timed out while waiting for a Resource Introduction :  In this post, I would like to explain you a generic JBO exception in Oracle ADF that throws an exception when there are no resources available to accommodate the new connection in the connection pool. In my project we have implemented a Web service using Oracle ADF SDO(Service Data Objects) to expose CRUD operations on the Business components. After the deployment in WebLogic server, we started observing the exceptions in server logs with the error message  "JBO-28102 - A Request was timed out while waiting for a Resource". This exception normally happens when there is no available resource to allocate new database connection.  To avoid such exceptions, there are options such as tuning connection pool configurations besides that, Below two other solutions that we have tried to resolve this issue, I believe any one of these will be useful for your us...

Introduction :  In Mule implementation, a common mistake while invoking Oracle's stored procedure is, incorrectly defining the order of IN/OUT parameters. These IN and OUT parameters data types and format should match with Oracle DB stored procedure's definition. Problem Statement :  I have recently come across a scenario, where I need to invoke Oracle's DB stored procedure from Mule with IN/OUT parameters. out of which couple of fields are having Date as datatype. During the invocation, there were some errors appeared which is little tricky to understand, however, the root cause was incorrect format of the input Date type parameter. I am taking a sample procedure and DB table mentioned below to illustrate the error scenarios with Oracle DB Procedure call and their possible solution. Database table structure : Oracle DB Procedure :  XX_TEST_CREATE_ORDER CREATE OR REPLACE PROCEDURE xx_test_create_order     i_orderid       IN NUMBER,   ...