连接极光异常是什么原因

anthony15
2019-08-02 19:58 1.8k 0

服务端调用极光api接口,大部分情况是正常的,但是中间总会夹杂这连接错误,导致我们数据错乱,不知道是什么原因引起练级异常呢?

```
cn.jiguang.common.resp.APIConnectionException: Connection IO error.
Can not connect to JPush Server. Please ensure your internet connection is ok.
If the problem persists, please let us know at support@jpush.cn.
at cn.jiguang.common.connection.NativeHttpClient._doRequest(NativeHttpClient.java:249) ~[jiguang-common-1.0.9.jar:na]
at cn.jiguang.common.connection.NativeHttpClient.doRequest(NativeHttpClient.java:99) ~[jiguang-common-1.0.9.jar:na]
at cn.jiguang.common.connection.NativeHttpClient.sendGet(NativeHttpClient.java:71) ~[jiguang-common-1.0.9.jar:na]
at cn.jiguang.common.connection.NativeHttpClient.sendGet(NativeHttpClient.java:66) ~[jiguang-common-1.0.9.jar:na]
at cn.jmessage.api.group.GroupClient.getGroupInfo(GroupClient.java:65) ~[jmessage-client-1.1.10.jar:na]
at cn.jmessage.api.JMessageClient.getGroupInfo(JMessageClient.java:363) ~[jmessage-client-1.1.10.jar:na]
at com.yw.jgIm.util.JgImUtil.getGroupInfo(JgImUtil.java:539) ~[yw-message-service-1.0.0-SNAPSHOT.jar:na]
at com.yw.message.service.jgIm.JgImService.checkParam(JgImService.java:133) [yw-message-service-1.0.0-SNAPSHOT.jar:na]
at com.yw.message.service.jgIm.JgImService.sendInvitation(JgImService.java:463) [yw-message-service-1.0.0-SNAPSHOT.jar:na]
at com.yw.message.service.jgIm.JgImService.routePacket(JgImService.java:92) [yw-message-service-1.0.0-SNAPSHOT.jar:na]
at com.yw.message.service.jgIm.JgImService$$FastClassBySpringCGLIB$$11e70dea.invoke() [yw-message-service-1.0.0-SNAPSHOT.jar:na]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) [spring-core-4.3.7.RELEASE.jar:4.3.7.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:721) [spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) [spring-tx-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) [spring-tx-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) [spring-tx-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) [spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:656) [spring-aop-4.3.5.RELEASE.jar:4.3.5.RELEASE]
at com.yw.message.service.jgIm.JgImService$$EnhancerBySpringCGLIB$$e8f6d47d.routePacket() [yw-message-service-1.0.0-SNAPSHOT.jar:na]
at com.yw.message.mq.comsumer.JiGuangImConsumer.onMessage(JiGuangImConsumer.java:35) [yw-message-service-1.0.0-SNAPSHOT.jar:na]
at org.springframework.amqp.rabbit.listener.adapter.MessageListenerAdapter.onMessage(MessageListenerAdapter.java:273) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:778) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:701) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$001(SimpleMessageListenerContainer.java:99) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$1.invokeListener(SimpleMessageListenerContainer.java:191) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.invokeListener(SimpleMessageListenerContainer.java:1213) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.executeListener(AbstractMessageListenerContainer.java:682) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.doReceiveAndExecute(SimpleMessageListenerContainer.java:1191) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.receiveAndExecute(SimpleMessageListenerContainer.java:1175) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$1200(SimpleMessageListenerContainer.java:99) [spring-rabbit-1.6.5.RELEASE.jar:na]
at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.run(SimpleMessageListenerContainer.java:1338) [spring-rabbit-1.6.5.RELEASE.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
Caused by: javax.net.ssl.SSLHandshakeException: server certificate change is restricted during renegotiation
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) ~[na:1.8.0_101]
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) ~[na:1.8.0_101]
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) ~[na:1.8.0_101]
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:292) ~[na:1.8.0_101]
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1471) ~[na:1.8.0_101]
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) ~[na:1.8.0_101]
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) ~[na:1.8.0_101]
at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) ~[na:1.8.0_101]
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) ~[na:1.8.0_101]
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) ~[na:1.8.0_101]
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) ~[na:1.8.0_101]
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) ~[na:1.8.0_101]
at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) ~[na:1.8.0_101]
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) ~[na:1.8.0_101]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513) ~[na:1.8.0_101]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) ~[na:1.8.0_101]
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) ~[na:1.8.0_101]
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) ~[na:1.8.0_101]
at cn.jiguang.common.connection.NativeHttpClient._doRequest(NativeHttpClient.java:166) ~[jiguang-common-1.0.9.jar:na]
... 34 common frames omitted

1个回答

热门排序
  • 你调的是哪一个 API 接口?

    出现连接失败没有获取到信息的时候,你们可以重新调用一下,为何会引起你们数据错乱呢?