29, 2017 at 9:15:56 AM UTC+2, Jorg Heymans wrote:
>
>
> On Friday, September 29, 2017 at 1:08:22 AM UTC+2, Kun Zhang wrote:
>>
>>
>>
>> On Wednesday, September 27, 2017 at 4:20:03 AM UTC-7, Jorg Heymans wrote:
>>>
>>> Happy to see this being posted
On Friday, September 29, 2017 at 1:08:22 AM UTC+2, Kun Zhang wrote:
>
>
>
> On Wednesday, September 27, 2017 at 4:20:03 AM UTC-7, Jorg Heymans wrote:
>>
>> Happy to see this being posted. We are running into this as well, it
>> happens once every couple of wee
Happy to see this being posted. We are running into this as well, it
happens once every couple of weeks we have no idea why. Indeed server side
we don't see anything in the logs it's as if nothing is going on. When it
happens we restart the services though, not the client application and it
I would make it explicit and just send a small "connected" message from the
client, along the philosophy of "you're not really connected until you're
able to send a message"
Jorg
On Saturday, April 8, 2017 at 6:37:42 PM UTC+2, Constantine wrote:
>
> Hi :)
>
> I'm using *nodejs* grpc server. My
Hi,
I am wondering what style people are using to define their grpc services.
For example, a service def could be written something like this, in its
most simple form:
syntax = "proto3";
package test;
message Ping {
string theMessage = 1;
}
message Pong {
string theResponse = 1;
}
Indeed the logging revealed in fact an unrelated error during SSL init, thanks
for the hint.
Jorg
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi,
After updating to grpc 1.1.1 it seems that the semantics around using
NameResolver have changed. Basically in our (working) 1.0.3 NameResolver
implementation we were doing this in start() :
Collection serviceInstances =
provider.getAllInstances(); // provider is a
On Thursday, January 26, 2017 at 8:52:54 PM UTC+1, Carl Mastrangelo wrote:
>
> Name resolution happens before the connection, so I'm not sure what you
> mean by "connection in progress". Could you clarify?
>
Well since the authority() returned by the NameResolver is used during
setup of
Small mistake in my mail, the stacktrace is shown clientside NOT
serverside.
Jorg
On Thursday, January 26, 2017 at 1:13:07 PM UTC+1, Jorg Heymans wrote:
>
> Hi,
>
> I have a grpc client-server setup using TLS (ClientAuth.REQUIRE) which is
> working fine. I am now trying to im
Indeed the issue I linked was closed because it was already fixed on master.
Next netty version should have this fix.
Thanks
Jorg
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it,
Hi,
I have been troubleshooting the ALPN error i was getting under a vanilla
spring-boot configuration, using
netty-tcnative-boringssl-static:1.1.33.Fork24 and a plain serverbuilder
with useTransportSecurity.
It turns out that it was caused by the spring-boot-starter-web dependency,
which
11 matches
Mail list logo
