Topic
  • 1 reply
  • Latest Post - ‏2012-04-08T03:20:42Z by mmalc
UserSpanish
UserSpanish
21 Posts

Pinned topic Problems JDBC Adapter integration.

‏2012-03-22T11:42:20Z |
Hi,

I have a doubt. How can I use a JDBC Adapter inside a mediation module? I have made my JDBC Adapter, now, I want to call it in the middle of my mediation module. I've added a service invoke, but it doesn't work good when it's called.

If I emulate the request and response, it works good, but when I disable the emulation, I get a error.

Thank you!
Mediation primitive failure:
Mediation primitive: ServiceInvoke1
Component: EjemploMediacionJDBC
Module: EjemploMediacionJDBC
com.ibm.ws.sibx.mediation.esb.SIBXFireFailTerminalException: CWSXM3713E: Se ha activado el terminal de anomalías en la primitiva de invocación de servicio ServiceInvoke1 de la operación testConFlujoMediacion en el componente de mediación EjemploMediacionJDBC del módulo EjemploMediacionJDBC pero el terminal no está conectado
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.handleUnmodeledFault(ServiceInvokeMediation.java:856)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.handleResponse(ServiceInvokeMediation.java:776)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.invokeFlowAction(ServiceInvokeMediation.java:686)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.mediate(ServiceInvokeMediation.java:576)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:739)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocationWithCatch(JavaMediationPrimitive.java:575)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:395)
at com.ibm.ws.sibx.scax.mediation.engine.SIBXJavaMediationPrimitive.invoke(SIBXJavaMediationPrimitive.java:108)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:344)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:841)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:761)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocationWithCatch(JavaMediationPrimitive.java:575)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:395)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:344)
at com.ibm.ws.sibx.scax.mediation.engine.Input.invoke(Input.java:228)
at com.ibm.ws.sibx.scax.mediation.engine.RequestFlow.invokeFlow(RequestFlow.java:135)
at com.ibm.ws.sibx.scax.mediation.engine.MediationFlow.invokeRequestFlow(MediationFlow.java:168)
at com.ibm.wsspi.sibx.mediation.flow.ejb.MediationFlowBean.invokeRequestFlow(MediationFlowBean.java:292)
at com.ibm.ws.sibx.scax.mediation.component.SIBXMediationFlowComponentImpl.invokeRequestFlow(SIBXMediationFlowComponentImpl.java:135)
at com.ibm.ws.sibx.scax.runtime.handler.MFCImplementationHandler.processMessage(MFCImplementationHandler.java:227)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:755)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1607)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:999)
at com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transactionGlobalActivitySessionAny(UOWNativeWASStrategyImpl.java:853)
at com.ibm.ws.sca.uow.handler.JoinUOWNativeHandler.processMessage(JoinUOWNativeHandler.java:212)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:766)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1607)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:999)
at com.ibm.ws.sca.internal.webmodule.handler.WebModuleContextSwitchHandler.processMessage(WebModuleContextSwitchHandler.java:146)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:766)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1607)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:990)
at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.managedInvoke(Invoker.java:314)
at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.invoke(Invoker.java:194)
at com.ibm.wbit.comptest.controller.invocation.impl.BaseInvocationHandler.invoke(BaseInvocationHandler.java:64)
at com.ibm.wbit.comptest.controller.invocation.impl.InvocationManager.doInvoke(InvocationManager.java:72)
at com.ibm.wbit.comptest.controller.invocation.impl.InvocationManager$1.run(InvocationManager.java:53)
at java.security.AccessController.doPrivileged(AccessController.java:224)
at javax.security.auth.Subject.doAs(Subject.java:495)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:131)
at com.ibm.wbit.comptest.controller.invocation.impl.InvocationManager.invoke(InvocationManager.java:47)
at com.ibm.wbit.comptest.controller.command.impl.BaseCommandHandler.doCommand(BaseCommandHandler.java:61)
at com.ibm.wbit.comptest.controller.command.impl.CommandProcessor.doCommand(CommandProcessor.java:102)
at com.ibm.wbit.comptest.controller.command.impl.CommandProcessor.doCommand(CommandProcessor.java:56)
at com.ibm.wbit.comptest.controller.servlet.TestControllerServlet.process(TestControllerServlet.java:180)
at ...........
Updated on 2012-04-08T03:20:42Z at 2012-04-08T03:20:42Z by mmalc
  • mmalc
    mmalc
    74 Posts

    Re: Problems JDBC Adapter integration.

    ‏2012-04-08T03:20:42Z  
    Unfortunately I can't read what your error message says so I can't be sure what the problem is, however it does seem as though you probably haven't wired up the terminals on the service invoke correctly. Have you got all of the terminals connected? Maybe your getting an error from the JDBC adapter and not handling it correctly.