com.bea.alsb.ws.codec.CodecException: No acceptable representation for response with "application/pdf" media type was found

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by tau.eric, 1 year ago
No acceptable representation for response with "application/pdf" media type was found
com.bea.alsb.ws.codec.CodecException: No acceptable representation for response with "application/pdf" 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)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.