BPM Timeout

Hello,
I have a scenario in which SAP uses ABAP proxy to connect to XI synchronously. In XI I'm using sync-async BPM which has steps that make web service calls to an external system. My problem here is that some of the webservice calls take more than 60 seconds because of which a timeout error is sent back to SAP. XI continues to process the further steps without errors (as the processing time is set to be more than a minute) but in the end gets stuck not knowing whom to send the response back (as the response has already gone back to SAP).
Here I'm not sure what timeout parameter needs to be changed to allow SAP to keep waiting for a response from XI even if it goes beyond 60 secs.
Thanks

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true
do have a look

Similar Messages

  • BPM Start Process

    We have scenario(file to file) where we get multiple files and is merged using BPM, transformed and sent to the receiver. We have file This is a time based collection. Incoming file adapter is set to poll every 30 sec, and the block in BPM timeout in 2 mins ( for testing purpose).
    The BPM receive step (inside the loop) has the start process turned on. The expected behaviour was to receive all files in one instance of BPM and send the merged one out.
    It is spawning the multiple BPM instance based on number of files in the sender file adapter. My guess is it is doing this since we have the start process on receive step and for each receive it is starting a new process. How do we eliminate this to have only one instance start as I am not finding any other step prior to receive ( block , and loop) where I can start the process.
    Any help is appericiated.
    Thanks,
    Samir

    1. If you want to merge the same file format , Use "Loop" step before "Recevie" step. Put some deadline branch , which will ensure your time limit.
    This would resolve your problem.
    2. If you want to merge different file format , you need to have multiple "Receive" steps and for that you need to use the "Fork" step.
    Let me know if you still find any problem.
    Thanks & Regards,
    Dijesh Tanna.

  • Http to bpm scenario

    my scenario is
    i have to create an order in SAP R/3 system for which i am first doing credit check in SQLSERVER and then creating an order in SAP R/3 system.i am using BPM in this scenario.
    when i am executing my scenario,in sxmb_moni i am getting "system error-restart no possible" and outbound technical channel as SA_COMM.
      can anybody explain this to me??

    Hi Rohit,
    The timeout that you are encountering is the BPM timeout.
    U may set from SXMB_ADM -> integration engine configuration ->
    Parameter category SA_COMM and press F1 after selecting SA_COMM on the parameters field.
    Refer SAP Notes 744135
    Regards,
    Prateek

  • Restarting BPM Automatic

    Hi,
    I have some that fall by BPM timeout communication between XI and R3 (180 seconds).
    With the transaction SWF_XI_SWPR I relaunch these messages manually, what I want to know is whether it is possible to automate this action through a JOB or something similar.
    Best Regards.
    Julian

    Regards Ravi.
    His document aims rather as a loose manage a workflow where a user gives approval processes and there is development through to its implementation.
    I was looking for information about how to relaunch syncs messages that fall mistakenly communication between XI and R/3
    Com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 4720d9fb-e721-0191-0000-0000c0a809cc (INBOUND)
    I think that there is this mode, unless it develops.
    Best Regards

  • Database locks in OBPM 10gR3

    Environment:
    Oracle BPM 10gR3 Version: 10.3.1.0.0 Build: #99954
    WebLogic Server 10.0 MP1 Clustered domain
    JDBC Driver - WebLogic Type 4 XA ( weblogic.jdbcx.oracle.OracleDataSource )
    We have a BPM project deployed on the WLS 10.0 MP1 Cluster,which was running fine for the last 18 months. But all of a sudden we are experiencing the database locks errors for the last few days, when we try to restart the BPM Engine.
    WebLogic JTA Timeout = 30 seconds
    Database Distributed_Lock_Timeout = 60 seconds
    WebLogic Datasources for Directory and Engine XA Connection Timeout = 30 seconds
    Error
    Process '/Test#Default-1.0' could not be started. Details:\nProcess execution engine execution error.
    Caused by: Exception [java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock ].
    Caused by: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
    fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:139)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:79)
         at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
         at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
         at fuego.ejbengine.service.EJBActiveProcessService.startProcess(EJBActiveProcessService.java:92)
         at fuego.server.service.ActiveProcessService.runProcessesLoader(ActiveProcessService.java:118)
         at fuego.server.service.ActiveProcessService.activateProcesses(ActiveProcessService.java:88)
         at fuego.ejbengine.service.EJBActiveProcessService.doActivateProcesses(EJBActiveProcessService.java:63)
         at fuego.ejbengine.cluster.DistributedEJBActiveProcessService.initialize(DistributedEJBActiveProcessService.java:37)
         at fuego.ejbengine.cluster.ClusterObjectFactory.initializeActiveProcessService(ClusterObjectFactory.java:33)
         at fuego.ejbengine.Engine.startServices(Engine.java:448)
         at fuego.ejbengine.Engine.start(Engine.java:129)
         at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1853)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1830)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1750)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Caused by: fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock ].
         at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
         at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
         at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
         at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
         at fuego.directory.provider.jdbc.JDBCProcessAccessor.updateDeployedProcess(JDBCProcessAccessor.java:1330)
         at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy57.updateDeployedProcess(Unknown Source)
         at fuego.directory.DirDeployedProcess.update(DirDeployedProcess.java:1022)
         at fuego.server.ActiveProcessManager.handleProcess(ActiveProcessManager.java:496)
         at fuego.server.service.ActiveProcessService.startProcess(ActiveProcessService.java:136)
         at fuego.ejbengine.service.EJBActiveProcessService.startProcessImpl(EJBActiveProcessService.java:107)
         at fuego.ejbengine.service.EJBActiveProcessService.access$100(EJBActiveProcessService.java:32)
         at fuego.ejbengine.service.EJBActiveProcessService$2.execute(EJBActiveProcessService.java:95)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         ... 52 more
    Caused by: java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
         at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
         at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
         at weblogic.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
         at weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
         at weblogic.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
         at weblogic.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
         at weblogic.jdbcx.base.BasePreparedStatementWrapper.executeUpdate(Unknown Source)
         at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:125)
         at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.update(JDBCPersistenceManager.java:946)
         at fuego.directory.provider.jdbc.JDBCProcessAccessor.updateDeployedProcess(JDBCProcessAccessor.java:1327)
         ... 68 more

    Hello -
    Following is the Oracle recommendation for BPM timeouts. Now you can try this.
    Increase the timeout:
    -in the Oracle Weblogic console go to Services -> JTA -> Timeout Seconds . Set the value to 300.
    also the DISTRIBUTED_LOCK_TIMEOUT value for BPM should follow the following formula:
    DISTRIBUTED_LOCK_TIMEOUT >= XA Transaction Timeout >= WebLogic Server JTA timeout
    This means that the configured "DISTRIBUTED_LOCK_TIMEOUT" value should be equal to or
    larger than the "XA Transaction Timeout" value which in turn should be equal to or larger than the "WebLogic Server JTA timeout".
    Note : Check your previous BPM Engine logs, you can see the timeout warning.
    BR,
    Justin.

  • Return message for timeout in BPM

    Hey
    I have a synchronous scenario using BPM. My question is: If the web service I'm calling is down and I receive a timeout, can I then create a return message from BPM to the sender system that can take attributes from the original message that did not reach it's target? I have read that I can do this in case of an error, but I read someone saying this is not possible when we have a timeout...
    Thanks!
    regards Ole
    Edited by: Ole on Sep 23, 2008 1:16 PM

    Hi Ole,
    You can implement a Dedadline branch in your BPM that catches your time out.
    You can follow theese links:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/7c5c41fe06cf1ee10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/8e2d4233c8db2ce10000000a1550b0/frameset.htm
    Carlos

  • How to fail messsages when timeout exception is thrown in BPM?

    Hi
    In my BPM, if the time out exception is thrown in BPM, in SXMB_MONI, all the inbound messages' staus is 'processed sucessfully' ? How can I make the message fail?  With a red flag  or anything indicating exception?
    In my design I used deadline branch to throw time out exception.And in the exception branch I used control step to cancel the process.

    Hi,
    In my design I used deadline branch to throw time out exception.And in the exception branch I used control step to cancel the process
    If this is what you have designed then increasing the timeout using the above mentioned blogs doesn't seem to be logical:) (BPM will throw the error when the deadline is meet....can't understand how by increasing timeout will help you)....instead of increasing the timeout you can increase the time limit mentioned in the deadline branch itself to ensure that your message will be processed in that particular time limit.
    Since you have reached the timeout it means that desired message processing has failed so better you raise an alert instead of going for a increase in timeout....increasing timeout decreases performance...
    Regards,
    Abhishek.

  • 11.1.1.5 - How can we increase the timeout of BPM Workspace ?

    Hi ,
    I am facing an issue where the BPM Workspace times out after every 5 mins or so.
    I read in another post that we need to edit some workspace.properties file - where can I find it.
    I tried using http://technology.amis.nl/blog/13768/increase-the-timeout-of-oracle-bpm-worklist-app/comment-page-1#comment-481839 but ran into some issues (should be there as my comment) where the timeout became too high.
    Appreciate your help.
    Thanks

    I got this resolved. Added a different variable for the weblogic.xml timeout and teh web.xml timeout (Btw the digits after the timeout props are not needed if you donot need too many variables).
    Also My config root was pointing to the wrong war. I changed it to point to a correct .war (relative location can be used too) & it worked just fine after that !
    Thanks

  • BPM Sync/Async Scenario:  error: "Timeout condition of pipeline reached"..!

    Hi,
    I am doing Sync/Async BPM scenario.
    -> Receive message and process and response back to the sender.
    Sometimes it will correct correctly. Sometime the message will come and stay in XI and fails with error
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    I observed that the messages will stay in transaction "SXMS_SAMON" . and will fail after sometime.
    What might be the reason. ? what need to do to stop these kind of errors?
    Thanks
    Deepthi.

    Hi Praveen,
    Webservice <--> XI -->BW .
    BPM :
    start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoBW)->Send(Send Response) ---> stop.
    Messages are getting struck in SMQ1 and SM58 at these three points.
    1. Message comes and stays in SXMB_MONI in status "Log Version"
    The messages are stuck in SMQ1 in READY status without doing any processing.
    XBQO$PE_WS90100002    WORKFLOW_LOCAL_100 1 READY 26.02.2009
    Once I push the queue by Activating/Unlocking, it will process.
    2. when it is trying to send the message to R/3 (Backend system) it is waiting in SM58 with below entry.
    WF-BATCH SWW_WI_EXECUTE_INTERNAL_RFC WORKFLOW_LOCAL_100 Transaction recorded
    Manually I execute LUW to push it. Once I done the message will go to R/3 system and Response mapping also complete.
    3. Again it is waiting at SM58 with below deatails while sending the response to sender.
    PIAFUSER  SWW_WI_COMP_EVENT_RECEIVE_IBF  WORKFLOW_LOCAL_100  Transaction recorded
    we are again manually execute LUW. Once we done the response message will go back to Sender.
    Any Idea to solve this..?
    Thanks
    Deepthi

  • BPM Error: Timeout condition of pipeline reached- After transporting to Prd

    Hi,
    I am doing Sync/Async BPM scenario.
    -> Receive message and process it and send to BI and response has to send back to the sender.
    start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoR/3)->Send(Send Response) ---> stop.
    It is working correctly in Test system. We transported to production and we are getting the below error.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
    <SAP:Retry>N</SAP:Retry>
    </SAP:Error>
    I crossed checked with the test system configuration and evything looks similar. Moreover there are someother Sync/Async BPM scenarios which are all working perfectly.
    Kindly help me , What might be the reason. ?
    Thanks
    Deepthi.

    Some of the trace:
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">No mapping required</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
    - <!--
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--
      -->
    - <Trace level="1" type="B" name="SA_COMM">
      <Trace level="1" type="T">Start Sync/Async Communication</Trace>
      <Trace level="1" type="Timestamp">2009-08-17T04:48:09Z AUSNSW Starting Processing</Trace>
      <Trace level="1" type="T">Pipeline Timeout: 17.08.2009 15:08:10 AUSNSW</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface OS_Payment</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/FOC/DirectSales/Payments</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface AS_Payment</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/SAP_PI/DirectSales/Payment</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>

  • Timeout querying LDAP groups from BPM Workspace Administration page

    I already configured my server to use Active Directory instead the Weblogic embedded LDAP to users authentication in the BPM Workspace.
    When I go to [Weblogic Console / Security Realms / myrealm / Users and Groups / Groups] the console shows correctly all the AD groups after a 20 secs aprox, but when I try to assign some group to a role using the BPM Workspace Administration menu, the app only show users in the search pop up, if I search usign "All" or "Groups" filter I always get this error:
    ORABPEL-10592
    Identity Service soap error.
    BPMIdentityService encountered soap error in method invoke for with fault "javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: miserver.com:389 [Root exception is java.net.ConnectException: Connection timed out]]".
    Ensure that the soap message is properly formed and has all necessary attributes and elements. Contact oracle support if error is not fixable.
            at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.invoke(IdentityServiceSOAPClient.java:265)
            at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.searchGroups(IdentityServiceSOAPClient.java:391)
            at oracle.bpel.services.identity.client.AbstractIdentityServiceClient.searchGroups(AbstractIdentityServiceClient.java:514)
            at oracle.bpel.worklistapp.dc.idbrowser.beans.model.identity.UnrestrictedIDSearcher.searchGroups(UnrestrictedIDSearcher.java:65)
            at oracle.bpel.worklistapp.dc.idbrowser.beans.model.IdentityBrowserModel.executeSearch(IdentityBrowserModel.java:265)
            at oracle.bpel.worklistapp.dc.idbrowser.beans.view.IdentityBrowserView.executeSearch(IdentityBrowserView.java:308)
            at oracle.bpel.worklistapp.dc.idbrowser.beans.controller.IdentityBrowserController.executeSearch(IdentityBrowserController.java:84)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
            at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
            at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
            at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1259)
            at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
            at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
            at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91)
            at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
            at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
            at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
            at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
            at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
            at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91)
            at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812)
            at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292)
            at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
            at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
            at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
            at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
            at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
            at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
            at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
            at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
            at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
            at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
            at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
            at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
            at java.security.AccessController.doPrivileged(Native Method)
            at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
            at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
            at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
            at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
            at java.security.AccessController.doPrivileged(Native Method)
            at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
            at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
            at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
            at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
            at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
            at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
            at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)It seems like the long response time from AD is closing the connection, but I can find where to configure the timeout for workspace app. In my Provider specific settings for AD provider I checked "Keep Alive Enabled" but doesn't work.
    Any ideas about this?, I'm using Oracle SOA Suite 11gR3

    Hello Martin,
    Did you check it on apex.oracle.com because I just did and didn’t encounter the same problem.
    Regards,
    Arie.
    &diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
    &diams; Author of Oracle Application Express 3.2 – The Essentials and More

  • BPM Process - Exception handling or timeout issues?

    Hi Guys,
    I have a BPM process as below.
    1. Receive step: Receive the file with multiple transactions.
    2. Transformation step: Split the file into individual transactions
    3  Block step which includes  -- par for each mode
    1. Send Step (Synchronus): Each individual transaction needs to contact the 3rd party system and get the response. --  Do i need to handle any exceptions here  ?
    2. Container : Collect all the responses 
    Block ends
    4. Transformation: combine all the responses in to a single file
    5. Send Step: synchronus -- send the above single file and get the response back
    6. Transformation : Transform the above response into the target structure.
    7.  Send: send the message asynchronusly to the target system
    I need suggestion regarding the exceptional handling or any time out issues, i need to take care of.
    any suggestions would be really appreciated
    Thanks,
    Raj
    Edited by: raj reddy on Feb 12, 2009 10:12 PM

    Hi,
    I) For the Block holding the Sync Send, create an Exception Block. (right click on Sync Send -> Insert   -> Exception Branch)
    II) Name the Exception block (ex: exceptionHandler).
    III) in the Sync Send step ->Properties -> Exceptions -> in System Error - add exceptionHandler.
    IV) Now within the Exception handler block you can create containers to hold values from payload, throw exception as email etc).
    This will cover your sync send step incase there is an error while sending the request of a timeout during receiving the response.
    You can also do the same for the Step 7) Asycn send - if required.
    Another suggestion in your question Step 6) can be done outside the bpm, when you do the interface determination for that Asycn Send you can add the Interface mapping that will map the responses to the target structure.
    Doing this will reduce one step in your BPM. For further information in how more you can fine tune your bpm, read this blog - https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5113. [original link is broken] [original link is broken] [original link is broken]
    All the best.
    Regards,
    Balaji.M

  • SOAP-XI-RFC sync without BPM scenario: How to catch timeout exception in PI

    Hi all
    I made a scenario where a Webservice request was placed via XI to RFC in CRM.
    This is all done without BPM.
    Now the request came up that I have to handle undhandled exceptions from RFC such as Fatal Error, Dump in CRM etc in PI so that customer can get the idea of what happend in the Backend rather PI failing in the monitoring. I did that in CRM by catching all the exception and sending a common error message to PI.
    But another requirement is to handle Message Timeout of the RFC in PI for e.g. If the request goes to the RFC and due to the volume of the data, it gets Timed Out then neither PI nor CRM can handle this and it results in PI failing to catch this excpetion.
    I tried Fault message type but that does not help either.
    Can I get some expert advice.
    Regards
    Naina

    Include your Send_to_RFC step inside a Block...have a deadline branch for this and an Exception Branch....in deadline branch have control step (thro Exception)....in Exception Branch have a Mapping and a Send Step....this mapping will produce a message (define separate DT for this) having constant values (like timeout occured message)
    If you are fine with alert message...then instead of Mapping and Send step in Exception include a Control Step (thro alert)....alert message can be "timeout occured in receiving RFC response"
    Regards,
    Abhishek.

  • Timeout in control step(raise exception) of BPM

    All,
    Does timeout in the above control step means
    > The typical inactive timeout i.e. while using collecttime pattern, if IDOCS keep coming, the process is going to be active until the point there are no more IDOCs coming and then the exception time window starts kicking in (inactive)
    OR
    > No matter what, the system simply shuts of the inbound channel when the time expires i.e. even if IDOCS are continously flowing and a timeout=1 min is set, the BPM instance will unceremoniously shutdown the instance?
    If #2 is true, I am sure this is load dependent (a 1 min timeout my as well become 2-3 mins correct??)
    Thanks - this is not very clear anywhere
    m

    Im supposing here your scenario is multiple IDOCs to 1 receiver, is that so? For example, n IDOCs to file.
    So, suppose you define, in BPM, the max number of loops (as per CollectPattern example) and also you define a deadline in surrounding Block step. After the block, you have relevant steps (for example, transformation step to execute mapping to file expected structure; and async send step, to send the message to file receiver).
    While an instance is running, it will be receiving IDOCs which satisfy the correlation you set in BPM. As soon as max number or deadline is reached, the IDOCs in that instance will be mapped into a file and that file will be sent to receiver system.
    Whenever new IDOCs arrive, they will be gathered in another BPM instance, and hence they will be sent in another file to receiver system.
    Hope I made myself clear this time.
    Regards,
    Henrique.

  • Who to manage TimeOut in BPM ?

    Hi Xi Experts,
    In SAP WorkFlow, its possible to manage timeout in WorkItem.
    I search in IR and ID on BPM design or configuration with no success . Does XI offers a simple way for this ?.
    Thanks a lot for your responses.
    Etienne

    Yep,
    it's called deadline.
    You can put all the steps you want to be under this timeout condition into a Block Step and then you add a deadline branch to it. In this branch, you configure the amount of time to wait (least granularity in minutes).
    We've performed with success a workaround to use timeouts with intervals less than a minute. Use a fork step. In one branch, put the steps (as you would in block step). In the other, use a transformation step and in it you use a mapping to a dummy message with a Thread.sleep() method in a UDF. With this, you can set any amount of time you want.
    It was not recommended by Tobias Breyer (for those who don't know, he's the BPE developer, at SAP AG) since fork step does not execute the branches with time paralelism but with logical paralelism (meaning that they'll not necessarily be triggered at the same time). But for practical purposes, it works just fine.
    Regards,
    henrique.

Maybe you are looking for

  • Not able to view the content in Microsoft help viewer (MS VS 2012)

    Hello Team, I'm Rahul from Daimler-Chrysler, Bangalore location. I'm the IT Engineer for Daimler-Chrysler. We tried many settings in IE but still not able to resolved. So i need more expert help.  My customer having one issue-  # User is not able to

  • After enter my serial number, he said that to use adobe creative suite 5 master collection you must

    after enter my serial number, he said that to use adobe creative suite 5 master collection you must provide an adobe ID, i entered my adobe ID and password and after that he tell me that, we are enable to start your subscription for adobe creative su

  • Embedding issues in IE

    I have a form embedded into a website and it has looked great for 6 months. Now all of the sudden in IE it is very fuzzy but in Google Chrome it still looks great. Any ideas?

  • Opening Hemera .hpi images

    Does anyone know if there's a way of opening Hemera .hpi images in Photoshop (CS3) other than via the clunky and unreliable (at best) Hemera browser? Thanks in advance.

  • Records not found in Infoset

    Hi, we have a infoset which build on 4-5 DSO and some master data. there are some records rhich are presant in DSO but not in report created on that infoset. Also when we doing the "display data" of that infoset those records are not available.  Can