"error_code": 400,

[ldpiuaeng]

i hava done complete according to the tutorial, but a get
{
"error_code": 400,
"message": "Bad Request"
}
https://github.com/strimzi/strimzi-kafka-bridge/blob/main/documentation/modules/proc-producing-messages-from-bridge-topics-partitions.adoc

[scholzj]

You should probably share the command you run, your Bridge configuration etc.

[ldpiuaeng]

this is my config：
#Bridge related settings
bridge.id=my-bridge

uncomment one the following lines (bridge.tracing) to enable Jaeger tracing, check the documentation how to configure the tracer

OpenTracing support

#bridge.tracing=jaeger

OpenTelemetry support

#bridge.tracing=opentelemetry

#Apache Kafka common
kafka.bootstrap.servers=10.20.16.95:9092

#Apache Kafka producer
kafka.producer.acks=1

#Apache Kafka consumer
kafka.consumer.auto.offset.reset=earliest

#AMQP related settings
amqp.enabled=false
amqp.flowCredit=100
amqp.mode=SERVER
amqp.host=0.0.0.0
amqp.port=5672
amqp.certDir=
amqp.messageConverter=io.strimzi.kafka.bridge.amqp.converter.AmqpDefaultMessageConverter

#HTTP related settings
http.enabled=true
http.host=0.0.0.0
http.port=9080
#Enable CORS
http.cors.enabled=true
http.cors.allowedOrigins=*
http.cors.allowedMethods=GET,POST,PUT,DELETE,OPTIONS,PATCH

this is my rund commong :
curl -X POST http://10.20.16.95:9080/topics/bridge-quickstart-topic -H 'content-type: application/vnd.kafka.json.v2+json' -d '{
"records": [
{
"value": "sales-lead-0002",
"partition": 2
},
{
"value": "sales-lead-0003"
}
]
}'

[scholzj]

What does the bridge log say?

[ldpiuaeng]

this ?

[scholzj]

Just share the full log I guess. Why is the client constantly disconnected? Does the connection to the Kafka broker work?

[ldpiuaeng]

i am sure that the kafka broker is aliving .i dont know why the client constantly disconnected.

and how to check the full log ?

[scholzj]

and how to check the full log ?

That really depends on your enviroment and how you run it.

[autolyticus]

I've been running into the same issue:

$ curl http://kbridge.example.com/topics/los-reisub0-abc           (base) 211ms  Wed Dec  7 02:59:29 2022
{"name":"los-reisub0-abc","configs":{"compression.type":"producer","leader.replication.throttled.replicas":"","message.downconversion.enable":"true","min.insync.replicas":"1","segment.jitter.ms":"0","cleanup.policy":"delete","flush.ms":"9223372036854775807","follower.replication.throttled.replicas":"","segment.bytes":"1073741824","retention.ms":"604800000","flush.messages":"9223372036854775807","message.format.version":"3.0-IV1","max.compaction.lag.ms":"9223372036854775807","file.delete.delay.ms":"60000","max.message.bytes":"1048588","min.compaction.lag.ms":"0","message.timestamp.type":"CreateTime","preallocate":"false","min.cleanable.dirty.ratio":"0.5","index.interval.bytes":"4096","unclean.leader.election.enable":"false","retention.bytes":"-1","delete.retention.ms":"86400000","segment.ms":"604800000","message.timestamp.difference.max.ms":"9223372036854775807","segment.index.bytes":"10485760"},"partitions":[{"partition":0,"leader":0,"replicas":[{"broker":0,"leader":true,"in_sync":true}]}]}

So the connection is clearly fine, however, when attempting to publish some data on the producer

$ curl -XGET \
                                 http://kbridge.example.com/topics/los-reisub0-abc \
                                 -H 'Content-type: application/vnd.kafka.json.v2+json' \
                                 -d '{
                               "records": [
                                  {
                                      "key": "key-1",
                                      "value": "value-1"
                                  },
                                  {
                                      "key": "key-2",
                                      "value": "value-2"
                                  }
                              ]}'

{"error_code":400,"message":"Bad Request"}

Returns the same HTTP Status code 400.

Here are the full logs doesn't look like there's anything too interesting after making the two above requests.
kafka-bridge-bridge-7695dc98b6-t2j78.log

I've deployed on on-prem K3S using Istio as the IngressGateway. Please let me know if you need any more details.

[ppatierno]

I think that this error could be related to this fix (on bridge 0.23.0) #714
My guess is that the content-type is not arriving as it should be to the bridge due to the gateway in the middle? Is that possible? I have never used Istio. So the thing is about checking what is really arriving to the bridge after the gateway.

[autolyticus]

Just remove the cors section under the spec.http one, it will do the trick.

Nope, that's not possible, tried it already. The YAML won't pass validation when running kubectl apply

 kubectl explain kafkabridge.spec.http.cors                                                                                                                      (base) 2403ms  Mon Dec 12 19:49:31 2022
KIND:     KafkaBridge
VERSION:  kafka.strimzi.io/v1beta2

RESOURCE: cors <Object>

DESCRIPTION:
     CORS configuration for the HTTP Bridge.

FIELDS:
   allowedMethods       <[]string> -required-
     List of allowed HTTP methods.

   allowedOrigins       <[]string> -required-
     List of allowed origins. Java regular expressions can be used.

EDIT: Sorry! I just had to delete it first with kubectl delete and recreate the resource with kubectl apply. The validation check seems to be only when updating the resource.

[autolyticus]

Works fine without CORS :D

 curl -X POST \
http://<host>/topics/los-reisub0-abc \
-H 'content-type: application/vnd.kafka.json.v2+json' \
-d '{"records": [{"key": "key-1","value": "value-1"},{"key": "key-2","value": "value-2"}]}'
{"offsets":[{"partition":1,"offset":0},{"partition":1,"offset":1}]}⏎

[ppatierno]

Happy about that! You didn't need CORS in the end but thanks to your "mistake" we found a bug in the bridge :-D

[cgalmarini]

Hi, sorry for posting on this old issue but I'm having this same issue on 0.27 version.
Any ideas about that?

[autolyticus]

I recommend opening a new issue with a detailed description of your setup and linking to this issue in case someone thinks it's relevant