Microcks error: $objectToArray requires a document input, found: missing

[etumwizere21]

Hi everyone,
I'm trying to use Microcks create a mock server from my asyncapi definition file but whenever I upload the file I get this type of error and it does not create mocks though it shows the operations. I'm not sure if I'm missing anything. any thought?

failed to handle {"aggregate" : "service", "pipeline" : [ { "$project" : { "labels" : { "$objectToArray" : "$metadata.labels" } } }, { "$unwind" : "$labels" }, { "$sort" : { "labels.v" : -1 } }, { "$group" : { "_id" : "$labels.k", "values" : { "$addToSet" : "$labels.v" }, "key" : { "$first" : "$labels.k" } } } ], "cursor" : {}, "allowDiskUse" : false, "$db" : "test"}

de.bwaldvogel.mongo.backend.aggregation.Aggregation$PlanExecutorError: [Error 40390] PlanExecutor error during aggregation :: caused by :: $objectToArray requires a document input, found: missing
at de.bwaldvogel.mongo.backend.aggregation.Aggregation.computeResult(Aggregation.java:242)
at de.bwaldvogel.mongo.backend.AbstractMongoDatabase.commandAggregate(AbstractMongoDatabase.java:623)
at de.bwaldvogel.mongo.backend.AbstractMongoDatabase.handleCommand(AbstractMongoDatabase.java:132)
at de.bwaldvogel.mongo.backend.AbstractMongoBackend.handleCommand(AbstractMongoBackend.java:340)
at de.bwaldvogel.mongo.backend.AbstractMongoBackend.handleMessage(AbstractMongoBackend.java:413)
at de.bwaldvogel.mongo.wire.MongoDatabaseHandler.handleMessage(MongoDatabaseHandler.java:73)
at de.bwaldvogel.mongo.wire.MongoDatabaseHandler.channelRead0(MongoDatabaseHandler.java:62)
at de.bwaldvogel.mongo.wire.MongoDatabaseHandler.channelRead0(MongoDatabaseHandler.java:27)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.base@17.0.12/java.lang.Thread.run(Thread.java:840)
at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:915)
at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:890)
Caused by: de.bwaldvogel.mongo.exception.MongoServerError: [Error 40390] $objectToArray requires a document input, found: missing
at de.bwaldvogel.mongo.backend.aggregation.Expression$50.apply(Expression.java:1033)
at de.bwaldvogel.mongo.backend.aggregation.Expression$50.apply(Expression.java:1028)
at de.bwaldvogel.mongo.backend.aggregation.Expression.apply(Expression.java:1746)
at de.bwaldvogel.mongo.backend.aggregation.Expression.evaluateDocumentExpression(Expression.java:1833)
at de.bwaldvogel.mongo.backend.aggregation.Expression.evaluate(Expression.java:1811)
at de.bwaldvogel.mongo.backend.aggregation.Expression.evaluateDocument(Expression.java:1752)
at de.bwaldvogel.mongo.backend.aggregation.stage.ProjectStage.projectDocument(ProjectStage.java:82)
at java.base@17.0.12/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at java.base@17.0.12/java.util.ArrayList$Itr.forEachRemaining(ArrayList.java:1003)
at java.base@17.0.12/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1845)
at java.base@17.0.12/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at java.base@17.0.12/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at java.base@17.0.12/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
at java.base@17.0.12/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
at java.base@17.0.12/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base@17.0.12/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
at de.bwaldvogel.mongo.backend.aggregation.stage.GroupStage.apply(GroupStage.java:43)
at de.bwaldvogel.mongo.backend.aggregation.Aggregation.runStagesAsStream(Aggregation.java:204)
at de.bwaldvogel.mongo.backend.aggregation.Aggregation.runStages(Aggregation.java:196)
at de.bwaldvogel.mongo.backend.aggregation.Aggregation.runStages(Aggregation.java:192)
at de.bwaldvogel.mongo.backend.aggregation.Aggregation.computeResult(Aggregation.java:235)
... 30 common frames omitted

here is our asyncapi definition attached

message_new_v3.zip

[lbroudoux]

Hello @etumwizere21

From what I see you're using the Uber distribution of Microcks. When using this distribution, the stacktrace above is "normal" and due to the embedded striped-down version of MongoDB we're using. For some reason, it fails to aggregate information where no label are present (that's the case where you're starting an instance). Once a label has been put on an API or Service, this error disappears from the logs.

