JCA binding error in bpel(11g)

Hi all,
I have created a DB adapter in BPEL and have deployed the bpel, when i tested the service i got this below error
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'AddressValidationListSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. AddressValidation:AddressValidationList [ AddressValidationList_ptt::AddressValidationListSelect(AddressValidationListSelect_inputParameters,TbgnStreetCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/11g'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/11g. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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:1245) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) 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:102) 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:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:698) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:285) 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:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) 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.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) 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.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) 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.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) 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.run(WebAppServletContext.java:3592) 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:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'AddressValidationListSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. AddressValidation:AddressValidationList [ AddressValidationList_ptt::AddressValidationListSelect(AddressValidationListSelect_inputParameters,TbgnStreetCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/11g'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/11g. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:985) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:716) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 68 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'AddressValidationListSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. AddressValidation:AddressValidationList [ AddressValidationList_ptt::AddressValidationListSelect(AddressValidationListSelect_inputParameters,TbgnStreetCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/11g'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/11g. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:882) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:715) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:226) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:97) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 71 more
View Log MessagesSaveClose
I checked for Dbadapter process unser soa_server its up and running
Kindly help me
Thank You

Similar Messages

JCA Binding error with FTP Adapter on put operation

Hi
I am facing a problem with put operation with ftp adapter. my soa service will get file from the 1st ftp server (Unix) as attachment and is putting the file on another ftp serve(Unix)r. the put operation is failing with the below error:-
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Error sending file to FTP Server. Error sending file to FTP Server. Unable to send file to server. Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>Unexpected termination: Socket closed</detail></part><part name="code"><code>null</code></part></remoteFault></bpelFault>
this is a SFTP server and the corressponding property is set to true on the configuration. I had also recreated the jndi again & also increased the max connections to 700, but still facing the same issue. Also i am able to ftp the files to this location through filezilla. Also i continously getting the below errors in soa_server1.out:-
<Jul 24, 2012 7:25:11 AM CDT> <Error> <oracle.soa.bpel.engine> <BEA-000000> <Unhandled exception for ComponentDN=default/NShoreAccrualConcService!1.0*soa_9113be23-2e93-4e54-9987-2e8ae5a4b2e6/ProcessNShoreAccurals CompositeInstanceId=330020 ComponentInstanceId=330018>
<Jul 24, 2012 7:25:11 AM CDT> <Error> <oracle.soa.bpel.engine> <BEA-000000> <This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. Root cause :
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Error sending file to FTP Server.
Error sending file to FTP Server.
Unable to send file to server.
Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>Unexpected termination: Socket closed</detail>
,code=<code>null</code>}
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:338)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1059)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
     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:158)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
     at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
     at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:555)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
     at sun.reflect.GeneratedMethodAccessor1687.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.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.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:413)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
     at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
     at sun.reflect.GeneratedMethodAccessor1119.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.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
     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.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
     at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
     at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
     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 $Proxy277.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:35)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
>
<Jul 24, 2012 7:25:11 AM CDT> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <failed to handle message
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Error sending file to FTP Server.
Error sending file to FTP Server.
Unable to send file to server.
Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>

Error itself indicates the potential issues -
Please ensure
1. Specified remote output Dir has write permission
2. Output filename has not exceeded the max chararters allowed by the OS and
3. Remote File System has enough spaceRegards,
Anuj

ORA-03111 - JCA Binding error while invoking a stored procedure in DB

