Invalid JSONRequest: JSONObject[actionname] not found.

2
We encounter a lot of logmessages with this message: Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: Invalid JSONRequest: JSONObject["actionname"] not found. [User 'Anonymous_76de4f61-1bbe-4d39-bf23-e7ef4725e15f' with session id 'a062a7d8-3310-414e-87da-9e31426046d8' and roles 'AnoniemeGebruiker'] Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (1/23) org.json.JSONException: JSONObject["actionname"] not found. Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (2/23) at org.json.JSONObject.get(JSONObject.java:453) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (3/23) at org.json.JSONObject.getString(JSONObject.java:658) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (4/23) at com.mendix.webui.actions.client.ExecuteAction.execute(ExecuteAction.java:56) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (5/23) at com.mendix.webui.requesthandling.ClientRequestHandler$$anonfun$handleRequest$1.apply$mcV$sp(ClientRequestHandler.scala:300) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (6/23) at com.mendix.webui.requesthandling.ClientRequestHandler$$anonfun$handleRequest$1.apply(ClientRequestHandler.scala:293) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (7/23) at com.mendix.webui.requesthandling.ClientRequestHandler$$anonfun$handleRequest$1.apply(ClientRequestHandler.scala:293) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (8/23) at com.mendix.core.session.Worker$$anonfun$receive$3$$anonfun$2$$anon$1.execute(ActionDispatching.scala:151) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (9/23) at com.mendix.util.classloading.Runner.doRunUsingClassLoaderOf(Runner.java:37) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (10/23) at com.mendix.core.session.Worker$$anonfun$receive$3$$anonfun$2.apply(ActionDispatching.scala:153) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (11/23) at scala.util.Try$.apply(Try.scala:191) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (12/23) at com.mendix.core.session.Worker$$anonfun$receive$3.applyOrElse(ActionDispatching.scala:147) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (13/23) at akka.actor.Actor$class.aroundReceive(Actor.scala:465) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (14/23) at com.mendix.core.session.Worker.aroundReceive(ActionDispatching.scala:140) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (15/23) at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (16/23) at akka.actor.ActorCell.invoke(ActorCell.scala:487) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (17/23) at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (18/23) at akka.dispatch.Mailbox.run(Mailbox.scala:220) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (19/23) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (20/23) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (21/23) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (22/23) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) Apr 8 12:24:50 127.0.0.1 tr10000: ERROR - Connector: (23/23) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) Anyone else saw these messages and solved this? I cannot see where is coming from (I don't use any variables with the name actionname)
asked
2 answers
2

Indeed the onclick microflow. It occurs when the formatstring is used in a listview with a onclick MF on this Listview. I stripped the onclick MF out of the widget (because not used). But it should be better fixed in the widget itself. I'll post it also on gitub

answered
0

I've seen this behaviour with, if I'm not mistaken, the checkbox set selector widget where a microflow was triggered on an on change event, while there was no on change microflow configured.

So probably this issue originates from a custom widget. Maybe this helps you in finding the root cause.

answered