[
https://issues.apache.org/jira/browse/GEODE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250457#comment-16250457
]
ASF GitHub Bot commented on GEODE-3149:
---------------------------------------
mhansonp commented on issue #148: GEODE-3149: Removing the VectorT.hpp header
file and typedefs
URL: https://github.com/apache/geode-native/pull/148#issuecomment-344089318
Actually, I think it will be easier to start over. I am working on plan B
approach now that I have more regex powers. I am hoping to have this wrapped up
by the end of the day vs, spending another day or two on the rebase with all
the conflicts.
Thanks,
Mark
> On Nov 13, 2017, at 12:22 PM, Jacob Barrett <[email protected]>
wrote:
>
> @mhansonp <https://github.com/mhansonp> Please resolve merge conflicts
(rebase) and push.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
<https://github.com/apache/geode-native/pull/148#issuecomment-344045796>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AZVB_T-U0UwjHvqycbkBUMYEr87leNWKks5s2KTsgaJpZM4QZ_PV>.
>
----------------------------------------------------------------
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:
[email protected]
> 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)
