Reputation: 85
I'm trying to set up microcks-uber to help with our integration testing locally. I've set up the containers, using VSCode devcontainers like so:
microcks:
image: quay.io/microcks/microcks-uber:1.10.0-native
ports:
- "9090:8080"
environment:
- TEST_CALLBACK_URL=http://microcks:8080
# - ASYNC_MINION_URL=http://microcks-async-minion:8081
volumes:
- "./application.properties:/deployments/config/application.properties"
I'm also using kcat, to try to intertact with the topics: kcat -b microcks:8080 -t PetstoreAsynchronousAPI-1.0.0-receiveNewPetCreateEvent
Using the tutorial schema:
asyncapi: 3.0.0
info:
title: Pets API
version: 1.0.0
description: |-
Petstore API
defaultContentType: application/json
components:
messages:
pet:
payload:
$ref: '#/components/schemas/Pet'
examples:
- name: Zaza
payload:
id: 1
name: Zaza
- name: Tigress
payload:
id: 2
name: Tigress
schemas:
Pet:
type: object
properties:
id:
format: int64
type: integer
name:
type: string
required:
- id
- name
channels:
newPetCreated:
address: new-pet
messages:
newPetCreated:
$ref: '#/components/messages/pet'
operations:
receiveNewPetCreateEvent:
action: receive
channel:
$ref: '#/channels/newPetCreated'
messages:
- $ref: '#/channels/newPetCreated/messages/newPetCreated'
Everytime I try to run the kcat commands, an error is returned Receive failed: Invalid response size 1213486160 (0..100000000): increase receive.message.max.bytes
I've tried adding a application.properties
file containing receive.message.max.bytes=200000000
mounted at deployments/config
as the docs seem to suggest, but this doesn't resolve things.
Are we able to adjust this value in the uber distribution?
Upvotes: 0
Views: 9