martes, 16 de febrero de 2016

OSB 12c: "No acceptable representation for response..." invoking REST service

Error: No acceptable representation for response with "application/xml; charset=iso-8859-1" media type was found

service> AbstractResponseMessage.getPart, com.bea.alsb.ws.codec.
CodecException: No acceptable representation for response with "application/xml; charset=iso-8859-1" media type was found
com.bea.alsb.ws.codec.CodecException: No acceptable representation for response with "application/xml; charset=iso-8859-1" media type was found
        at com.bea.wli.sb.service.handlerchain.handlers.OutboundRestHandler$AbstractResponseMessage.getPart(OutboundRestHandler.java:373)
        at com.bea.wli.sb.service.handlerchain.handlers.OutboundRestHandler$AbstractResponseMessage.getPart(OutboundRestHandler.java:316)
        at com.bea.alsb.ws.codec.internal.runtime.soap.SoapDocCodec.marshallBody(SoapDocCodec.java:67)
        at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.marshall(SoapCodec.java:147)
        at com.bea.alsb.ws.codec.internal.runtime.soap.SoapDocClientCodec.marshall(SoapDocClientCodec.java:58)
        at com.bea.wli.sb.service.handlerchain.handlers.OutboundRestHandler.handleResponse(OutboundRestHandler.java:208)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
        at com.bea.wli.sb.service.handlerchain.handlers.OutboundMessageContentHandler.handleResponse(OutboundMessageContentHandler.java:89)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
        at com.bea.wli.sb.service.handlerchain.handlers.LoadBalanceFailover$LoadBalanceFailoverHelper.handleResponse(LoadBalanceFailover.java:475)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
        at com.bea.wli.sb.service.handlerchain.handlers.UpdateOutboundStatistics.handleResponse(UpdateOutboundStatistics.java:89)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleResponse(AbstractHandler.java:139)
        at com.bea.wli.sb.service.handlerchain.handlers.EndpointManagementHandler.handleResponse(EndpointManagementHandler.java:122)
        at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$1.handleResponse(AbstractHandler.java:307)
        at com.bea.wli.sb.service.handlerchain.handlers.TransportProviderInvoker$ServiceTransportListener.onReceiveResponse(TransportProviderInvoker.java:302)
        at com.bea.wli.sb.transports.http.wls.rest.RestOutboundMessageContext$Reply.run(RestOutboundMessageContext.java:467)
        at weblogic.work.WorkAreaContextWrap.run(WorkAreaContextWrap.java:55)
        at weblogic.work.ContextWrap.run(ContextWrap.java:40)
        at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:194)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
>

This error can be caused by a mismatch between the type of response you specified in the adapter and the real response the REST service is returning.

For example, if you specified that the service returns HTTP 200 OK with a JSON body, but the service returns just HTTP 200K withouth payload (body).



OSB: 12.1.3


No hay comentarios: