ESB calling BPEL: failed to handle message error

Hi all,
I'm trying to invoke a BPEL process from an ESB process but I'm getting the following error:
<2007-03-21 12:38:26,458> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
javax.transaction.RollbackException
     at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:582)
     at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:244)
     at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:130)
     at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433)
     at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
     at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
     at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:139)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.transaction.RollbackException
     at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:582)
     at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:244)
     at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:130)
     at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433)
     at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
     ... 29 more
<2007-03-21 12:38:26,458> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Fallo al manejar el mensaje de distribución ... excepción ORABPEL-05002
Error del manejador de mensajes.
Se ha producido una excepción al intentar procesar el mensaje "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; la excepción es: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
ORABPEL-05002
Error del manejador de mensajes.
Se ha producido una excepción al intentar procesar el mensaje "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; la excepción es: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:171)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
I've been looking through the Internet but i haven't found anything. this same process has been working, so I don't understand anything. Please, can anyone help me? thank you very much.

It sounds like the BPEL process is failing. Is there an error instance n the BPEL console? Can you test the BPEL process standalone from the BPEL console?

Similar Messages

  • ESB calling BPEL service

    Hello All.
    We have created an ESB that includes a database partner link that reads new records then uses that data and calls a BPEL process.
    We have a single server in development and clustered servers in test, qa and prod.
    In dev, the ESB calls the BPEL process once as it should.
    In the clustered environments, the ESB calls the BPEL process twice. In the ESB console there is only one instance of the ESB and in the BPEL console there are two.
    Is this a bug in the software or is there a ESB/BPEL configuration that we might have missed?
    Thanks in advance.

    You need to implement the DB polling as a singleton service. What is happing is the activation agent is running on both nodes. You need to make it run on just one.
    have a look at metalink note 746108.1
    also the enterprise deployment guide provides pointers
    http://download.oracle.com/docs/cd/E10291_01/core.1013/e10294/webapp.htm#sthref142
    cheers
    James

  • ESB: Calling BPEL-Workflow

    I am trying to initiate a BPEL-Workflow with ESB.
    I am getting following error-message:
    oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: Eine unbehandelte Exception wurde im ESB-System ausgelöst. Es wurde folgende Exception gemeldet: "java.lang.Exception: Erstellen von "ejb/collaxa/system/DeliveryBean"-Bean nicht erfolgreich. Es wurde folgende Exception gemeldet: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
         javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279)
         at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:83)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:67)
         at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
         at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source)
         at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
         at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.raiseEvent(Unknown Source)
         at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.raiseEvent(Unknown Source)
         at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(Unknown Source)
         at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(Unknown Source)
         at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:279)
         at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1327)
         at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1276)
         at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1230)
         at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:482)
         at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:383)
         at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
         at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
         at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
         at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.naming.AuthenticationException: Not authorized
         at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:99)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
         at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:609)
         at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:153)
         at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:137)
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:251)
         at com.evermind
    Can anybody help, how to set the right permissions?

    IMHO you did not solve your first problem. Because in first case you chose directly from routing service as target operation your BPEL process operation. And ESB wanted to execute that though RMI. Which has transaction support and is also faster. But your credentials were invalid. Therefore you got that exception.
    After that you decided to use SOAP HTTP protocol, which is not transaction enabled and is slower :-(
    In case you would like to use RMI, you have to change in your SOA Suite in this file:
    <orahome>/bpel/utilities/ant-orabpel.properties
    credentials for oc4jadmin user. After you update that, restart server.
    And then it should work.

  • SubTemplate call is failing with XML-22002 error

    Hi,
    I am using Oracle BI Publisher 10.1.3.4 in WebLogic Server 10.3.6.0.
    Subtemplate reference is used in some reports. Whn we click on view of such report, below error is shown.
                   "The report cannot be rendered because of an error, please contact the administrator."
    The patch 9017232 is also installed.
    The detailed error log is below:
    [111413_123806333][oracle.apps.xdo.common.xml.XSLTWrapper][ERROR] XSL error:
    <Line 3, Column 71>: XML-22002: (Fatal Error) Error while processing include XSL file (xdoxsl:///FCReports/HeaderFooter_LandScape.xsb).
    <Line 78, Column 312>: XML-22008: (Error) Namespace prefix 'ref' used but not declared.
    @Line 3 ==> <xsl:import href="xdoxsl:///FCReports/HeaderFooter_LandScape.xsb"/>
    [111413_123806337][oracle.apps.xdo.template.FOProcessor][EXCEPTION] java.lang.reflect.InvocationTargetException
        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 oracle.apps.xdo.common.xml.XSLT10gR1.invokeNewXSLStylesheet(Unknown Source)
        at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
        at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
        at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
        at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
        at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
        at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
        at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
        at oracle.apps.xdo.servlet.RTFCoreProcessor.transform(RTFCoreProcessor.java:91)
        at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:276)
        at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
        at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:554)
        at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:257)
        at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
        at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
        at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        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:301)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:97)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.xdo.parser.v2.XPathException: Namespace prefix 'ref' used but not declared.
        at oracle.xdo.parser.v2.XSLProcessor.reportException(XSLProcessor.java:806)
        at oracle.xdo.parser.v2.XSLProcessor.newXSLStylesheet(XSLProcessor.java:614)
        ... 38 more
    Syntax used in Report is
    <?import:xdoxsl:///Reports/HeaderFooter_LandScape.xsb?loc=en_US><?call@inlines:Header?><?with-param:PM_REPORT_NAME;string('Customer details report')?><?end call?>
    XDO.CFG file contents
    <config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/">
       <properties>
          <property name="bursting-multithreading-on">false</property>
          <property name="xdk-secure-io-mode">false</property>
       <property name="xslt-scalable">true</property></properties>
    </config>
    Please suggest whether this issue is with BI report setup.
    Thanks in Advance.
    Regards,
    Bala.

    Hi Surya,
    Would you let us know from where you are calling web service and for what?
    And if possible provide error log as screenshot or txt file. So that it will be easy to trace issue.
    For gland your issue, go through below posts
    Not able to execute MII Transaction as web service
    Error calling BLS Transaction as Web service
    Problem in generating wsdl ?
    Create MII transaction & MII Web Service and consume them in ABAP
    Regards,
    Praveen Reddy

  • Appcmd.exe add backup Output message: ERROR ( hresult:80070002, message:Command execution failed.

    [04.01.2014 21:41:55.0743] [1] 0.  ErrorRecord: System.InvalidOperationException: Running the command 'C:\Windows\system32\inetsrv\appcmd.exe add backup IISBackup130408621156784845' failed. 
    Output message: ERROR ( hresult:80070002, message:Command execution failed.  
    The system cannot find the file specified.
    Error message:  
    Process exit code: 2.
    [04.01.2014 21:41:55.0746] [1] [ERROR] The following error was generated when "$error.Clear(); 
    configure-WSManIISHosting -EnableKerberosModule;
    " was run: "Running the command 'C:\Windows\system32\inetsrv\appcmd.exe add backup IISBackup130408621156784845' failed. 
    Output message: ERROR ( hresult:80070002, message:Command execution failed.  
    The system cannot find the file specified.
    Error message:  
    Process exit code: 2.".
    [04.01.2014 21:41:55.0746] [1] [ERROR] Running the command 'C:\Windows\system32\inetsrv\appcmd.exe add backup IISBackup130408621156784845' failed. 
    Output message: ERROR ( hresult:80070002, message:Command execution failed.  
    The system cannot find the file specified.
    BlatniS

    Try this instead in an Elevated PowerShell
    Import-Module WebAdministration
    Backup-WebConfiguration -Name MyIISBackup
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • Transfered calls are failing

    Hi All,
    In IPCCE environment, some of the agent to agent transfer calls are failing with the below error.
    Couldn't find CallConnection with DeviceID of 32767308.  CILConnectionID:9
    I can see this same device ID 32767308 for all the failed calls. This device ID 32767308 is present only in ctios client and server logs. Any idea where/why this device ID getting generated for the failed calls?
    Regards,
    Adithya

    Hi Irfan,
    Thanks for the reply.
    Let me explain the cal flow.
    Agent A selects the available agents(Agent B) first and then consults with agent B(First Call leg). If agent B agrees to take the call, agent A does the complete transfer.(call leg 2) which triggers the ICM script thru a Dailed Number.
    Just we found that here  the call leg 1 is getting dropped before establishing the call leg 2. Thats why we see that the error message Couldn't find CallConnection with DeviceID. Any suggestion?
    Regards,
    Adithya

  • Error Calling BPEL from ESB

    I am using the SOA Suite and have a very simple ESB project which picks up files from a directory and calls a BPEL process following a simple XSL translation. I am getting the following error:
    An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is: javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized] at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279) at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250) at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:174) at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:158) at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusiness
    The esb has been deployed to our server (OAS 10.1.3) using jdeveloper. Please can anybody point me in the right direction.

    Not really. There are 2 ways to invoke BPEL.
    1) Over SOAP using an ESB SOAP service that parses a BPLE WSDL. This works like any standard HTTP/SOAP invocation and would be used when BPEL and ESB are not in the same container.
    2) Over Java by add a routing rule to an ESB Routing Servie and select a BPEL process in the BPELSystem as the target. This is the preferred binding when ESB and BPEL are colocate din the same container. This takes advantage of the fact that ESB kistens on the BPEL internal Control jms queue when a BPEL process is deployed into the container. That is how the BPEL processes show up in the BPELSystem ESB service tree.

  • Oracle 10G JMS error : Failed to handle dispatch message ... exception ORABPEL-05002

    Hi All,
    We are using a JMS adapter as partner link in a BPEL process to produce messages to JMS Queue.
    We are getting an error while producing a message to a JMS Queue.
    The error comes for 1 or 2 instances among 5 to10 intsances. (all these instances ran with in 1 or 2 seconds).
    We are using Oracle 10G SOA suite.
    This error is getting in the Production environment.
    The error is as follows (took error from server log).
    Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
    messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
    parts: {{summary=file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
    file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
    ; nested exception is:
    ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    I tried the below JMS tunings with differnt combination, but no improvement.
                <property name="useJCAConnectionPool">true</property>
                <property name="maxSizeJCAConnectionPool">500</property>
                <property name="retryMaxCount">10</property>
                <property name="retryInterval">60</property>
    Please let me know if any other logs or any other information is required.
    Thanks,
    Pershad

    sorry, I forgot the below things which I tried to tune the JMS.
    <property name="retryMaxCount">10</property>
    <property name="retryInterval">60</property>
    <property name="useJCAConnectionPool">true</property>
    <property name="maxSizeJCAConnectionPool">500</property>
    Thanks.

  • Error when calling BPEL from ESB in clustered environment

    Hi
    We have recently installed SOA Suite in a clustered environment and have a serious issue.
    I am not able to call BPEL processes from my ESB services via WSIF (by using the 'browse target operation' in JDeveloper). The exception i get at runtime is this.
    "javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found"
    When I instead call the BPEL process via SOAP (by using a SOAP invocation service i JDeveloper) it works fine.
    Everything works fine in development environment which not are clustered.
    Has anyone any excperience from using ESB in a clustered environment?
    Regards
    Kalle Viklund

    Hi
    ESB and BPEL resides in the same oc4j-instance. Though, esb-rt and orabpel are different applications in that oc4j-instance. And the lookup 'ejb/collaxa/system/DeliveryBean' only exists in the orabpel application.
    In the ESB Console I already have the same setting for the 'BPELSystem' as for the 'Defaultsystem'.
    Cluster name: esb_prod
    Virtual host: prod1.sth.nu
    Port: 80
    Topic location: ESBTopics/Topics/ESB_JAVA_DEFERRED
    Connection factory location: OracleOJMS/XATCF
    regards
    Kalle

  • Calling BPEL Process From ESB

    Hi Gurus,
    I'm experiencing an issue calling a BPEL process using the ESB SOAP Service. Basically, the ESB calls the BPEL process and manages to pass the message to the asychronous BPEL process however the first step in the BPEL process after the Recieve, an Assign, always fails with an Xpath error saying that the attribute being mapped is blank. However, when I look at the Recieve step I can see the value for this attribute. I can Initiate the BPEL process manually and enter the same values and these process successfully.
    Has anyone encountered this issue previously or know what I'm doing wrong?
    Any assistance appreciated.
    Pete

    Hi there,
    I am getting the same issue. I have two bpel processes, the first processplaces data into a common .xsd format and then sends it over to another process with is expeting the same .xsd format.
    I'm pretty sure i know what the issue is, but i'm not sure what the philosophy behind the whole thing is and how it is solved.
    When i transfrom the data over to the common .xsd is allocated a namespace ns0 which is then prepended to each element. When this is sent to the other process this stays prepended. The data is then allocated to the common .xsd in the second process with is allocated another namespace ns3.
    So when you try an assign is searching for ns3:rootElemnt....... which doesn't exist as it as the ns0 carried over from the first process.
    Is this correct? What do we do to get round it?
    Thanks,

  • Error handling message: flex.messaging.MessageException: No destination with id '' is registered with any service

    Hi,
    We are using both Remoting and HttpService calls for our business application.
    We were able to communicate with the LCDS server till this point with whatever default settings provided for AMFChannel configuration in services-config.xml through a flex client. Also we have a clustered environment for this servers which works out fine till now.
    Now for performance enhancement improvements, we started using Caching Mechanism for our HttpService urls (through some third party service), which will now be cached on the network instead of accessing every time from our clustered servers. But all our AMF calls through Remoting services are still the same.
    So after migrating to this Caching environment, we started encountering intermittent issues where some of our AMF calls were failing with falling exception trace :
    16:03:40,576 INFO [STDOUT] [Flex] [ERROR] Error handling message: flex.messaging.MessageException: No destination with id '' is registered with any service.
    incomingMessage: Flex Message (flex.messaging.messages.CommandMessage)
    operation = invalid.12
    clientId = D7855C44-810B-64AB-C176-7C38F83DEB2C
    correlationId =
    destination =
    messageId = 2DA6BDB8-859E-8AE1-03A4-57743DE03188
    timestamp = 1247007820561
    timeToLive = 0
    body = {}
    hdr(DSId) = D77C6BD2-3808-1512-3984-CCF397428E35
    hdr(DSEndpoint) = my-amf
    errorReply: Flex Message (flex.messaging.messages.ErrorMessage)
    clientId = D7855C44-810B-64AB-C176-7C38F83DEB2C
    correlationId = 2DA6BDB8-859E-8AE1-03A4-57743DE03188
    destination =
    messageId = D7855C64-3E08-466B-96F8-5BAE7D385129
    timestamp = 1247007820574
    timeToLive = 0
    body = null
    code = Server.Processing
    message = No destination with id '' is registered with any service.
    details = null
    rootCause = null
    body = null
    extendedData = null
    So i do not understand, most of the times the AMF calls works correctly and some times it fails with above fail trace.
    Any suggestions would be appreciated.
    Thanks,
    FlexPirate

    It might be a bit late but replying for anyone who lands on this page facing this same problem.
    The solution for "No destination with id '<my dest id>' is registered with any service" problem is that you have to make sure your destination definition is added in your:
    C:\ColdFusion9\wwwroot\WEB-INF\flex\messaging-config.xml
    Secondly, If you are deploying it on a ColdFusion Server, then you have to make sure exact same definition is added in Server messaging-config.xml file as well.
    This should solve this problem.
    While we are at it, wanted to point another possible gotcha.
    if your Server is using SSL protocol i.e. it has https:// rather than http://, Then within your <destination> definition block in messaging-config.xml, you have to add appropriate secure channels in <channels> section. You can find all available channel definitions in
    C:\ColdFusion9\wwwroot\WEB-INF\flex\services-config.xml

  • BPEL Transaction Inactive : Instance terminated without handling the Error

    Hi All,
         I have a BPEL process which uses XA transaction to insert data in MS SQL Server table.
    When I try to insert "out of range date value", it errs out as expected, but the transaction terminates without proceeding for the error handling part. I even tried disabling the idempotent option for the DB adapter, still the process terminates without error handling.
    Kindly guide me how I can overcome transaction inactive issue and handle the error in the catch all block.
    Thanks in advance.
    The error message is as follows,
    "Error Message: {http://schemas.oracle.com/bpel/extension}runtimeFault
    Non Recoverable System Fault :
    < bpelFault><faultType>0</faultType><runtimeFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "130,047", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "130047" for process "SyncAggregateSpendABCSImpl" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error.< /summary></part><part name="detail"><detail>ORABPEL-02199 JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "130,047", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "130047" for process "SyncAggregateSpendABCSImpl" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error. at com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive(TransactionUtils.java:107) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:356) at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1099) at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:594) at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:132) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:173) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2718) at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1197) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1100) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:76) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:251) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:330) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4652) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4583) at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:714) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:559) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:531) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:319) at sun.reflect.GeneratedMethodAccessor16515.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.oracle.pitchfork.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:103) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:113) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:100) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:154) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:113) at sun.reflect.GeneratedMethodAccessor1671.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.oracle.pitchfork.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:68) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54) at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy368.handleInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:30) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:89) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:65) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:933) at java.lang.Thread.run(Thread.java:662) Caused by: oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.integration.platform.blocks.adapter.fw.jca.cci.EndpointInteractionException.getFabricInvocationException(EndpointInteractionException.java:75) at oracle.integration.platform.blocks.adapter.AdapterReference.getFabricInvocationException(AdapterReference.java:316) at oracle.integration.platform.blocks.adapter.AdapterReference.request(AdapterReference.java:219) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:182) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:190) at sun.reflect.GeneratedMethodAccessor2127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy386.request(Unknown Source) at oracle.fabric.CubeServiceEngine.requestToMesh(CubeServiceEngine.java:858) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:267) ... 61 more Caused by: BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:486) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:572) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeSyncJcaReference(JCAInteractionInvoker.java:545) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performSynchronousInteraction(JCAEndpointInteraction.java:547) at oracle.integration.platform.blocks.adapter.AdapterReference.request(AdapterReference.java:179) ... 76 more Caused by: BINDING.JCA-11616 DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:698) at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:664) at oracle.tip.adapter.db.exceptions.DBResourceException.outboundWriteException(DBResourceException.java:712) at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:1117) at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:247) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:357) ... 80 more Caused by: java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value. at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1178) at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:210) at org.eclipse.persistence.internal.databaseaccess.DatabasePlatform.executeBatch(DatabasePlatform.java:2101) at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:144) at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:535) at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:1717) at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:253) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:207) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:264) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeSelect(DatasourceCallQueryMechanism.java:246) at org.eclipse.persistence.queries.DataReadQuery.executeNonCursor(DataReadQuery.java:197) at org.eclipse.persistence.queries.DataReadQuery.executeDatabaseQuery(DataReadQuery.java:152) at org.eclipse.persistence.queries.DataReadQuery.execute(DataReadQuery.java:137) at org.eclipse.persistence.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2831) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1449) at org.eclipse.persistence.sequencing.QuerySequence.select(QuerySequence.java:309) at org.eclipse.persistence.sequencing.QuerySequence.updateAndSelectSequence(QuerySequence.java:254) at org.eclipse.persistence.sequencing.StandardSequence.getGeneratedValue(StandardSequence.java:62) at org.eclipse.persistence.sequencing.DefaultSequence.getGeneratedValue(DefaultSequence.java:145) at org.eclipse.persistence.sequencing.Sequence.getGeneratedValue(Sequence.java:225) at org.eclipse.persistence.internal.sequencing.SequencingManager$NoPreallocation_State.getNextValue(SequencingManager.java:677) at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067) at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70) at org.eclipse.persistence.internal.descriptors.ObjectBuilder.assignSequenceNumber(ObjectBuilder.java:355) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:351) at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:163) at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:178) at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:475) at org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80) at org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:91) at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:287) at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58) at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:844) at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:743) at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108) at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2871) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1449) at org.eclipse.persistence.internal.sessions.CommitManager.commitNewObjectsForClassWithChangeSet(CommitManager.java:224) at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:123) at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3800) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1416) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1505) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writeChanges(UnitOfWorkImpl.java:5502) at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:927) at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:247) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:357) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:572) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeSyncJcaReference(JCAInteractionInvoker.java:545) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performSynchronousInteraction(JCAEndpointInteraction.java:547) at oracle.integration.platform.blocks.adapter.AdapterReference.request(AdapterReference.java:179) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:182) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:190) at sun.reflect.GeneratedMethodAccessor2127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy386.request(Unknown Source) at oracle.fabric.CubeServiceEngine.requestToMesh(CubeServiceEngine.java:862) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:267) at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1099) at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:594) at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:132) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:75) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:173) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2718) at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1197) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1100) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:78) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:251) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:330) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4652) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4584) at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:714) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:559) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:531) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:319) at sun.reflect.GeneratedMethodAccessor16515.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.oracle.pitchfork.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:103) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:113) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:100) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:154) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:113) at sun.reflect.GeneratedMethodAccessor1671.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.oracle.pitchfork.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:68) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54) at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy368.handleInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:30) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:89) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:66) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909) ... 2 more< /detail></part><part name="code"><code>com.collaxa.cube.engine.EngineException</code></part></runtimeFault></bpelFault>"

    Hello,
    You can't catch the roll back exception directly. It will rollback your transaction and because of that it will not get in the catch block.
    To solve this you can create a new BPEL to do the DB insert. Invoke that BPEL with a new transaction. Catch the Database error in the first BPEL
    Example:
      <component name="InsertData" version="2.0">
        <implementation.bpel src="InsertData.bpel"/>
        <property name="bpel.config.transaction">requiresNew</property>
        <property name="bpel.config.inMemoryOptimization">false</property>
        <property name="bpel.config.completionPersistPolicy">On</property>
      </component>
    In this example I have all my logic in the "SyncSypplierMaster" and then I invoke the BPEL "InsertData" (with the property <property name="bpel.config.transaction">requiresNew</property>) to insert in the database. I catch the error in the "SyncSypplierMaster" BPEL where I have the "InsertData" invocation.
    This works because SyncSypplierMaster" is in a different transaction.
    Note: If you are inserting in multiple tables and the error is in a child table you will not catch the DB error message also. If this is your case, I recommend you to investigate what is the patch required to solve this problem.
    Best Regards,
    Daniel Dias

  • Error upon ResolveCallbackMessage class for Failed to handle dispatch msg

    Hello,
    I'm using Oracle BPEL Manager on Windows XP,
    the version of Eclipse is 3.0.0, build id 200406111814,
    and j2sdk1.4.2_04.
    I have deployed from the Developer Prompt the Seller and the Buyer processes, and from the Oracle BPEL console started 3 instances for the Buyer with values for the CID and Order respectively: 1,1; 2,2; 3,3.
    After several seconds, I had 3 instances for the Seller with state 'completed' and 3 instances for the Buyer with state 'running'.
    At the same time, appeared 3 error messages on the Start BPEL Process Manager Console with the same content:
    <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.delivery.ResolveCallbackMessage"; the exception is: Transaction was rolled back: java.lang.ClassCastException; nested exception is: java.lang.ClassCastException
    These processes use correltation defined and it seems the the Oracle BPEL Server does not recognize when there is more then 1 running instances and is received message, to which instances to apply it according to the correlation property.
    Need help if there is something else to be configured this to work,
    Thank you in advance,
    Best Regards

    Hi,
    I've tested the Seller and buyer Samples by reproducing the upper situation - several running instance of Buyer process,
    and everything works fine - no errors.
    But, the situation if I'm using a new created process leads to the same error.
    Here what I'm doing:
    Process test1: (async. oracle bpel process)
    =============================================
    The test1.bpel file is:
    &lt;!-- test1 BPEL Process [Generated by the Oracle BPEL Designer] --&gt;
    &lt;process name="test1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cor="http://acm.org/samples" targetNamespace="http://acm.org/samples" suppressJoinFailure="yes" xmlns:tns="http://acm.org/samples" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension"&gt;
         &lt;partnerLinks&gt;
              &lt;partnerLink name="client" partnerLinkType="tns:test1" myRole="testProvider" partnerRole="testRequester"/&gt;
         &lt;/partnerLinks&gt;
         &lt;variables&gt;
              &lt;variable name="input" messageType="tns:Order1RequestMessage"/&gt;
              &lt;variable name="output" messageType="tns:echoResponseMessage"/&gt;
              &lt;variable name="DeliveryS" messageType="tns:DeliveryRequestMessage"/&gt;
              &lt;variable name="result" type="xsd:string"/&gt;
         &lt;/variables&gt;
         &lt;correlationSets&gt;
              &lt;correlationSet name="id123" properties="tns:id123"/&gt;
         &lt;/correlationSets&gt;
         &lt;sequence name="main"&gt;
              &lt;receive name="receiveInput" partnerLink="client" portType="tns:test1" operation="order123" variable="input" createInstance="yes"&gt;
                   &lt;correlations&gt;
                        &lt;correlation set="id123" initiate="yes"/&gt;
                   &lt;/correlations&gt;
              &lt;/receive&gt;
              &lt;assign&gt;
                   &lt;copy&gt;
                        &lt;from variable="input" part="payload" query="//onInitate123/rumiBegin"/&gt;
                        &lt;to variable="result"/&gt;
                   &lt;/copy&gt;
              &lt;/assign&gt;
              &lt;receive name="getDelivery" partnerLink="client" portType="tns:test1" operation="dlv" variable="DeliveryS" createInstance="no"&gt;
                   &lt;correlations&gt;
                        &lt;correlation set="id123" initiate="no"/&gt;
                   &lt;/correlations&gt;
              &lt;/receive&gt;
              &lt;assign&gt;
                   &lt;copy&gt;
                        &lt;from variable="DeliveryS" part="payload" query="//onDelivery123/rumiEnd"/&gt;
                        &lt;to variable="result"/&gt;
                   &lt;/copy&gt;
              &lt;/assign&gt;
              &lt;invoke name="callbackClient" partnerLink="client" portType="tns:testCallback" operation="onResult" inputVariable="output"/&gt;
         &lt;/sequence&gt;
    &lt;/process&gt;
    ==============================================
    The test1.wsdl file is:
    &lt;?xml version="1.0"?&gt;
    &lt;definitions name="test1"
    targetNamespace="http://acm.org/samples"
    xmlns:tns="http://acm.org/samples"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    &gt;
    &lt;types&gt;
    &lt;schema attributeFormDefault="qualified"
    elementFormDefault="qualified"
    targetNamespace="http://acm.org/samples"
    xmlns="http://www.w3.org/2001/XMLSchema"
    &gt;
    &lt;element name="onInitate123" type="tns:Order" /&gt;
    &lt;complexType name="Order"&gt;
                   &lt;sequence&gt;
                   &lt;element name="rumiBegin" type="string" /&gt;
              &lt;/sequence&gt;
              &lt;/complexType&gt;
    &lt;element name="onDelivery123" type="tns:Delivery" /&gt;
    &lt;complexType name="Delivery"&gt;
                   &lt;sequence&gt;
                   &lt;element name="rumiEnd" type="string" /&gt;
              &lt;/sequence&gt;
              &lt;/complexType&gt;
              &lt;element name="echoResponse"&gt;
    &lt;complexType&gt;
    &lt;sequence&gt;
    &lt;element name="result" type="string"/&gt;
    &lt;/sequence&gt;
    &lt;/complexType&gt;
    &lt;/element&gt;
    &lt;/schema&gt;
    &lt;/types&gt;
    &lt;message name="Order1RequestMessage"&gt;
    &lt;part name="payload" element="tns:onInitate123"/&gt;
    &lt;/message&gt;
    &lt;message name="Order1ResponseMessage"&gt;
    &lt;part name="payload" element="tns:echoResponse"/&gt;
    &lt;/message&gt;
    &lt;message name="DeliveryRequestMessage"&gt;
    &lt;part name="payload" element="tns:onDelivery123"/&gt;
    &lt;/message&gt;
    &lt;message name="DeliveryResponseMessage"&gt;
    &lt;part name="payload" element="tns:echoResponse"/&gt;
    &lt;/message&gt;
    &lt;message name="echoResponseMessage"&gt;
    &lt;part name="payload" element="tns:echoResponse"/&gt;
    &lt;/message&gt;
    &lt;portType name="test1"&gt;
    &lt;operation name="order123"&gt;
    &lt;input message="tns:Order1RequestMessage"/&gt;
    &lt;/operation&gt;
    &lt;operation name="dlv"&gt;
    &lt;input message="tns:DeliveryRequestMessage"/&gt;
    &lt;/operation&gt;
    &lt;/portType&gt;
    &lt;portType name="testCallback"&gt;
    &lt;operation name="onResult"&gt;
    &lt;input message="tns:echoResponseMessage"/&gt;
    &lt;/operation&gt;
    &lt;/portType&gt;
    &lt;plnk:partnerLinkType name="test1"&gt;
    &lt;plnk:role name="testProvider"&gt;
    &lt;plnk:portType name="tns:test1"/&gt;
    &lt;/plnk:role&gt;
    &lt;plnk:role name="testRequester"&gt;
    &lt;plnk:portType name="tns:testCallback"/&gt;
    &lt;/plnk:role&gt;
    &lt;/plnk:partnerLinkType&gt;
    &lt;bpws:property name="id123" type="xsd:string"/&gt;
    &lt;bpws:propertyAlias propertyName="tns:id123"
    messageType="tns:Order1RequestMessage" part="payload"
    query="/onInitate123/rumiBegin"/&gt;
    &lt;bpws:propertyAlias propertyName="tns:id123"
    messageType="tns:DeliveryRequestMessage" part="payload"
    query="/onDelivery123/rumiEnd"/&gt;
    &lt;/definitions&gt;
    ================================================
    From a different SOAP Server I'm sending message for the operation 'order123' to the Oracle Server
    using as endpoint location http://leon:9700/orabpel/default/test1
    and the message looks like this:
    (the value for the correlation is 101)
    &lt;SOAP:Envelope
    SOAP:encodingType='http://schemas.xmlsoap.org/soap/encoding/'
    SOAP:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:ref="http://schemas.xmlsoap.org/ws/2002/04/reference/"
    xmlns:dt='urn:schemas-microsoft-com:datatypes'&gt;&lt;SOAP:Body&gt;
    &lt;order123&gt;&lt;onInitate123&gt;&lt;rumiBegin&gt;101&lt;/rumiBegin&gt;&lt;/onInitate123&gt;&lt;/order123&gt;&lt;/SOAP:Body&gt;
    &lt;/SOAP:Envelope&gt;
    As a result there is an instance with state running for the process test1 on the Oracle BPEL Console.
    After this, I'm sending again from the same SOAP Server message for the operation 'dlv' like this:
    (the value for the correlation is 101)
    &lt;SOAP:Envelope
    SOAP:encodingType='http://schemas.xmlsoap.org/soap/encoding/'
    SOAP:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:ref="http://schemas.xmlsoap.org/ws/2002/04/reference/"
    xmlns:dt='urn:schemas-microsoft-com:datatypes'&gt;&lt;SOAP:Body&gt;
    &lt;dlv&gt;&lt;onDelivery123&gt;&lt;rumiEnd&gt;101&lt;/rumiEnd&gt;&lt;/onDelivery123&gt;&lt;/dlv&gt;&lt;/SOAP:Body&gt;&lt;/SOAP:Env
    elope&gt;
    AS a result the instance created before continues to have state 'running' (which is supposed to be 'completed' as by using the same correlation value)
    and the error is given on the Oracle BPEL Server Console:
    &lt;2004-08-24 14:56:02,200&gt; &lt;ERROR&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseScheduledWorker::process&gt;
    Failed to handle dispatch message ... exception Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.delivery.ResolveCallbackMessage";
    the exception is: Transaction was rolled back: java.lang.ClassCastException; nested exception is: java.lang.ClassCastException

  • Response not coming back to ESB when calling BPEL process

    Hi,
    I am doing some demo,
    the actual process is, in ESB, I am reading a file and passing thsoe fiel contents to BPEL as SOAP service. In BPEL proecess, I processed the message and sending the response back to the ESB. When I deployed and check the process flow in the BPEL console, everything looks fine, I mena, it sending the response back to the ESB, where as in ESB process, I am not able to see the response.
    Is there any thing that I am missing?
    Thanks.

    Is the BPEL process a synchronous process?
    Also for performance reasons it it best to call BPEL process via the direct jca connector not SOAP.
    You do this by just selecting the BPEL process in the routing service going through the wizard. There is no need to creat a SOAP service. The good this about this is that in the ESB process it provides a link to the BPEL process.
    cheers
    James

  • Calling BPEL WSDL form ESB(Urgent)

    Hi,
    Firstly I am new to BPEL. This question might be very simple. I need the solution ASAP.
    Coming to the usecase.
    I have one service "A" in ESB and other service "B" in BPEL. To make it simple I need to listen a file using a file adapter in service "A"(ESB) and route the values to other service "B" (BPEL) and insert in to database using a database adapter.
    Can this be possible. If so can any one please provide me pointers to create the services in ESB and BPEL to execute the above usecase.
    Thanks
    Rao.

    Hi,
    Thats not that difficult.
    The steps to undertake are :
    1.create a bpel proces which accepts your format as input. and write it to your database either calling a stored procedure or insert the data right into a table.
    2. deploy this project to your app server and test it using the BPELConsole. This way you can make sure your BPEL project works.
    3. create an ESB process which reads a file ( the file adapter ). You'll get a Routing Service for free.
    4. Double click on the routing service, press the green + sign to add a routing rule. Select the service browser. browse your BPEL system and select the BPEL process you deployed in step 2.
    5. Create the mapper file to map the input of your file adapter to the input of your BPEL process
    6. Deploy your ESB process.
    And you should be ready to go.
    HTH
    Edit :
    You can also use a SOAP Service as the previous poster mentioned. There are a few ways to tie ESB and BPEL together. One is by using SOAP the other is by calling the BPEL process directly ( internally the data then flows over a RMI connection ).
    Message was edited by:
    Martin.Kleinman

Maybe you are looking for

  • Doubt on Alert Configuration:PI 7.1

    Hi all,         I am working on PI 7.1.Ours is an Idoc to JDBC Scenario.We reqiure Alerts to be triggered for error notifications and also data from the payload as part of alert emails. BPMs are not used in our design. Please help me on how to procee

  • How do I get rid of IOS7 app icons?

    The new IOS7 update icons look like toy apps. They look very unprofessional and hard to figure out. What happened to Apple being for educational and business applications and a reliable computer and software company? Like to know how to change back t

  • Timing information

    Is it possible to show timing information for a SQL query region like the SQL Workshop shows when I execute anything in it? "Statement took 0.05 seconds" How would pagination affect this? Would it show the time to fetch the currenly displayed set of

  • Every time I restart my laptop, the iTunes tutorial pops up - How do I stop this?

    I cannot find the option to stop this form happening. I cannot find the 'com.apple.iTunes.plist' that people have suggested deleting from other forums.

  • Windows troubleshooter, windows update, and windows defender are not working :(

    I'm running Windows 7, 64 bits and I suddenly encountered this problem, apparently none of these basic Windows things are working, I can't turn them on in anyway I've tried, and apparently I have no viruses in my computer. Has anyone encountered the