geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3149) Protobuf protocol module will throw exceptions on some input
Date Fri, 10 Nov 2017 19:39:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247960#comment-16247960
] 

ASF GitHub Bot commented on GEODE-3149:
---------------------------------------

dgkimura commented on a change in pull request #148: GEODE-3149: Removing the VectorT.hpp
header file and typedefs
URL: https://github.com/apache/geode-native/pull/148#discussion_r150320949
 
 

 ##########
 File path: clicache/src/LocalRegion.cpp
 ##########
 @@ -893,7 +893,7 @@ namespace Apache
 
         _GF_MG_EXCEPTION_TRY2/* due to auto replace */
 
-        apache::geode::client::VectorOfRegionEntry vc;
+			std::vector<std::shared_ptr<apache::geode::client::RegionEntry>> vc;
 
 Review comment:
   Uhh... I guess we don't have a managed C++ linter, but can you get rid of the spaces you
added here?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Protobuf protocol module will throw exceptions on some input
> ------------------------------------------------------------
>
>                 Key: GEODE-3149
>                 URL: https://issues.apache.org/jira/browse/GEODE-3149
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Brian Rowe
>             Fix For: 1.3.0
>
>
> The protobuf protocol handler needs to be able to handle any input on the incoming socket
without crashing.  
> Right now closing the socket will cause a crash as we try to process a message from the
empty stream (the bug here might be that the server connection shouldn't be trying to process
a message here, but the protocol deserialization still needs to have much better error handling).
> {code:java}
> severe 2017/06/28 13:50:55.565 PDT <ServerConnection on port 22514 Thread 0> tid=0x31]
Uncaught exception in thread Thread[ServerConnection on port 22514 Thread 0,5,ServerConnection
on port 22514]
> java.lang.NullPointerException
> 	at org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.processOneMessage(ProtobufStreamProcessor.java:67)
> 	at org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.receiveMessage(ProtobufStreamProcessor.java:79)
> 	at org.apache.geode.internal.cache.tier.sockets.GenericProtocolServerConnection.doOneMessage(GenericProtocolServerConnection.java:68)
> 	at org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1155)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:552)
> 	at java.lang.Thread.run(Thread.java:748)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message