You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2018/01/28 02:40:00 UTC
[jira] [Commented] (SCB-308) Vertx transport server timeout will
cause VertxServerRequestToHttpServletRequest getRemoteAddress
NullPointException
[ https://issues.apache.org/jira/browse/SCB-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342409#comment-16342409 ]
Willem Jiang commented on SCB-308:
----------------------------------
If the server connection is broken, we should not still keep the address there.
I don't think it's a good solution that you keep the address in the ServletRequest even the connection is broken.
> Vertx transport server timeout will cause VertxServerRequestToHttpServletRequest getRemoteAddress NullPointException
> --------------------------------------------------------------------------------------------------------------------
>
> Key: SCB-308
> URL: https://issues.apache.org/jira/browse/SCB-308
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
> Affects Versions: java-chassis-1.0.0-m1
> Reporter: jeho0815
> Assignee: jeho0815
> Priority: Major
>
> VertxServerRequestToHttpServletRequest use the the vertx HttpServerRequest socketAddress, this will call the netty channel to get remote addtess, but server has timeout, so the remote address has been released and return null. so we have to bind the socketaddress to the ServletRequest
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)