Hi,
We are facing this problem for one interface alone.
Need expert advice to fix this problem..
This is scheduled to run once in a day and fails daily for past 2 weeks..
We receive below error as response..
Same interface worked fine for past 1 yr..
Also it works fine if we reprocess the batch in next day morning...
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DB_Legacy_To_EBS_Invoice_Conversion' failed due to: Stored procedure invocation error. Error while trying to prepare and execute the IRSOA.AR_SOA_INVOICE.TRN_GET_CUST_INV_RAW_TO_STAGE API. An error occurred while preparing and executing the IRSOA.AR_SOA_INVOICE.TRN_GET_CUST_INV_RAW_TO_STAGE API. Cause: java.sql.SQLException: ORA-03111: break received on communication channel ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
AND
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DB_Legacy_To_EBS_Invoice_Conversion' failed due to: Stored procedure invocation error. Error while trying to prepare and execute the IRSOA.AR_SOA_INVOICE.TRN_GET_CUST_INV_RAW_TO_STAGE API. An error occurred while preparing and executing the IRSOA.AR_SOA_INVOICE.TRN_GET_CUST_INV_RAW_TO_STAGE API. Cause: java.sql.SQLException: ORA-01013: user requested cancel of current operation ORA-06512: at "IRSOA.XXIR_AR_SOA_CUSTOMER_INVOICE", line 213 ORA-06512: at line 1 ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution
Thanks,
Sundaram

Looks like the SQL might be taking a longer time to execute and might be timing out.
Please refer the following:
Re: ORA-01013: user requested cancel of current operation
http://www.dba-oracle.com/t_ora_01013_user_requested_cancel_of_current_operation.htm
Additionally, ORA-06512 indicates that there is a mismatch of the with the data length that is being processed. Refer http://www.techonthenet.com/oracle/errors/ora06512.php
Hope this helps.
Thanks,
Patrick

BINDING.JCA-12510 JCA Resource Adapter location error in SOA 11g Suite

Hi,
I am just testing one simple SOA Application in SOA 11g Suite. Created a SOA Composite Application with one DB Adapter at designtime all worked fine with DB Adapter. But when I deploy the Application on the server I get the following error:
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/soademoDatabase'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/soademoDatabase. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ".Do I need to jndi-name in weblogic-ra.xml if so what is the exact location. Any help is appreciated.
Thanks

I did but still not able to connect now getting the following error. I went to the Weblogic Console, clicked on deployments, selected DBAdapter, clicked on configuration ,
and then I don't see outbound configurations instead it shows Outbound Connection Pools, Under Outbound Connection Pools tab I clicked on New and it asked to select Outbound Connection Group I selected the one that was already there (with JNDI eis/DB/SOADemo) and then created my JNDI which was added to the default Outbound Connection Group and in the end it asked to save the Plan.xml which I saved it under a new directory created under soa directory. But still am not able to connect.
How do I create my own Connection Group as don't want to use the defualt one out there.
After creating the JNDI Name it asks for saving the Plan.xml file. Where exactly we save this file. Are there any standards.
Why can't I update any properties when I click on the new JNDI name it takes to Settings for javax.resource.cci.ConnectionFactory --> Outbound Connection Properties but there I see a save buttn but I can't make any changes.
BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception. Missing Property: [DBManagedConnectionFactory.userName]. You may have set a property (in _db.jca) which requires another property to be set also. Make sure the property is set in the interaction (activation) spec by editing its definition in _db.jca. . ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. Is there any documentation that lists all these steps as I couldn't find it anywhere. The guide only talks abou DBAdapter but how to configure etc can't find any info. Any help is appreciated.
Thanks.

Adding new element to BPEL for use in PL SQL type, has binding errors

Figured I might as well post this here since I haven't gotten a single reply in 3 days anywhere else :/
I have a BPEL service that calls a PL SQL procedure. I have added a new element to the BPEL called quote_cart_line.
All I had to the BPEL to accomplish this was edit 3 files -
Async_Invoke_Import_Model.xsd (Source)
<element name="orig_sys_line_ref" type="integer" minOccurs="1" nillable="true"/>
       <element name="quote_cart_line" minOccurs="1" nillable="true" type="integer"/>
      </sequence>
.....APPS_NI_MODEL_IMPORT_UTIL_IMPORT_SELECTIONS.xsd (Target)
<element name="ORIG_SYS_LINE_REF" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
         <element name="QUOTE_CART_LINE" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
      </sequence>
