weblogic.wsee.codec.CodecException

Failed to decode message

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4

  • via Unknown by ARPL,
  • via Unknown by ARPL,
  • Stack trace

    • weblogic.wsee.codec.CodecException: Failed to decode message at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:188) at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:139) at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:40) at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141) at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114) at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80) at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66) at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44) at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285) at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) 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:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: com.bea.xml.XmlException: unable to find binding type for t|e=getFreightElement|d=getFreightElement@http://sykdev/SYKSBLFRGWebService.wsdl/types/ : [Lsykdev.SykSblSourceLineUser; at com.bea.staxb.runtime.internal.UnmarshalResult.determineBindingType(UnmarshalResult.java:284) at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:222) at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshalType(UnmarshallerImpl.java:127) at weblogic.wsee.bind.runtime.internal.LiteralDeserializerContext.unmarshalType(LiteralDeserializerContext.java:72) at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:172) at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:86) at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeWrappedElement(BaseDeserializerContext.java:135) at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:507) at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:287) at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:172) at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:125) at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:182) ... 26 more Caused by: com.bea.xml.XmlException: unable to find binding type for t|e=getFreightElement|d=getFreightElement@http://sykdev/SYKSBLFRGWebService.wsdl/types/ : [Lsykdev.SykSblSourceLineUser; ... 38 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.