smallchi / jt809dotnetty Goto Github PK

每天8000w数据，一个月就24亿，主从模式可以承受的住吗？

似乎出现了未处理的异常： 'group.id' configuration parameter is required and was not specified。

请问怎么处理？

版本信息：

os:debian 10
kafka: 2.7.0/kafka_2.13-2.7.0.tgz

Error Message：

kafka@gps:~/Downloads/JT809.GpsConsumer$ sudo dotnet JT809.GpsConsumer.dll
dbug: Microsoft.Extensions.Hosting.Internal.Host[1]
Hosting starting
Unhandled exception. System.ArgumentException: 'group.id' configuration parameter is required and was not specified.
at Confluent.Kafka.Consumer2..ctor(ConsumerBuilder2 builder)
at Confluent.Kafka.ConsumerBuilder2.Build() at JT809.KafkaService.JT809_GpsPosition_Consumer..ctor(IOptions1 consumerConfigAccessor, ILoggerFactory loggerFactory) in D:\smallChi\JT809DotNetty-master\src\JT809.DotNetty.Simples\Superior\JT809.KafkaService\JT809_GpsPosition_Consumer.cs:line 37
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitIEnumerable(IEnumerableCallSite enumerableCallSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.b__0(ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at JT809.GpsConsumer.Program.Main(String[] args) in D:\smallChi\JT809DotNetty-master\src\JT809.DotNetty.Simples\Superior\JT809.GpsConsumer\Program.cs:line 34
at JT809.GpsConsumer.Program.

使用JT809.Inferior.Server 作为服务器
使用JT809.DotNetty.Tcp.Test 作为发送端

是我使用的不对吗？
或是哪里的问题？

我想用先前创建.Net Framework supersocket框架（包括websocket转发）引用JT809DotNetty可行么？请指教简单的调用的用法，该怎么初始化JT809DotNetty呢 谢谢

809协议里面的链路是不是就是一个socket连接啊？根据请求方的请求信息，如果正确，服务端就建立一个标识的连接，如果不正确就断开，这样理解正确么？老大 问下 咱这个框架是单独于supersocket么？ 还会继续更新么？谢谢

JT809.Inferior.Client ：下级平台主 链路为客户端 从链路为服务端
JT809.Superior.Server：上级平台 主链路为服务端 从链路为客户端