.....Transform_NIE_Inputs.xsl (Transforming from Source to Target)
<ns1:orig_sys_line_ref>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:orig_sys_line_ref"/>
        </ns1:orig_sys_line_ref>
        <ns1:quote_cart_line>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:quote_cart_line"/>
        </ns1:quote_cart_line>
      </ns1:import_line>
.....I have done this to two other BPELs and they work fine. (1st BPEL calls the second BPEL passing this new element, which then passes it to this BPEL I am having trouble with, which then should be binding it to a PL SQL type)
So this BPEL calls a PL SQL procedure, binding the elements from the BPEL to a PL SQL type (ni_model_import_line). So I edited the PL SQL type to accept this new parameter:
orig_sys_header_ref       NUMBER,
       quote_cart_line           NUMBER,
       CONSTRUCTOR FUNCTION ni_model_import_line(p_part_number                IN VARCHAR2,
MEMBER PROCEDURE add_orig_sys_header_ref(p_org_sys_header_ref          IN NUMBER),
       MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER)
MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER) IS
BEGIN
   quote_cart_line := p_quote_cart_line;
END add_quote_cart_line;
END;
.....I invoke all of this, and the new element gets populated in 3 different BPELs, including this one I explained here. But when it comes time to call the PL SQL I am now getting an error:
<fault>
-<bpelFault>
<faultType>0</faultType>
-<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'nie_import_2' failed due to: Interaction processing error.
Error while processing the execution of the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API interaction.
An error occurred while processing the interaction for invoking the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API. Cause: java.lang.NullPointerException
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
</part>
-<part name="detail">
<detail>null</detail>
</part>
-<part name="code">
<code>null</code>
</part>
</bindingFault>
</bpelFault>
</fault>This doesnt happen if I remove the references to this new element and try again, so it obviously is a problem with the element, but I have no idea what it is. It works fine when going from BPEL to BPEL, but as soon as the process tries to call the PL SQL procedure this happens. It is even more frustrating because I have done this exactly before adding another element, and it worked fine...
Any ideas or tips please?

Figured I might as well post this here since I haven't gotten a single reply in 3 days anywhere else :/
I have a BPEL service that calls a PL SQL procedure. I have added a new element to the BPEL called quote_cart_line.
All I had to the BPEL to accomplish this was edit 3 files -
Async_Invoke_Import_Model.xsd (Source)
<element name="orig_sys_line_ref" type="integer" minOccurs="1" nillable="true"/>
       <element name="quote_cart_line" minOccurs="1" nillable="true" type="integer"/>
      </sequence>
.....APPS_NI_MODEL_IMPORT_UTIL_IMPORT_SELECTIONS.xsd (Target)
<element name="ORIG_SYS_LINE_REF" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
         <element name="QUOTE_CART_LINE" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
      </sequence>
.....Transform_NIE_Inputs.xsl (Transforming from Source to Target)
<ns1:orig_sys_line_ref>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:orig_sys_line_ref"/>
        </ns1:orig_sys_line_ref>
        <ns1:quote_cart_line>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:quote_cart_line"/>
        </ns1:quote_cart_line>
      </ns1:import_line>
.....I have done this to two other BPELs and they work fine. (1st BPEL calls the second BPEL passing this new element, which then passes it to this BPEL I am having trouble with, which then should be binding it to a PL SQL type)
So this BPEL calls a PL SQL procedure, binding the elements from the BPEL to a PL SQL type (ni_model_import_line). So I edited the PL SQL type to accept this new parameter:
orig_sys_header_ref       NUMBER,
       quote_cart_line           NUMBER,
       CONSTRUCTOR FUNCTION ni_model_import_line(p_part_number                IN VARCHAR2,
MEMBER PROCEDURE add_orig_sys_header_ref(p_org_sys_header_ref          IN NUMBER),
       MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER)
MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER) IS
BEGIN
   quote_cart_line := p_quote_cart_line;
END add_quote_cart_line;
END;
.....I invoke all of this, and the new element gets populated in 3 different BPELs, including this one I explained here. But when it comes time to call the PL SQL I am now getting an error:
<fault>
-<bpelFault>
<faultType>0</faultType>
-<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'nie_import_2' failed due to: Interaction processing error.
Error while processing the execution of the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API interaction.
An error occurred while processing the interaction for invoking the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API. Cause: java.lang.NullPointerException
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
</part>
-<part name="detail">
<detail>null</detail>
</part>
-<part name="code">
<code>null</code>
</part>
</bindingFault>
</bpelFault>
</fault>This doesnt happen if I remove the references to this new element and try again, so it obviously is a problem with the element, but I have no idea what it is. It works fine when going from BPEL to BPEL, but as soon as the process tries to call the PL SQL procedure this happens. It is even more frustrating because I have done this exactly before adding another element, and it worked fine...
Any ideas or tips please?

Trying to add new elemwent to BPEL, and it is now having binding error

I have a BPEL service that calls a PL SQL procedure. I have added a new element to the BPEL called quote_cart_line.
All I had to the BPEL to accomplish this was edit 3 files -
Async_Invoke_Import_Model.xsd (Source)
<element name="orig_sys_line_ref" type="integer" minOccurs="1" nillable="true"/>
       <element name="quote_cart_line" minOccurs="1" nillable="true" type="integer"/>
      </sequence>
.....APPS_NI_MODEL_IMPORT_UTIL_IMPORT_SELECTIONS.xsd (Target)
<element name="ORIG_SYS_LINE_REF" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
         <element name="QUOTE_CART_LINE" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
      </sequence>
.....Transform_NIE_Inputs.xsl (Transforming from Source to Target)
<ns1:orig_sys_line_ref>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:orig_sys_line_ref"/>
        </ns1:orig_sys_line_ref>
        <ns1:quote_cart_line>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:quote_cart_line"/>
        </ns1:quote_cart_line>
      </ns1:import_line>
.....I have done this to two other BPELs and they work fine. (1st BPEL calls the second BPEL passing this new element, which then passes it to this BPEL I am having trouble with, which then should be binding it to a PL SQL type)
So this BPEL calls a PL SQL procedure, binding the elements from the BPEL to a PL SQL type (ni_model_import_line). So I edited the PL SQL type to accept this new parameter:
orig_sys_header_ref       NUMBER,
       quote_cart_line           NUMBER,
       CONSTRUCTOR FUNCTION ni_model_import_line(p_part_number                IN VARCHAR2,
MEMBER PROCEDURE add_orig_sys_header_ref(p_org_sys_header_ref          IN NUMBER),
       MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER)
MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER) IS
BEGIN
   quote_cart_line := p_quote_cart_line;
END add_quote_cart_line;
END;
.....I invoke all of this, and the new element gets populated in 3 different BPELs, including this one I explained here. But when it comes time to call the PL SQL I am now getting an error:
<fault>
-<bpelFault>
<faultType>0</faultType>
-<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'nie_import_2' failed due to: Interaction processing error.
Error while processing the execution of the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API interaction.
An error occurred while processing the interaction for invoking the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API. Cause: java.lang.NullPointerException
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
</part>
-<part name="detail">
<detail>null</detail>
</part>
-<part name="code">
<code>null</code>
</part>
</bindingFault>
</bpelFault>
</fault>This doesnt happen if I remove the references to this new element and try again, so it obviously is a problem with the element, but I have no idea what it is. It works fine when going from BPEL to BPEL, but as soon as the process tries to call the PL SQL procedure this happens. It is even more frustrating because I have done this exactly before adding another element, and it worked fine...
Any ideas or tips please?
Edited by: 849655 on Aug 9, 2011 2:35 PM
Edited by: 849655 on Aug 9, 2011 2:36 PM

