strimzi:MirrorMaker2.0连接到IBMEventStream

7gcisfzg  于 2021-06-04  发布在  Kafka
关注(0)|答案(1)|浏览(555)

我用strimzi在kubernetes上配置了Kafka。我试图通过mm2将kafka与ibm eventstream连接起来,但出现了错误。。
任何引起问题的思想和主题
2020-03-09 17:25:40258对/connectors/my cluster source->my-cluster-target.mirrorsourceconnector/config(org.apache.kafka.connect.runtime.rest.errors.connectexceptionmapper)[qtp1584918772-17]com.fasterxml.jackson.databind.exc.missmatchdinputException:无法反序列化的示例 java.lang.String [source:(org.glassfish.jersey.message.internal.readerinterceptorexecutor$uncloseableinputstream)处的启动外\u对象令牌;行:1,列:1335](通过引用链:java.util.linkedhashmap[“targetconnector”]),位于com.fasterxml.jackson.databind.exc.missmatchedInputException.from(missmatchedInputException)。java:59)在com.fasterxml.jackson.databind.deserializationcontext.reportinputmismatch(反序列化上下文)。java:1442)在com.fasterxml.jackson.databind.deserializationcontext.handleunexpectedtoken(反序列化上下文。java:1216)在com.fasterxml.jackson.databind.deserializationcontext.handleunexpectedtoken(反序列化上下文)。java:1126)在com.fasterxml.jackson.databind.deser.std.stringdeserializer.deserialize(stringdeserializer。java:63)在反序列化(stringdeserializer)。java:10)在com.fasterxml.jackson.databind.deser.std.mapdeserializer.\u readandbindstringkeymap(mapdeserializer。java:527)在com.fasterxml.jackson.databind.deser.std.mapdeserializer.deserialize(mapdeserializer。java:364)在com.fasterxml.jackson.databind.deser.std.mapdeserializer.deserialize(mapdeserializer。java:29)在com.fasterxml.jackson.databind.objectreader.\u bind(objectreader。java:1682)在com.fasterxml.jackson.databind.objectreader.readvalue(objectreader。java:977)在com.fasterxml.jackson.jaxrs.base.providerbase.readfrom(providerbase。java:814)在org.glassfish.jersey.message.internal.readerinterceptorexecutor$terminalreaderinterceptor.invokereadfrom(readerinterceptorexecutor)。java:233)在org.glassfish.jersey.message.internal.readerinterceptorexecutor$terminalreaderinterceptor.aroundreadfrom(readerinterceptorexecutor。java:212)在org.glassfish.jersey.message.internal.readerinterceptorexecutor.procedue(readerinterceptorexecutor。java:132)位于org.glassfish.jersey.server.internal.mappableexceptionwrapperinterceptor.aroundreadfrom(mappableexceptionwrapperinterceptor)。java:49)在org.glassfish.jersey.message.internal.readerinterceptorexecutor.procedue(readerinterceptorexecutor。java:132)在org.glassfish.jersey.message.internal.messagebodyfactory.readfrom(messagebodyfactory。java:1067)在org.glassfish.jersey.message.internal.inboundmessagecontext.readentity(inboundmessagecontext。java:850)在org.glassfish.jersey.server.containerrequest.readentity(containerrequest。java:247)在org.glassfish.jersey.server.internal.inject.EntityParamValueProvider$entityvaluesupplier.apply(entityparamvalueparamprovider。java:73)在org.glassfish.jersey.server.internal.inject.EntityParamValueProvider$entityvaluesupplier.apply(EntityParamValueProvider。java:56)在org.glassfish.jersey.server.spi.internal.paramvaluefactorywithsource.apply(paramvaluefactorywithsource。java:50)在org.glassfish.jersey.server.spi.internal.parametervaluehelper.getparametervalues(parametervaluehelper。java:68)位于org.glassfish.jersey.server.model.internal.javaresourcemethoddispatcherprovider$abstractmethodparaminvoker.getparamvalues(javaresourcemethoddispatcherprovider)。java:109)在org.glassfish.jersey.server.model.internal.javaresourcemethoddispatcherprovider$responseoutinvoker.dodispatch(javaresourcemethoddispatcherprovider)。java:176)位于org.glassfish.jersey.server.model.internal.abstractjavaresourcemethoddispatcher.dispatcher(abstractjavaresourcemethoddispatcher)。java:79)在org.glassfish.jersey.server.model.resourcemethodinvoker.invoke(resourcemethodinvoker。java:469)在org.glassfish.jersey.server.model.resourcemethodinvoker.apply(resourcemethodinvoker。java:391)在org.glassfish.jersey.server.model.resourcemethodinvoker.apply(resourcemethodinvoker。java:80)在org.glassfish.jersey.server.serverruntime$1.run(serverruntime。java:253)在org.glassfish.jersey.internal.errors$1.call(errors。java:248)在org.glassfish.jersey.internal.errors$1.call(errors。java:244)在org.glassfish.jersey.internal.errors.process(errors。java:292)在org.glassfish.jersey.internal.errors.process(errors。java:274)在org.glassfish.jersey.internal.errors.process(错误。java:244)在org.glassfish.jersey.process.internal.requestscope.runinscope(requestscope。java:265)位于org.glassfish.jersey.server.serverruntime.process(serverruntime。java:232)位于org.glassfish.jersey.server.applicationhandler.handle(applicationhandler。java:679)在org.glassfish.jersey.servlet.webcomponent.serviceimpl(网络组件。java:392)在org.glassfish.jersey.servlet.webcomponent.service(webcomponent。java:346)在org.glassfish.jersey.servlet.servletcontainer.service(servletcontainer。java:365)在org.glassfish.jersey.servlet.servletcontainer.service(servletcontainer。java:318)在org.glassfish.jersey.servlet.servletcontainer.service(servletcontainer。java:205)位于org.eclipse.jetty.servlet.servletholder.handle(servletholder。java:852)位于org.eclipse.jetty.servlet.servlethandler.dohandle(servlethandler。java:544)位于org.eclipse.jetty.server.handler.scopedhandler.nexthandle(scopedhandler。java:233)在org.eclipse.jetty.server.session.sessionhandler.dohandle(sessionhandler。java:1581)位于org.eclipse.jetty.server.handler.scopedhandler.nexthandle(scopedhandler。java:233)在org.eclipse.jetty.server.handler.contexthandler.dohandle(contexthandler。java:1307)在org.eclipse.jetty.server.handler.scopedhandler.nextscope(scopedhandler。java:188)在org.eclipse.jetty.servlet.servlethandler.doscope(servlethandler。java:482)位于org.eclipse.jetty.server.session.sessionhandler.doscope(sessionhandler。java:1549)在org.eclipse.jetty.server.handler.scopedhandler.nextscope(scopedhandler。java:186)在org.eclipse.jetty.server.handler.contexthandler.doscope(contexthandler。java:1204)在org.eclipse.jetty.server.handler.scopedhandler.handle(scopedhandler。java:141)在org.eclipse.jetty.server.handler.contexthandlercollection.handle(contexthandlercollection。java:221)在org.eclipse.jetty.server.handler.statisticshandler.handle(statisticshandler。java:173)在org.eclipse.jetty.server.handler.handlerwrapper.handle(handlerwrapper。java:127)在org.eclipse.jetty.server.server.handle(server。java:494)位于org.eclipse.jetty.server.httpchannel.handle(httpchannel。java:374)位于org.eclipse.jetty.server.httpconnection.onfillable(httpconnection.org.eclipse.jetty.server.httpconnection.onfillable)。java:268)在org.eclipse.jetty.io.abstractconnection$readcallback.succeeded(abstractconnection。java:311)在org.eclipse.jetty.io.fillinterest.fillable(fillinterest。java:103)在org.eclipse.jetty.io.channelendpoint$2.run(channelendpoint。java:117)在org.eclipse.jetty.util.thread.queuedthreadpool.runjob(queuedthreadpool。java:782)在org.eclipse.jetty.util.thread.queuedthreadpool$runner.run(queuedthreadpool。java:918)在java.lang.thread.run(线程。java:748)

c6ubokkw

c6ubokkw1#

从您共享的日志来看,ibm eventstream似乎无法通过引导路径/入口url进行连接:
org.apache.kafka.connect.runtime.rest.errors.connectexceptionmapper
因此,我的建议是,请检查您在kubernetes上的入口配置,因为我假设您正在尝试访问kubernetes集群的strimzi集群,并确保您可以从本地使用kafka console consumer/producer生成/消费消息,访问k8s中的kafka集群。
如果您使用的是https,请确保在路由/入口url末尾附加443(或8443)端口,并删除在ibm eventstream配置中设置的“https://”作为引导服务器url。

相关问题