Now it looks like this is not related at all to the import error you encounter. I'll have to take a look at your AsyncAPI file definition to see what's going wrong.

Final thought: using the uber image for doing asynchronous mocks is not the easiest path to go with when starting with Microcks. I would rather recommend using the Docker compose development mode (see https://microcks.io/documentation/guides/installation/docker-compose/#development-mode) for easier startup.

[etumwizere21]

if I understood you well you are saying that I miss
location: $message.payload#/header/vehId_num
right?

[lbroudoux]

Yes exactly!

[etumwizere21]

Hi Laurent,
Now I have the async mock server with kafka working. Thank you so much for your support!
I want to do the POC for async mock server with MQTT since it would be our first preference to use.

referring to your above reply saying:
"
Regarding MQTT, we don't provide an MQTT as such, so you have to use/start one on your own. You used to have https://github.com/microcks/microcks/blob/master/minions/async/artemis.sh for test purpose but I'm not sure what is it's current status. Once you have a MQTT broker running at hand, you then have to edit the config/application.properties under the install/docker-compose folder to tell Microcks how to connect it.

You first have to add MQTT to the list of supported bindings and then add the connection properties like below:
%docker-compose.minion.supported-bindings=KAFKA,WS,MQTT

%docker-compose.mqtt.server=localhost:1883
%docker-compose.mqtt.username=microcks
%docker-compose.mqtt.password=microcks
"
Attached are the screenshots of what I tried by follow your Instructions but I'm unable to read the topic message.
Please advise me what I'm missing, or I misunderstood.
Thank you

[lbroudoux]

Hey @etumwizere21
There are few things to change and check here.

1. You have to declare a MQTT bindings on your AsyncAPI file so that Microcks actually knows it has to connect to a broker and send messages. This can be done applying a binding like in https://github.com/microcks/microcks/blob/master/webapp/src/test/resources/io/github/microcks/util/asyncapi/api-maintenance.async-api-spec.yaml#L17 Beware that the sample if for AsyncAPI 2 and it has to be adapted if using AsyncAPI 3. The reference is here: https://github.com/asyncapi/bindings/tree/master/mqtt . Once this is done, you should see an additional MQTT bindings appear in the service details in Microcks UI.
2. Please check that https://github.com/microcks/microcks/blob/master/minions/async/artemis.sh is actually working on Linux as it is now broken for MacOS (we have to move to another image).
3. From the microcks-async-minion container perspective, the MQTT server is probably not %docker-compose.mqtt.server=localhost:1883 as you're using another container. You might try: to use the MQTT container alias if you started this container within the same docker-compose file / docker network or try host.docker.internal to reach out your host network.

[etumwizere21]

Hi Laurent,
I rely appreciate your support! Thank you so much
I think I have tried to follow your instruction as the attached screenshot shows unless I misunderstood it.

I think the problem I have now is with testing it. like subscribing to see the messages. below is what I was trying but doesn't work. please guide me on how you test it after having the asycaip uploaded.

[lbroudoux]

Hello,
my-mqtt-broker.apps.try.microcks.io is just a placeholder we put as example in the features.properties configuration file. In your case, I think that localhost:1883 would be a better option if your MQTT Explorer application is running as a native application on your host network.

Have you checked the async-minion container logs? Is the connection to Artemis from the minion is ok? Can you see in the logs that it is publishing mock messages on the queues?

[etumwizere21]

Hi Laurent,
Looking at minion logs, it looks like there are connection issues. in the application.properties I tried both %docker-compose.mqtt.server=localhost:1883 and docker-compose.mqtt.server=async-artemis-1 (async-artemis-1 being alias) but none solves the connection issues. below are the screenshot.

With "%docker-compose.mqtt.server=localhost:1883"

Microcks-UI:

minion Running ContainerID:

Minion logs:

With "docker-compose.mqtt.server=async-artemis-1"

MQTT Running container Alias:

Minion running containerID:

Minion error logs:

[lbroudoux]

Are you sure that the async-artemis-1 is actually attached to the same docker network? It is the case when you start all the services from the same docker-compose file but not if you have started it outside... And have you tried with host.docker.internal:1883?

[etumwizere21]

yes I have tried both. attached are screenhorts for host.docker.internal:1883 please let me know if we can have a working session with you anytime. I'm happy to meet what it requires to have a session with you and have this closed if at your end it is working as you expected.

[etumwizere21]

Hi Laurent,
did you get a chance to look at the above ? any feedback?