So is there any further info I can provide or anything like that? I am still no closer to solving this it appears...
This makes no sense to me. I have edited these BPELs in this manner twice before and never had problems.
I have 3 bpels. I added the new element to each of them.
BPEL1 - calls some PL SQL and also passess the elements to the next BPEL (BPEL2)
BPEL2 - passes the elements to BPEL 3
BPEL3 - Calls PL SQL in exactly the same way as BPEL1
however, where BPEL 1 is functioning fine, BPEL3 is resulting in the error above. So frustrating, because BPEL3 works exactly like BPEL1, there is no reason it shouldn't be working. The elements are the same order as the PL SQL type and procedure it is mapping to, so that isn't the problem
Edited by: 849655 on Aug 11, 2011 7:51 AM

Error:JCA Binding execute of Reference operation 'writetoBAM' failed

Hi All,
I have two different environment, On which BAM server is installed and configured on both. Both servers has same folder structure for Data Objects. I have created "abc" data object on server1. Implemented sensors in bpel. deployed respective composites on server1, bam sensors works fine. I am able to get data in data object.
Now i have manually created similar data object "abc" on server2 having same column as in "abc" data object on server1. Deployed composites on server2. Now found BAM sensors are not working am not able to get data in "abc" data object on server2
Found error in soa-diagnostic.log :
Exception not handled by the Collaxa Cube system.
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'writetoBAM' failed due to: javax.resource.ResourceException: javax.resource.ResourceException: BAM-06008: The XML payload is invalid; extra contents were found.".
The invoked JCA adapter raised a resource exception.
Please help,
Thanks,
sagar

Found error in naming of data object field id.

"JCA Binding execute of Reference operation 'Write' failed due to: Translation Error.

Hi, i am trying to read a comma delimited file using an inbound file adapter, i have used a mediator to route records to the outbound file adapter.My input.txt file contains 10 records as Fname,Lname.I have used native format builder to generate xsd. To achieve transformation,in the mediator i have mapped only the Fname from source to traget using a for-each loop.I am trying to publish records in the batches of 2 so i have configured inbound file adapter accordingly.My inbound file adapter reads the first two records and the same is visible at the em console mediator instance(payload), i am even able to see the first two records being transformed in the transformed payload in the mediator instance detail but at the outbound file adapter i get an error saying :
Error during invoking 1-way operation "Write" on target service "writeFile"
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Write' failed due to: Translation Error. Translation Error. Error while translating message to native format. Please make sure that the payload for the outbound interaction conforms to the schema. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
When i map both the Fname and Lname in the xsl map file i get the output.But i only need one field at the outfile i:e either the Fname or the Lname.
Given below are the details of the interface:
My Interface Flow:       InboundFileAdapter--------ReadsFile------->Medaitor------Transformation----->OutboundFileAdapter-----writesFile
Input Payload(comma delimited text file) as,
Brad,Pitt
Keanu,Reaves
Martin,Lawrance
Johnny,Depp
etc
etc
Schema definition for payload:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
            xmlns:tns="http://TargetNamespace.com/readFile"
            targetNamespace="http://TargetNamespace.com/readFile"
            elementFormDefault="qualified"
            attributeFormDefault="unqualified"
            nxsd:version="NXSD"
            nxsd:stream="chars"
            nxsd:encoding="US-ASCII">
