TopLink issue on Bpel 10.1.3.3

We are having an issue with the bpel flow on Bpel 10.1.3.3 where when it is inserting into the database, not all of the fields are saving to the database.Several of the fields are being stored as null in the database although there are values
that should be saved. I deployed the flow on both Bpel 10.1.2 and Bpel 10.1.3.3 which have same database connection. Bpel 10.1.2 has no problem. My flow is created by Bpel 10.1.2 designer. I also use JDveloper 10.1.3.3 to migrate the flow and then deploy it on Bpel 10.1.3.3. However, I am still facing an issue on Bpel 10.1.3.3.
The data being inserted to database which I saw it from Bpel console.
<description>CAR-47511-000073*EBS.01088</description>
<exchangeRateType>ALEXTEST</exchangeRateType>
<invoiceAmount>4086.82</invoiceAmount>
<invoiceCurrencyCode>USD</invoiceCurrencyCode>
<invoiceDate>2006-03-20T08:00:00</invoiceDate>
<invoiceId/>
<invoiceNum>ALEX-000002|EBS.000002</invoiceNum>
<orgId>204</orgId>
<invoiceTypeLookupCode>STANDARD</invoiceTypeLookupCode>
<source>TRANSPORTATION MANAGEMENT</source>
<vendorId>3932</vendorId>
<vendorSiteId>4646</vendorSiteId>
However, only invoice id, source, vendor id, vendor site id are inserted into dabase. All others are nulls.
Any idea? thanks !!

