hession调用json解析异常 com.caucho.hessian.io.HessianProtocolException: expected integer at 0x74 java.util
生活随笔
收集整理的這篇文章主要介紹了
hession调用json解析异常 com.caucho.hessian.io.HessianProtocolException: expected integer at 0x74 java.util
小編覺得挺不錯的,現在分享給大家,幫大家做個參考.
大家好,我是烤鴨:
?? ?采坑實錄,使用hession報錯 expected integer at 0x74 java.util.ArrayList。
1. ?報錯信息如下:
2020-03-18 14:27:48.057 [TID: N/A] [Apollo-RemoteConfigLongPollService-1] ?WARN ?[class:com.ctrip.framework.apollo.internals.RemoteConfigLongPollService | method:doLongPollingRefresh | line:193] logInfo==> Long polling failed, will retry in 16 seconds. appId: etc-manage-service-apply, cluster: default, namespaces: application, long polling url: null, reason: Get config services failed from http://apollo.meta/services/config?appId=etc-manage-service-apply&ip=192.168.xxx.xxx [Cause: Could not complete get operation [Cause: apollo.meta]]com.caucho.hessian.client.HessianRuntimeException: com.caucho.hessian.io.HessianProtocolException: expected integer at 0x74 java.util.ArrayList ([com.alibaba.fastjson.JSONObject, message, 失敗,請求參數錯誤, status])[M] t [\x00\x1fcom.alibaba.fastjson.JSONObject\x07message\x0b\xe6\xa0\xb8\xe9\x94\x80\xe5\xa4\xb1\xe8\xb4\xa5,\xe8\xaf\xb7\xe6\xb1\x82\xe5\x8f\x82\xe6\x95\xb0\xe9\x94\x99\xe8\xaf\xaf\x06status\x011zz]at com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java:222)at com.sun.proxy.$Proxy115.changeCardStatus(Unknown Source)at com.etc.bigcar.CouponTest.testChangeCardStatus(CouponTest.java:34)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)at org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:73)at org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:83)at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)at org.junit.runners.ParentRunner.run(ParentRunner.java:363)at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)at org.junit.runner.JUnitCore.run(JUnitCore.java:137)at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) Caused by: com.caucho.hessian.io.HessianProtocolException: expected integer at 0x74 java.util.ArrayList ([com.alibaba.fastjson.JSONObject, message, 失敗,請求參數錯誤, status])[M] t [\x00\x1fcom.alibaba.fastjson.JSONObject\x07message\x0b\xe6\xa0\xb8\xe9\x94\x80\xe5\xa4\xb1\xe8\xb4\xa5,\xe8\xaf\xb7\xe6\xb1\x82\xe5\x8f\x82\xe6\x95\xb0\xe9\x94\x99\xe8\xaf\xaf\x06status\x011zz]at com.caucho.hessian.io.Hessian2Input.error(Hessian2Input.java:2943)at com.caucho.hessian.io.Hessian2Input.expect(Hessian2Input.java:2880)at com.caucho.hessian.io.Hessian2Input.readInt(Hessian2Input.java:825)at com.caucho.hessian.io.Hessian2Input.readType(Hessian2Input.java:2438)at com.caucho.hessian.io.Hessian2Input.readObject(Hessian2Input.java:1694)at com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java:207)... 33 more2. ?分析
? ?這個錯誤跟服務方無關,可以看到信息已經打印出來了,說明服務方已經返回成功了。是調用方和服務方的版本不一致導致的。
? ?問了服務提供方的hession版本,換了 3.1.6 和寫法,之前沒引入 單獨的 hessian 包,用的dubbo rpc 的初始化bean 的方式。
? ?增加依賴。
?
?
總結
以上是生活随笔為你收集整理的hession调用json解析异常 com.caucho.hessian.io.HessianProtocolException: expected integer at 0x74 java.util的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: Adobe Acrobat XI Pro
- 下一篇: HashMap jdk1.7和1.8概述