<xsd:element name="Root-Element">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="Employee" minOccurs="1" maxOccurs="unbounded">
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="Fname" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
              <xsd:element name="Lname" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""" />
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
</xsd:schema>
XSL Map:
<xsl:template match="/">
    <imp1:Root-Element>
      <xsl:for-each select="/imp1:Root-Element/imp1:Employee">
        <imp1:Employee>
          <imp1:Lname>
            <xsl:value-of select="imp1:Lname"/>
          </imp1:Lname>
        </imp1:Employee>
      </xsl:for-each>
    </imp1:Root-Element>
</xsl:template>
</xsl:stylesheet>
Please help me with the above mentioned error and if above transformation is possible using a mediator instead of BPEL
Regards,
Saif

Hi Saif, Are you using the same xsd for the outbound (write) file adapter as well? In that case, you may need to map both the names (Fname and Lname) but leave the name which you do not want to be written to the file as an empty text. For example, if you would need to map only the Lname, but not the Fname, the xsl will be like,
<xsl:template match="/">
    <imp1:Root-Element>
      <xsl:for-each select="/imp1:Root-Element/imp1:Employee">
        <imp1:Employee>
          <imp1:Fname>
          <xsl:text disable-output-escaping="no"></xsl:text>
          </imp1:Fname>
          <imp1:Lname>
            <xsl:value-of select="imp1:Lname"/>
          </imp1:Lname>
        </imp1:Employee>
      </xsl:for-each>
    </imp1:Root-Element>
</xsl:template>
</xsl:stylesheet>
Another option is to have a separate xsd with only one element (Fname or Lname) for the outbound file adapter, in which case you would need to map only one field.

Errors in direct binding invocation from BPEL to OSB

Hi All,
I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
Any help about the management of this situation would be appreciated.
Thanks,
The log trace is the next one:
[component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", 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 "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", 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 "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     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:850)
     at java.lang.Thread.run(Thread.java:662)
And this is the payload from the instance details:
<messages>
<input>
... input data....
</input>
<fault>
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", 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 "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>
</exception>
<root class="oracle.fabric.common.FabricInvocationException">
oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
<stack>
<f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
<f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
<f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
<f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
<f>java.security.AccessController.doPrivileged</f>
<f>javax.security.auth.Subject.doAs#396</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
<f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
<f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
<f>java.lang.reflect.Method.invoke#597</f>
<f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
<f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
<f>...</f>
</stack>
</root>
</fault>
</messages>
Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

Hi All,
I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
Any help about the management of this situation would be appreciated.
Thanks,
The log trace is the next one:
[component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", 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 "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", 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 "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     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:850)
     at java.lang.Thread.run(Thread.java:662)
And this is the payload from the instance details:
<messages>
<input>
... input data....
</input>
<fault>
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", 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 "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>
</exception>
<root class="oracle.fabric.common.FabricInvocationException">
oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
<stack>
<f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
<f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
<f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
<f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
<f>java.security.AccessController.doPrivileged</f>
<f>javax.security.auth.Subject.doAs#396</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
<f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
<f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
<f>java.lang.reflect.Method.invoke#597</f>
<f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
<f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
<f>...</f>
</stack>
</root>
</fault>
</messages>
Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

BPEL 11g Deployment Error Index Out of Bounds

Hiiii all,
Facing an issue while deploying a composite to the SOA Suite 11g. There are no issues when i compile the application.. I donot deploy directly to the app server using jdev , instead deploy it to the jar and deploy to server.
Below the error:
Error during deployment/undeployment: Error occurred during deployment of component: UpdatePINPS to service engine: implementation.bpel for composite: Update: ORABPEL-05250
Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "/usr/wls1033/Oracle/Middleware/user_projects/domains/{domain}/deployed-composites/UpdatePIN_rev1.0/sca_Update_rev1.0/soa_522fc650-7030-46f2-a21f-0177aec0aba4"; the exception reported is: java.lang.IndexOutOfBoundsException: Index: 0 Size: 0
Seeking your help,
Thanks in advance :)

Hi,
I am also gettting same error, any clue for resolving this issue, please

BPEL 11g error consuming UCM SOAP service.

Hi,
Has anyone consumed the search.wsdl from UCM 11g in BPEL or OSB 11g?
Consume search.wsdl from BPEL 11g
Any help would be much appreciated.
Regards,
Shaukat

I'm sorry. I didn't notice.
1) Go to SICF.
2) Click execute.
3) Expand the tree:
sap --> bc --> srt
Make sure that everything in <b>srt</b> is active. You might have to have your Basis team do this.

Issue with Datasource in BPEL 11g

Hi,
I am getting the following error intermittently with the datasource when used in the BPEL process. I already had a look at the forum post A stale Connection Factory or Connection Handle may be used in SOA 11g
The particular settings suggested in the above forum post is already done and still the issue persists. Is there any possibility that database is not allowing these many connections from their end? We have set the maxConnection pool size to 1000 and also tried with modifying the size to 2000.
any pointers for debugging this issue would be appreciated.
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'FetchCustomFenceRingsSelect' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
+EnrichSubscriptionRequestComposite:FetchCustomFenceRings [ FetchCustomFenceRings_ptt::FetchCustomFenceRingsSelect(FetchCustomFenceRingsSelect_inputParameters,FugroringsCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/DB/test3 from JNDI and get a new Connection Handle.+
Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.
+".+
+The invoked JCA adapter raised a resource exception.+
+Please examine the above error message carefully to determine a resolution.+
Thanks!!

Hi,
Do you see its an issue with availbility of connections in the connection pool? the connection pool maximum size is 2000 now and i think its very huge number.
In our BPEL component we have 8 to 9 db adapter calls and number of concurrent requests are very low. So i don't see a reason that bpel component will consumer all these available datasources.
Thanks.

Problem with DB JCA adapter in Soa suite 11g composite appl

i am testing a simple credit card validation composite with Oracle SOA suite 11g11.1.1.4.0, Jdevloper 11.1.1.3.0 and oracle universal XE DB. I am having an exception given below. I have checked that data source is properly configured and appearing at the right place in JNDI tree. Suggestion like 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DBconnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR) has also been tried result is same
**Any suggestion will greatly appreciated .**
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'CreditCardDBServiceSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. CreditCardValidation:CreditCardDBService [ CreditCardDBService_ptt::CreditCardDBServiceSelect(CreditCardDBServiceSelect_inputParameters,CreditcardsCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DBconnection'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DBconnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) 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.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) 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:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) 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.wrapRun(WebAppServletContext.java:3715) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681) 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:2277) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'CreditCardDBServiceSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. CreditCardValidation:CreditCardDBService [ CreditCardDBService_ptt::CreditCardDBServiceSelect(CreditCardDBServiceSelect_inputParameters,CreditcardsCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DBconnection'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DBconnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 79 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'CreditCardDBServiceSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. CreditCardValidation:CreditCardDBService [ CreditCardDBService_ptt::CreditCardDBServiceSelect(CreditCardDBServiceSelect_inputParameters,CreditcardsCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DBconnection'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DBconnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 82 more

Hi,
The JNDI Name to use for the service connection is "eis/DB/soademoDatabase".
This Database is a requirement of the course... (Chapter 4 of Getting Started with Oracle SOA Suite 11g R1 - A Hands-On Tutorial).

Exception occured during invocation of JCA binding ORA-01403: no data found ORA-06512: at line 1

Dear Legends,
My requirement is to call store procedure from BPEL. So for I created a BPEL with 2 assign activity and 1 Invoke activity to Invoke the DB adapter. After Deploying I tested the process but it shows the following error:
<bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DB_SBL_SPROCS1' failed due to: Interaction processing error.
Error while processing the execution of the SIEBEL.PORTAL_SPROCS.ACP_CONREGISTRATIONLOOKUP_WRAP API interaction.
An error occurred while processing the interaction for invoking the SIEBEL.PORTAL_SPROCS.ACP_CONREGISTRATIONLOOKUP_WRAP API. Cause: java.sql.SQLException: ORA-01403: no data found
ORA-06512: at line 1
Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-1403" 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.
</summary></part><part name="detail"><detail>ORA-01403: no data found
ORA-06512: at line 1
</detail></part><part name="code"><code>1403</code></part></bindingFault></bpelFault></fault><faultType>
<message>0</message></faultType></messages></details></event><event sid="BpPrc0.1" cat="2" n="16" date="2013-08-08T05:39:39.121-04:00" type="4"><message>"BPELFault" has not been caught by a catch block.</message></event><event sid="BpPrc0.1" cat="2" n="17" date="2013-08-08T05:39:39.270-04:00" type="3"><message>The transaction was rolled back. The work performed for bpel instance "960968" was rolled back, but the audit trail has been saved for this instance.If this is a sync request, please resubmit the request from the client. If it is an async request, please recover from the recovery console by resubmitting the invoke message.</message></event></audit-trail>
What does the above error says?
1. Whether concern Grant or Execute Privileges is not properly provided to the user?
2. Is there any Dangling Privileges are prevailing?
3. Is that the Store Procedure to be Handled with an Error Handling by means of Exception?
4. Is that I have been giving wrong test data?
5. Is that No data being existing in the Procedure?
6. Is that anything related to XA and NON-XA Data Source?
Any kind of help would be much appreciated. Thanks in Advance.
Thanks,
Karthik

Can you check the following ?
a. Hopefully the when you execute the procedure using sql tool it works fine and returns data.
b. Is there any input parameter available for procedure ?
c. IF yes, is the parameter is mapped with the procedure parameter and populated with value before calling the procedure ?
d. In the audit trial, you can see from the invoke activity to see whether the parameter is populated with value or not ?
e. Check the input parameter by executing the procedure with sql tool to see whether this request is receiving any data in return or not ?
Thanks,
Vijay

Roll back in Adapter DataBase using Polling | BPEL 11g

Hello Guys,
I'm having a problem with roll back for polling "Update a field in Table(Logical Delete)" in DataBase Adapter BPEL 11g.
My process is:
Does polling in the table from the database changed the value in column from 0 for 1 and then put the message on a JMS queue.
The problem is:
When an exception occurs in the process, for example, exception when posting message in the queue, he does not roll back the database, then the value in the table column is changed to 1 and not 0 as it should.
Adapter Data Base:
Oracle XA
Properties BPEL(Composite):
<binding.jca config="XXXX_db.jca">
    <property name="singleton">true</property>
</binding.jca>
<component name="XXXXX" version="2.0">
    <implementation.bpel src="XXXXX.bpel"/>
    <property name="bpel.config.transaction" type="xs:string" many="false">required</property>
    <property name="bpel.config.oneWayDeliveryPolicy">sync</property>
</component>
Properties JCA of Data Base:
<property name="DescriptorName" value="XXXXXXXXX"/>
      <property name="QueryName" value="XXXXXXSelect"/>
      <property name="MappingsMetaDataURL" value="XXXXXX-or-mappings.xml"/>
      <property name="PollingStrategy" value="LogicalDeletePollingStrategy"/>
      <property name="MarkReadColumn" value="STATUS"/>
      <property name="MarkReadValue" value="1"/>
      <property name="MarkReservedValue" value="2${weblogic.Name}-${IP}"/>
      <property name="MarkUnreadValue" value="0"/>
      <property name="PollingInterval" value="5"/>
      <property name="MaxRaiseSize" value="1"/>
      <property name="MaxTransactionSize" value="10"/>
      <property name="NumberOfThreads" value="1"/>
      <property name="ReturnSingleResultSet" value="false"/>
Its roll back?
Could anyone please help me on this.
Tks,
Azevedo, Artur.

You need to ensure that your process is working in a single transaction.
You are correctly using the XA datasource.
Next you need to ensure that you do not have a dehydration point in the process and if there is a call to another BPEL process they are in a same transaction.

JCA binding error in bpel(11g)

Similar Messages

Maybe you are looking for