To complement information:
1/ Zoom in doesn't have this issue:
both Ctrl + Numpad + and Ctrl + = are working
On AZERTY keyboard = and + are on same key.
2/ When using Ctrl + Numpad - , I observe same behaviour as Ctrl + 6 (opens a box to comment)...
Can you at least fix Ctrl + Numpad - for zoom out?
(this won't be unversal but will at leas save 90% of the issues)

Similar Messages

  • Performance issues in BPEL

    We are having an integration wherein the messages coming via b2b are being passed on to the bpel process for further processing..
    When we are testing with about 500 transactions means 500 separate files each having one transaction in it ..one ST SE transaction data block in it only about 10 transactions are being processed in parallel by the bpel process...while the remaining transactions go into the manual recovery queue.
    so at a time only about 10 bpel instances are getting created and then once few of these transactions get completely processed by the bpel process..slowly the transactions from the Manual Recovery Queue gets assigned to a new bpel instance..means a new bpel instances get created..
    we are expecting a load of about 16000 transactions for the entire day and the concern here is that we need all of these b2b transactions to be processed by the bpel process in about 5 to 6 hours...is it possible in any way that we change the configuration setting such that more number of parallel bpel instances could be trigerred at the same time so that this could increase the processing speed on the bpel side.
    Could someone please help us out with this slowness issue in bpel.
    thanks

    Have a look at this doc
    http://www.oracle.com/technology/tech/soa/soa-suite-best-practices/soa_best_practices_1013x_drop1.pdf
    The section on threading should answer you question. You need to set the dspMaxThreads property to the appropraite level for your environment. Make sure your hardware is able to cope.
    cheers
    James

  • Toplink issues select distinct type query before fetch

    When we have type classifiers identified by value, Toplink issues a 'SELECT DISTINCT TYPE' on the parent object and then queries the child records for that type, is there way to avoid the select distinct
    type query from Toplink in queries, this is slowing down the query performance. thanks

    More info
    This is the Report Query:
    Session session = PersistenceFactory.newSession();
    ExpressionBuilder eb = new ExpressionBuilder();
    ReportQuery query = new ReportQuery( eb );
    query.setReferenceClass( FXSingleLegDealC.class );
    query.useCollectionClass( ArrayList.class );
    query.setSelectionCriteria( eb.get( "objectID" ).equal( 249994 ) );
    query.addAttribute( "objectID", eb.get( "objectID" ) );
    query.addAttribute( "parentDealFXDealLegCurrency1Amount", eb.get( "dealFXSingleLegParent" ).get( "fxDealLeg" ).get( "currency1Amount" ) );
    query.addAttribute( "parentDealFXDealLegCurrency1Amount", eb.get( "dealFXSingleLegParent" ).get( "fxDealLeg" ).get( "currency2Amount" ) );
    query.addAttribute( "parentDealFXDealLegCurrency1Amount", eb.get( "dealFXSingleLegParent" ).get( "fxDealLeg" ).get( "currency1" ).get( NamedEntity.ShortName) );
    query.addAttribute( "parentDealFXDealLegCurrency1Amount", eb.get( "dealFXSingleLegParent" ).get( "counterpartyA" ).get( NamedEntity.ShortName) );
    ArrayList result = ( ArrayList ) session.executeQuery( query );
    This is the SQL Generated:
    SELECT t0.id, t1.ccy1Amt, t1.ccy2Amt, t2.shortName, t3.shortName FROM IdcCpty t3, IdcInstr t2, IdcDeal t1, IdcDeal t0
    WHERE (((t0.id = ?) AND (t0.type = ?)) AND ((((t1.id = t0.parentId) AND (t1.type = ?)) AND ((t2.id = t1.ccy1Id) AND (t2.type = ?))) AND ((t3.id = t1.cptyAId) AND (t3.type = ?))))
    bind => [249994, IdcFXSLegDealC, IdcFXSLegDealC, IdcCrncC, IdcLglEntC]
    Not sure why we need to query for type on t2 and t3 after we have made a join by id (t2.id = t1.ccy1Id,t3.id = t1.cptyAId), this is really breaking our performance, we do not want to add an index on
    the type column
    can someone please respond!?

  • Toplink Exception in BPEL process

    Hi All,
    We get the attached error while running a BPEL process which uses a DBAdapter (which uses Toplink under the covers). Can you provide any pointers on why this exception might be happening.
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.
    at
    oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:310)
    at
    oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:174)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.acquireClientSession(DBManagedConnectionFactory.java:512)
    at oracle.tip.adapter.db.DBManagedConnection.getSession(DBManagedConnection.java:208)
    at oracle.tip.adapter.db.transaction.DBCciLocalTransaction.getSession(DBCciLocalTransaction.java:149)
    at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:143)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:528)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:164)
    at
    oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452)
    at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.expire(BPELInvokeWMP.java:120)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:3868)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2228)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
    at
    IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
    at
    com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
    at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
    at
    com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:568)
    Caused by: Exception [TOPLINK-4002] (OracleAS TopLink - 10g
    (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433
    at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:221)
    at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:105)
    at oracle.toplink.sessions.DatabaseLogin.connect(DatabaseLogin.java:218)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(DatabaseAccessor.java:398)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(DatabaseAccessor.java:423)
    at oracle.toplink.threetier.ConnectionPool.buildConnection(ConnectionPool.java:90)
    at oracle.toplink.threetier.ExternalConnectionPool.startUp(ExternalConnectionPool.java:114)
    at oracle.toplink.threetier.ServerSession.connect(ServerSession.java:447)
    at oracle.toplink.publicinterface.DatabaseSession.login(DatabaseSession.java:531)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:648)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.acquireClientSession(DBManagedConnectionFactory.java:329)
    ... 26 more
    Caused by: java.sql.SQLException: invalid arguments in call
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java(Compiled
    Code))
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:239)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:205)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
    at com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:160)
    at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:100)
    ... 35 more
    <2007-05-22 12:47:15,075> <ERROR> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Rolling back JCA LocalTransaction
    <2007-05-22 12:47:15,075> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Marking this exception as Retriable
    <2007-05-22 12:47:15,076> <DEBUG> <default.collaxa.cube.ws>
    <WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException:
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - WSIF JCA Execute of operation 'ReceiveRequest' failed due
    to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    ; nested exception is:
    ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need
    to configure the connection settings in the deployment descriptor
    (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml)
    and restart the server. Caused by Exception [TOPLINK-4002]
    (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
    oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.
    at
    oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:570)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452)
    at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.expire(BPELInvokeWMP.java:120)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:3868)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2228)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
    at
    IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
    at
    com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
    at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
    at
    com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:568)
    Caused by: ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need
    to configure the connection settings in the deployment descriptor
    (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml)
    and restart the server. Caused by Exception [TOPLINK-4002]
    (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
    oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.
    at
    oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:310)
    at
    oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:174)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.acquireClientSession(DBManagedConnectionFactory.java:512)
    at oracle.tip.adapter.db.DBManagedConnection.getSession(DBManagedConnection.java:208)
    at oracle.tip.adapter.db.transaction.DBCciLocalTransaction.getSession(DBCciLocalTransaction.java:149)
    at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:143)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:528)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:164)
    at
    oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
    ... 20 more
    Caused by: Exception [TOPLINK-4002] (OracleAS TopLink - 10g
    (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433
    at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:221)
    at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:105)
    at oracle.toplink.sessions.DatabaseLogin.connect(DatabaseLogin.java:218)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(DatabaseAccessor.java:398)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(DatabaseAccessor.java:423)
    at oracle.toplink.threetier.ConnectionPool.buildConnection(ConnectionPool.java:90)
    at oracle.toplink.threetier.ExternalConnectionPool.startUp(ExternalConnectionPool.java:114)
    at oracle.toplink.threetier.ServerSession.connect(ServerSession.java:447)
    at oracle.toplink.publicinterface.DatabaseSession.login(DatabaseSession.java:531)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:648)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.acquireClientSession(DBManagedConnectionFactory.java:329)
    ... 26 more
    Caused by: java.sql.SQLException: invalid arguments in call
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java(Compiled
    Code))
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:239)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:205)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
    at com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:160)
    at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:100)
    ... 35 more
    <2007-05-22 12:47:15,082> <DEBUG> <default.collaxa.cube.ws>
    <WSIFInvocationHandler::invoke> Fault happened:
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - WSIF JCA Execute of operation 'ReceiveRequest' failed due
    to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    ; nested exception is:
    ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need
    to configure the connection settings in the deployment descriptor
    (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml)
    and restart the server. Caused by Exception [TOPLINK-4002]
    (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
    oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.
    <2007-05-22 12:47:16,119> <DEBUG> <default.collaxa.cube.ws>
    <WSInvocationManager::invoke> operation: ReceiveRequest,
    partnerLink: <partnerLink name="DBReceiveRequest"
    partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/db/ReceiveRequest/}ReceiveRequest_plt">
    <myRole name="null">
    <ServiceName>null</ServiceName>
    <PortType>null</PortType>
    <Address>null</Address>
    </myRole>
    <partnerRole name="ReceiveRequest_role">
    <ServiceName>{http://xmlns.oracle.com/pcbpel/adapter/db/ReceiveRequest/}ReceiveRequest</ServiceName>
    <PortType>{http://xmlns.oracle.com/pcbpel/adapter/db/ReceiveRequest/}ReceiveRequest_ptt</PortType>
    <Address>null</Address>
    </partnerRole>
    <conversationId>bpel://localhost/default/BPEL_XXP4UHRADRV~1.0/601-BpInv1-BpSeq2.6-1</conversationId>
    <properties>{}</properties>
    </partnerLink>
    <2007-05-22 12:47:16,120> <DEBUG> <default.collaxa.cube.ws>
    <WSInvocationManager::invoke> def is
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    <2007-05-22 12:47:16,120> <DEBUG> <default.collaxa.cube.ws>
    <WSIFInvocationHandler::invoke> opName=ReceiveRequest,
    parnterLink=<partnerLink name="DBReceiveRequest"
    partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/db/ReceiveRequest/}ReceiveRequest_plt">
    <myRole name="null">
    <ServiceName>null</ServiceName>
    <PortType>null</PortType>
    <Address>null</Address>
    </myRole>
    <partnerRole name="ReceiveRequest_role">
    <ServiceName>{http://xmlns.oracle.com/pcbpel/adapter/db/ReceiveRequest/}ReceiveRequest</ServiceName>
    <PortType>{http://xmlns.oracle.com/pcbpel/adapter/db/ReceiveRequest/}ReceiveRequest_ptt</PortType>
    <Address>null</Address>
    </partnerRole>
    <conversationId>bpel://localhost/default/BPEL_XXP4UHRADRV~1.0/601-BpInv1-BpSeq2.6-1</conversationId>
    <properties>{}</properties>
    </partnerLink>
    <2007-05-22 12:47:16,120> <DEBUG> <default.collaxa.cube.ws>
    <WSIFInvocationHandler::doShortCut> Parner Property optShortCut
    <2007-05-22 12:47:16,126> <INFO> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Using JCA Connection Pool - max size = <unbounded>
    <2007-05-22 12:47:16,127> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Looking up Resource Adapter JDNI location 'eis/DB/APPS'
    <2007-05-22 12:47:16,127> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound> Instantiating outbound JCA
    interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
    <2007-05-22 12:47:16,127> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound> Populating outbound JCA interactionSpec
    oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with
    properties: {ProcedureName=DEQ_REQ_MSG, PackageName=XXP4U_HRADRV_BPEL_PKG,
    SchemaName=APPS}
    <2007-05-22 12:47:16,139> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - No XMLRecord headers provided
    <2007-05-22 12:47:16,139> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Starting JCA LocalTransaction
    <2007-05-22 12:47:16,139> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Invoking JCA outbound Interaction
    <2007-05-22 12:47:16,154> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.DBManagedConnectionFactory
    createServerSession> create a new ServerSession
    <2007-05-22 12:47:16,155> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.DBManagedConnectionFactory
    createServerSession> The platform class name was specified as:
    oracle.toplink.internal.databaseaccess.Oracle9Platform
    <2007-05-22 12:47:16,156> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.DBManagedConnectionFactory
    createServerSession> Using an app server connection pool. DataSource name is jdbc/OracleHRAppsDataSourceDS
    <2007-05-22 12:47:16,158> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger
    log> TopLink, version: OracleAS TopLink - 10g (9.0.4.5) (Build
    040930)
    <2007-05-22 12:47:16,159> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger
    log> connecting session: Not named
    <2007-05-22 12:47:16,159> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger
    log> connecting(DatabaseLogin(
    platform=>Oracle9Platform
    datasource name=>jdbc/OracleHRAppsDataSourceDS
    <2007-05-22 12:47:16,161> <ERROR> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.DBManagedConnectionFactory
    acquireClientSession> unable to build the TopLink Session
    <2007-05-22 12:47:16,162> <DEBUG> <default.collaxa.cube.ws>
    <Database Adapter::Outbound> <oracle.tip.adapter.db.DBManagedConnectionFactory
    acquireClientSession>
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433
    <2007-05-22 12:47:16,165> <ERROR> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Could not invoke operation 'ReceiveRequest' against the
    'Database Adapter' due to:
    ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need
    to configure the connection settings in the deployment descriptor
    (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml)
    and restart the server. Caused by Exception [TOPLINK-4002]
    (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
    oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.
    at
    oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:310)
    at
    oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:174)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.acquireClientSession(DBManagedConnectionFactory.java:512)
    at oracle.tip.adapter.db.DBManagedConnection.getSession(DBManagedConnection.java:208)
    at oracle.tip.adapter.db.transaction.DBCciLocalTransaction.getSession(DBCciLocalTransaction.java:149)
    at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:143)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:528)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:164)
    at
    oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452)
    at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.expire(BPELInvokeWMP.java:120)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:3868)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2228)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
    at
    IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
    at
    com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
    at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
    at
    com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:568)
    Caused by: Exception [TOPLINK-4002] (OracleAS TopLink - 10g
    (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433
    at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:221)
    at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:105)
    at oracle.toplink.sessions.DatabaseLogin.connect(DatabaseLogin.java:218)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(DatabaseAccessor.java:398)
    at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(DatabaseAccessor.java:423)
    at oracle.toplink.threetier.ConnectionPool.buildConnection(ConnectionPool.java:90)
    at oracle.toplink.threetier.ExternalConnectionPool.startUp(ExternalConnectionPool.java:114)
    at oracle.toplink.threetier.ServerSession.connect(ServerSession.java:447)
    at oracle.toplink.publicinterface.DatabaseSession.login(DatabaseSession.java:531)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:648)
    at
    oracle.tip.adapter.db.DBManagedConnectionFactory.acquireClientSession(DBManagedConnectionFactory.java:329)
    ... 26 more
    Caused by: java.sql.SQLException: invalid arguments in call
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java(Compiled
    Code))
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:239)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:205)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
    at com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:160)
    at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:100)
    ... 35 more
    <2007-05-22 12:47:16,165> <ERROR> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Rolling back JCA LocalTransaction
    <2007-05-22 12:47:16,165> <DEBUG> <default.collaxa.cube.ws>
    <AdapterFramework::Outbound>
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - Marking this exception as Retriable
    <2007-05-22 12:47:16,165> <DEBUG> <default.collaxa.cube.ws>
    <WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException:
    file:/oracle/crp1/BPEL/integration/orabpel/domains/default/tmp/.bpel_BPEL_XXP4UHRADRV_1.0.jar/ReceiveRequest.wsdl
    [ ReceiveRequest_ptt::ReceiveRequest(InputParameters,OutputParameters)
    ] - WSIF JCA Execute of operation 'ReceiveRequest' failed due
    to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    ; nested exception is:
    ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need
    to configure the connection settings in the deployment descriptor
    (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml)
    and restart the server. Caused by Exception [TOPLINK-4002]
    (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
    oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.
    at
    oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:570)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452)
    at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.expire(BPELInvokeWMP.java:120)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:3868)
    at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2228)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
    at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
    at
    IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
    at
    com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
    at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
    at
    com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:568)
    Caused by: ORABPEL-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    See root exception for the specific exception. You may need
    to configure the connection settings in the deployment descriptor
    (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml)
    and restart the server. Caused by Exception [TOPLINK-4002]
    (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
    oracle.toplink.exceptions.DatabaseException
    Exception Description: java.sql.SQLException: invalid arguments
    in call
    Internal Exception: java.sql.SQLException: invalid arguments
    in call
    Error Code: 17433.

    It looks like you are not providing a username or password in your DataSource.

  • Java.lang.RuntimeException: failed to compile execlets (JAVA embeding issue in BPEL 2.0)

    HI i was trying to use java code in BPEL 2.0 by using java Embedding. while deploying the application getting the error.
    even after importing the corrsponding class
    below is the code snippet for the same :
    <import location="oracle.soa.management.facade.Locator"
         importType="http://schemas.oracle.com/bpel/extension/java"/>
         <import location="oracle.soa.management.facade.LocatorFactory"
         importType="http://schemas.oracle.com/bpel/extension/java"/>
         <import location="oracle.soa.management.facade.Component"
         importType="http://schemas.oracle.com/bpel/extension/java"/>
    <extensionActivity>
          <bpelx:exec name="Java_Embedding1" language="java">
            <![CDATA[Locator locator = LocatorFactory.createLocator();    
    String compositeRevision = (String)getVariableData("compositeRevision");  
    String compositeNameRevision = "ASG/ImportCustomerData!"+ compositeRevision; 
    Composite prowessCustomerComposite = (Composite)locator.lookupComposite(compositeNameRevision);   
    CompositeInstanceFilter filter = new CompositeInstanceFilter();    
    filter.setState(CompositeInstance.STATE_RUNNING);]]>
          </bpelx:exec>
        </extensionActivity>
    while deploying gettting below error.
    06:18:58 PM] Error deploying archive sca_ImportCutomerData_rev1.0.jar to partition "default" on server AdminServer [http://LTRTHIPIREDDY.keste.com:7001]
    [06:18:58 PM] HTTP error code returned [500]
    [06:18:58 PM] Error message from server:
    There was an error deploying the composite on AdminServer: Deployment Failed: Error occurred during deployment of component: importCustomerData_BPEL to service engine: implementation.bpel, for composite: ImportCutomerData: ORABPEL-05250
    Error deploying BPEL suitcase.
    error while attempting to deploy the BPEL component file "E:\Oracle\Middleware\user_projects\domains\Raja_domain\servers\AdminServer\dc\soa_3ca99378-812f-460f-9760-d19a15c0ef44"; the exception reported is: java.lang.RuntimeException: failed to compile execlets of importCustomerData_BPEL
    This error contained an exception thrown by the underlying deployment module.
    Verify the exception trace in the log (with logging level set to debug mode).
    [06:18:58 PM] Check server log for more details.
    [06:18:58 PM] Error deploying archive sca_ImportCutomerData_rev1.0.jar to partition "default" on server AdminServer [http://LTRTHIPIREDDY.keste.com:7001]
    [06:18:58 PM] ####  Deployment incomplete.  ####
    [06:18:58 PM] Error deploying archive file:/C:/JDeveloper/mywork_Arbonne/CustomerInboundApp/ImportCutomerData/deploy/sca_ImportCutomerData_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Thanks in Advance...
    rajashekar

    Hi have solved the issue by importing the  class file.
    <import location="oracle.soa.management.facade.Locator"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.facade.LocatorFactory"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.facade.Composite"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="java.util.List"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.util.CompositeInstanceFilter"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.facade.CompositeInstance"
              importType="http://schemas.oracle.com/bpel/extension/java"/>

  • Rollback Issue in BPEL

    Hi All,
    I am facing issue with Txn rollback in BPEL while using fault policies.My BPEL polls JMS Q and  invokes 2 databases and 1 jms adapter in a sequential manner. I want if any invocation fails , the preceding successful invocations should be rollbacked and txn should be retried as per the source jms q retry settings .I have worked on it using 2 approaches-
    1. Without using Fault Policy- I created a catchall and added a throw activity with rollback fault in it. So if any invocation fails, the rollback and retry is working fine as per the source Q retry settings.
    2.With Fault Policy- I created a fault policy and fault binding(composite/reference level).Also I created a catchall and added a throw activity with rollback fault in it.When any invocation fails, the fault policy is called, and the Ora:retry action executes and retry calling the failed adapter as per the retry configuration set in the policy file. If after all retries, still invocation fails, then transaction goes to CatchAll block.Here is the problem.The transaction is not getting rollbacked and does not even retry as per the JMS Q retry configuration.
    My agenda is to have a process, where in if any invocation fails, that should be retried as per fault policy retry configuration.If still invocation is faulted after all retries, the preceding invocations should be rollbacked and the message should be rollbacked to source jms Q. Again bpel should be instantiated with new transaction. Each instance should itself retry as per fault policy retry configuration.It should keep on retrying(creating new instances) till source Q jms retry limit is achieved.
    Please help..
    Thanks
    Rishu

    Hi Ananth,
    Thanks for your reply.
    I am using fault policies for Error handling in all my interfaces instead of handling the faults using the catch block.So the same approach I need to follow in this interface as well , where I am facing the issue. In my affected interface, I have 3 invocations in sequence manner and want that If any invocation fails, the earlier successful transactions should be rollbacked.So when I am using fault policy, the failed invocation is getting retried as per the fault policy retry , but it is not rollbacking the earlier 2 successful invocations, which it should do to have an effective error handling. Same is getting accomplished by using Catch and throwing rollback error from there. I am ok even if Q retry should not get executed but I need to rollback the previous successfully executed invocations.Could you please let me know how to handle this scenario using fault policy..May be I am skipping something then..
    Thanks and Regards,
    Rishu Sharma

  • Spring JPA + Toplink Issues

    Heya,
    I followed a developer works tutorial on integrating Toplink with Spring, and everything seemed to go well, when I start up the application, it looks like Toplink finds all my annotations and validates them (if any where invalid, it sure lets me know). However, when I go to persist my object, I get an IllegalArgumentException:
    Caused by: java.lang.IllegalArgumentException: Object: au.gov.nla.aons2.registry.domain.Registry@f3b83 is not a known entity type.
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:3198)
         at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerImpl.persist(EntityManagerImpl.java:190)
         at org.springframework.orm.jpa.JpaTemplate$5.doInJpa(JpaTemplate.java:263)
         at org.springframework.orm.jpa.JpaTemplate.execute(JpaTemplate.java:191)
    My Registry should be valid; at first I thought it was something to do with class hierarchies, but I removed that from the equation and I'm still getting the error. My class looks like this:
    @Entity
    @Table(name="registry", uniqueConstraints= {@UniqueConstraint(columnNames={"name"})})
    public class Registry implements Serializable {
    private static final long serialVersionUID = -4335133039987702902L;
    @Id
    private Long id;
    private String name;
    @Temporal(TemporalType.TIMESTAMP)
         private Calendar lastRun;
    private String url;
    @OneToOne(cascade=CascadeType.ALL)
    @PrimaryKeyJoinColumn
         private Schedule schedule;
         private String status = ScheduleStatus.IDLE;
         public Long getId() {
              return id;
         public void setId(Long id) {
              this.id = id;
         public Calendar getLastRun() {
              return lastRun;
         public void setLastRun(Calendar lastRun) {
              this.lastRun = lastRun;
         public String getName() {
              return name;
         public void setName(String name) {
              this.name = name;
    @Transient
         public String getType()
    throw new RuntimeException("this should be overridden.");
         public String getUrl() {
              return url;
         public void setUrl(String url) {
              this.url = url;
         public Schedule getSchedule() {
              return schedule;
         public void setSchedule(Schedule schedule) {
              this.schedule = schedule;
         public String getStatus() {
              return status;
         public void setStatus(String status) {
              this.status = status;
    My Spring config looks like this:
         <bean id="entityManagerFactory"
              class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
              <property name="jpaVendorAdapter">
                   <bean
                        class="org.springframework.orm.jpa.vendor.TopLinkJpaVendorAdapter">
                        <property name="generateDdl" value="true" />
                        <property name="showSql" value="true" />
                        <property name="databasePlatform"
                             value="oracle.toplink.essentials.platform.database.HSQLPlatform" />
                   </bean>
              </property>
              <property name="dataSource" ref="dataSource" />
              <property name="loadTimeWeaver">
                   <bean
                        class="org.springframework.instrument.classloading.SimpleLoadTimeWeaver" />
              </property>
         </bean>
    My persistence.xml looks like this:
    <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
         <persistence-unit name="aons" transaction-type="RESOURCE_LOCAL">
         </persistence-unit>
    </persistence>
    Finally, and here's the really odd part, my log displays the registering of the Registry Class as a persistence object:
    [TopLink Config]: 2007.04.17 09:32:50.874--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.registry.domain.LcDfwRegistry] is being defaulted to: LcDfwRegistry.
    [TopLink Config]: 2007.04.17 09:32:50.890--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.registry.domain.Registry] is being defaulted to: Registry.
    [TopLink Config]: 2007.04.17 09:32:50.921--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Long au.gov.nla.aons2.registry.domain.Registry.id] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:50.937--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.String au.gov.nla.aons2.registry.domain.Registry.name] is being defaulted to: NAME.
    [TopLink Config]: 2007.04.17 09:32:50.952--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.util.Calendar au.gov.nla.aons2.registry.domain.Registry.lastRun] is being defaulted to: LASTRUN.
    [TopLink Config]: 2007.04.17 09:32:50.952--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.String au.gov.nla.aons2.registry.domain.Registry.url] is being defaulted to: URL.
    [TopLink Config]: 2007.04.17 09:32:50.983--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.String au.gov.nla.aons2.registry.domain.Registry.status] is being defaulted to: STATUS.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The discriminator column name for the root inheritance class [class au.gov.nla.aons2.registry.domain.Registry] is being defaulted to: DTYPE.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.schedule.domain.DayOfMonth] is being defaulted to: DayOfMonth.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The table name for entity [class au.gov.nla.aons2.schedule.domain.DayOfMonth] is being defaulted to: DAYOFMONTH.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Long au.gov.nla.aons2.schedule.domain.DayOfMonth.id] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Integer au.gov.nla.aons2.schedule.domain.DayOfMonth.dayOfMonth] is being defaulted to: DAYOFMONTH.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.registry.domain.GdfrRegistry] is being defaulted to: GdfrRegistry.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.registry.domain.PronomRegistry] is being defaulted to: PronomRegistry.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.schedule.domain.Schedule] is being defaulted to: Schedule.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The table name for entity [class au.gov.nla.aons2.schedule.domain.Schedule] is being defaulted to: SCHEDULE.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Long au.gov.nla.aons2.schedule.domain.Schedule.id] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.String au.gov.nla.aons2.schedule.domain.Schedule.scheduleType] is being defaulted to: SCHEDULETYPE.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Integer au.gov.nla.aons2.schedule.domain.Schedule.hour] is being defaulted to: HOUR.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Integer au.gov.nla.aons2.schedule.domain.Schedule.minutes] is being defaulted to: MINUTES.
    [TopLink Config]: 2007.04.17 09:32:50.999--ServerSession(21324485)--Thread(Thread[main,5,main])--Element [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to a one to many mapping.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--Element [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to a one to many mapping.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.String au.gov.nla.aons2.schedule.domain.Schedule.descriptiveString] is being defaulted to: DESCRIPTIVESTRING.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--The alias name for the entity class [class au.gov.nla.aons2.schedule.domain.Weekday] is being defaulted to: Weekday.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--The table name for entity [class au.gov.nla.aons2.schedule.domain.Weekday] is being defaulted to: WEEKDAY.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.Long au.gov.nla.aons2.schedule.domain.Weekday.id] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--The column name for element [private java.lang.String au.gov.nla.aons2.schedule.domain.Weekday.name] is being defaulted to: NAME.
    [TopLink Config]: 2007.04.17 09:32:51.015--ServerSession(21324485)--Thread(Thread[main,5,main])--The target entity (reference) class for the one to one mapping element [private au.gov.nla.aons2.schedule.domain.Schedule au.gov.nla.aons2.registry.domain.Registry.schedule] is being defaulted to: class au.gov.nla.aons2.schedule.domain.Schedule.
    [TopLink Config]: 2007.04.17 09:32:51.108--ServerSession(21324485)--Thread(Thread[main,5,main])--The primary key column name for the mapping element [private au.gov.nla.aons2.schedule.domain.Schedule au.gov.nla.aons2.registry.domain.Registry.schedule] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.108--ServerSession(21324485)--Thread(Thread[main,5,main])--The foreign key column name for the mapping element [private au.gov.nla.aons2.schedule.domain.Schedule au.gov.nla.aons2.registry.domain.Registry.schedule] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.108--ServerSession(21324485)--Thread(Thread[main,5,main])--The target entity (reference) class for the one to many mapping element [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to: class au.gov.nla.aons2.schedule.domain.DayOfMonth.
    [TopLink Config]: 2007.04.17 09:32:51.155--ServerSession(21324485)--Thread(Thread[main,5,main])--The join table name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to: SCHEDULE_DAYOFMONTH.
    [TopLink Config]: 2007.04.17 09:32:51.155--ServerSession(21324485)--Thread(Thread[main,5,main])--The source primary key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.155--ServerSession(21324485)--Thread(Thread[main,5,main])--The source foreign key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to: Schedule_ID.
    [TopLink Config]: 2007.04.17 09:32:51.155--ServerSession(21324485)--Thread(Thread[main,5,main])--The target primary key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The target foreign key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.daysOfMonth] is being defaulted to: daysOfMonth_ID.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The target entity (reference) class for the one to many mapping element [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to: class au.gov.nla.aons2.schedule.domain.Weekday.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The join table name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to: SCHEDULE_WEEKDAY.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The source primary key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The source foreign key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to: Schedule_ID.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The target primary key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to: ID.
    [TopLink Config]: 2007.04.17 09:32:51.171--ServerSession(21324485)--Thread(Thread[main,5,main])--The target foreign key column name for the many to many mapping [private java.util.List au.gov.nla.aons2.schedule.domain.Schedule.weekdays] is being defaulted to: weekdays_ID.
    I really don't get it... I think I'm going to have a look at the source and see if I can figure it out. Apart from this problem, I was really enjoying JPA;P

    Okay, I think I've found the problem, but don't know what is causing it. When my code attempts to persist my object, it fails on the Class.equals method. For some reason (classloaders I'll bet), there are two instances of the Class Registry, with two different object ids - so when it calls:
    // Optimize descriptor lookup through caching the last one accessed.
    ClassDescriptor lastDescriptor = this.lastDescriptorAccessed;
    if ((lastDescriptor != null) && (lastDescriptor.getJavaClass().equals(theClass))) {
    return lastDescriptor;
    And should match, the Class.equals() fails:
    public boolean equals(Object obj) {
         return (this == obj);
    So... what now, if it is a class loading issue, how do I ensure that there is only one copy of the Registry class object instantiated. If it isn't a class loading issue, what else could it be?

  • Ref:Siebel webservice calling issue in Bpel

    Hi,
    Hope you are doing good. Kindly share you valuable ideas regards below issue please.
    I have developed one mediator with 4 Operations namely 1). InsertOrUpdateContactSSM Operation
    2).UpdateContact Operation
    3). UpdateContact Operations
    4).QueryByIdContact Operation.
    I have created 4 BPEL process's for above 4 Operations. Here my SOA suite version is 11.1.1.6.
    I have invoking one Siebel webservice, In this webservice having above operation defined.
    It's developed, it's complied without error and i have deployed into my SOA server it's deployed successfully.
    At testing time it's throwing below :
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'InsertOrUpdateContactSSM' failed due to: *SOAP-ENV:Server, error code: There is no active Web Service with operation named &apos;http://www.absa.co.za/siebel/webservices:InsertOrUpdateContactSSM_Input&apos;.(SBL-EAI-04313)".* The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    Any one can give proved solution for above error. It's bit Urgent.
    Thanks in Advance.
    regards
    Anil

    Follow the instructions mentioned at this blog to resolve "SBL-EAI-04313" Error
    http://www.soastation.org/2007/05/troubleshooting-siebel-web-services-no.html
    Here is the another link with screen shots:
    https://blogs.oracle.com/pt/entry/siebel_web_service_invocation
    Mark the Posting appropriately as "helpful" or "Correct Answer", if your issue is solved.
    Edited by: 980644 on Feb 27, 2013 6:10 PM

  • Issue calling BPEL process in other domains

    I just moved my code from the development environment to test and I found an issue where the BPEL processes can't call one another if they reside in a different domain. There's no issue in calling a BPEL process from another BPEL process if they are in the same domain, but it just doesn't work if they are in different domains. The odd thing is that I'm not getting any errors either. I looked at the BPEL admin and everything seems to be consistent with what's in the development environment where everything works, so is there somewhere else I should look? thanks in advance.

    Are your domain names in lower case? There are several problems when using domain names which contain uppercase letters.
    Andre

  • An issue with BPEL fault handling

    Hi,
    I need to catch an exception in my BPEL process. The exception is thrown from a partner service(in java). I am using the catch fault handler in BPEL to catch a specific fault.
    1. When I give "systemFault" as the faultName its catching the fault
    2. But when I give "Exception" as the faultName its not catching the fault
    In the second case server log gives me the following fault,
    BPCOR-6135:A fault was not handled in the process scope; Fault Name is {......
    Can you please help me to figure out the problem here.
    Please let me know if you need any more information.
    Thanks in advance,
    Jose John

    Thank you very much for your reply.
    Following is the wsdl file,
    relevant part of the WSDL file
    <message name="Exception">
    <part name="fault" element="tns:Exception"/>
    </message>
    <portType name="PostConstraintChecker">
    <operation name="check">
    <input message="tns:check"/>
    <output message="tns:checkResponse"/>
    <fault message="tns:Exception" name="Exception"/>
    </operation>
    </portType>
    <binding name="PostConstraintCheckerPortBinding" type="tns:PostConstraintChecker">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="check">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal"/>
    </input>
    <output>
    <soap:body use="literal"/>
    </output>
    <fault name="Exception">
    <soap:fault name="Exception" use="literal"/>
    </fault>
    </operation>
    </binding>
    Is this correct? Do you see any problems in this? Please let me know if you need any more information which will help you in debugging the issue.
    Thanks,
    Jose John

  • Issue with BPEL append operation

    Hi All,
    I have the following block in my BPEL Code:
    <assign name="Assign_5">
    <bpelx:append>
    <bpelx:from variable="FFNUMTwoOutputClone"
    part="payload"
    query="/ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters/ns8:AddParameters/ns8:Parameter"/>
    <bpelx:to variable="decomposedOrder_OutputVariable"
    part="payload"
    query="/ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters/ns8:AddParameters"/>
    </bpelx:append>
    </assign>
    as far as I know, the ns8:Parameter should get appended to ns8:AddParameters. But during the execution of the process, the following selection failure is encountered:
    <selectionFailure xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
    -<part name="summary">
    <summary>
    Assign Operation Misuse.
    The selection result of /ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters/ns8:AddParameters is not an XML element; append operation cannot be performed.Please check the BPEL source at line number "347" .
    </summary>
    </part>
    </selectionFailure>
    Please suggest the cause and workaround for this issue as this is a very critical requirement.
    Regards,
    CC

    Hi,
    If you want to append to addparameters the query should be like this
    <assign name="Assign_5">
    <bpelx:insertAfter>
    <bpelx:from variable="FFNUMTwoOutputClone"
    part="payload"
    query="/ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters/ns8:AddParameters/ns8:Parameter"/>
    <bpelx:to variable="decomposedOrder_OutputVariable"
    part="payload"
    query="/ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters/ns8:AddParameters"/>
    </bpelx:insertAfter>
    </assign>
    Append operation actually appends as a child node to the node selected in bpelx:to part of append operation.
    or else u can use below code which gives the same result
    <assign name="Assign_5">
    <bpelx:append>
    <bpelx:from variable="FFNUMTwoOutputClone"
    part="payload"
    query="/ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters/ns8:AddParameters/ns8:Parameter"/>
    <bpelx:to variable="decomposedOrder_OutputVariable"
    part="payload"
    query="/ns8:FulfillmentOrderEBM/ns8:DataArea/ns8:FulfillmentOrder/ns8:FulfillmentOrderActions/ns8:FulfillmentAction/ns8:FulfillmentServices/ns8:FulfillmentService/ns8:ServiceParameters"/>
    </bpelx:append>
    </assign>

  • Issue with BPEL silent deinstall

    I'm using the BPEL shiphome for iAS phase 1 (linux). I have created a response file and successfully installed BPEL using the silent mode. However, when I try the silent deinstallation, I get the following error:
    Deinstall in progress (Mon Oct 17 06:59:49 PDT 2005)
    ERROR: Invalid action deinstallMiditer
    Usage: BPMInstaller installStandalone
    -oracle-home <oracleHome>
    -http-proxy-required true|false
    -http-proxy-host <proxyHost>
    -http-proxy-port <proxyPort>
    -http-no-proxy-for '<noProxyHosts>'
    I can successfully deinstall using OUI. So the issue is only with the silent mode of deinstallation. Please post your suggestions.
    Thanks,
    Karthik.

    Ronny , No where you can't install weblogic to start with uninstall again !
    just go with the option #1  if it is linux just rm directory should work otherwise delete the binaries, folders manually & environment variables
    thanks,
    Saichand

  • Issue with BPEL Correlation on Invoke 11g

    The scenario is like...
    One initial receive -> Invoke to a Web Service -> Receive from JMS Q -> End of the process.
    I have applied BPEL Correlation on Invoke by creating property alias with Output Message Type.Pattern I have also used.
    Now, when I run the composite, the instance is in error but no error message.
    On the other hand, if I use the Input message type for correlation property alias, the BPEL process proceeds. But my requirement is to do the correlation on output variable of invoke which needs to be checked against receive input variable.
    Can any one suggest some resolution here?
    Thanks.

    Hi,
    Here the option what I can think of is that use some unique element that you passing in first invoke for correlation and customize the external service to ask them to have your passed value as part of their queue values, That way you can correlate the messages and once correlated based on unique value you match up the tokens.
    Suggesting this work around as, correlation will always need token, which is passed as an input to the first Invoke. so defining correlation based on output token is not possible.
    If you find something please do share.
    -Umesh

  • Unified Timeout Issue in BPEL

    Hi all,
    We have two BPEL processess one ReqCS which is the "calling BPEL" and PS which is the "called BPEL". The called BPEL PS has a number of calls to database and wrappers. The problem is that the ReqCS BPEL which is calling the PS BPEL gets faulted. But the PS BPEL gets completed. We r getting the error Description as "Waiting for response has timedout. We tried changing the sycnMaxTime of the BPEL but it didnt help. PS has quiet a number of calls which makes the output XML as a huge one. We can see the output XML in the instance of the PS. But we couldnt see the instance of the ReqCS BPEL.
    Regards
    Prabhu
    Edited by: Prabhu on Mar 23, 2011 6:42 AM

    And Also this is working fine when the output xml is less sized.
    Regards
    Prabhu

  • TimeOut Issue in BPEL

    Hi all,
    We have two BPEL processess one ReqCS which is the "calling BPEL" and PS which is the "called BPEL". The called BPEL PS has a number of calls to database and wrappers. The problem is that the ReqCS BPEL which is calling the PS BPEL gets faulted. But the PS BPEL gets completed. We r getting the error Description as "Waiting for response has timedout. We tried changing the sycnMaxTime of the BPEL but it didnt help. PS has quiet a number of calls which makes the output XML as a huge one. We can see the output XML in the instance of the PS. But we couldnt see the instance of the ReqCS BPEL.But this is working fine when the PS BPEL XML is less size.
    Regards
    Prabhu

    And Also this is working fine when the output xml is less sized.
    Regards
    Prabhu

Maybe you are looking for