Question

Strange microflow error message

0

Hi, I am working on Mendix app which is hosted on Siemens MindSphere. And what to create a MindSphere event and after a couple of seconds I am polling the status of the event. I case the finished state is reached I am requesting the result on a calculation or after a certain time a timeout has occurred. In the development environment everything works as it was planned. But after pushing the app to Mindsphere I get after two or three iterations of the polling loop an error message (“An error occurred, please contact your system administrator”). I have added a lot of log message nodes activities and activated the stack trace node. But I can’t find any indications of an error. The microflow is continues the loop and recognize after some seconds a finished state event and get a valid result. But the page will not be refreshed automatically. The both action options of the object commit activity are activated. It’s possible to the result on the page, but I must sort the data grid widget manually. Does anyone have an idea to solve this issue? Thanks and regards Ingo

asked 2020-02-07

Ingo Bernsdorf

5 answers

Rom van Arendonk · Answer 1 · 2020-02-07

If the polling happens in a microflow which is triggered by a button,it may be a timeout issue. You can solve this by editing the button properties and switching from synchronous to asynchronous. This would also explain why you don’t see an error message in your log: the timeout is client side, while everything on the server works fine.

Ingo Bernsdorf · Answer 2 · 2020-02-10

Hi Rom,

thanks for your hint. I have tried to configure the microflow calling options and set it to asynchronous mode. But the result was a little bit surprising, the error occurred much earlier. But now I can find something in the log file...

Ingo Bernsdorf · Answer 3 · 2020-02-10

ActionManager: Exception in execution of monitored action '{"name":"WindNODEWebApp.MVP_optimizationLoopProcessID_2","type":"Microflow"}' (execution id: 53f5247f-5d51-4bbf-9e20-d51b1a9af7e1, execution type: CLIENT_ASYNC_MONITORED)
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT ERROR - ActionManager: com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.core.CoreException: com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: java.lang.NullPointerException
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at MindSphereSingleSignOn.DS_MindSphereAccessToken (JavaAction : 'GetAccessToken')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at {"name":"MindSphereSingleSignOn.MindSphereAccessTokenConnector","type":"JavaAction"}
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.CreateStartOptimizingEvent (JavaAction : 'Access token')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.MVP_optimizationLoopProcessID_2 (SubMicroflow : 'CreateStartOptimizingEvent')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT Advanced stacktrace:
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.CreateStartOptimizingEvent (JavaAction : 'Access token')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.MVP_optimizationLoopProcessID_2 (SubMicroflow : 'CreateStartOptimizingEvent')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT Advanced stacktrace:ActionManager: Exception in execution of monitored action '{"name":"WindNODEWebApp.MVP_optimizationLoopProcessID_2","type":"Microflow"}' (execution id: 53f5247f-5d51-4bbf-9e20-d51b1a9af7e1, execution type: CLIENT_ASYNC_MONITORED)
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT ERROR - ActionManager: com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.core.CoreException: com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: java.lang.NullPointerException
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at MindSphereSingleSignOn.DS_MindSphereAccessToken (JavaAction : 'GetAccessToken')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at {"name":"MindSphereSingleSignOn.MindSphereAccessTokenConnector","type":"JavaAction"}
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.CreateStartOptimizingEvent (JavaAction : 'Access token')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.MVP_optimizationLoopProcessID_2 (SubMicroflow : 'CreateStartOptimizingEvent')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT Advanced stacktrace:
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.CreateStartOptimizingEvent (JavaAction : 'Access token')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT at WindNODEWebApp.MVP_optimizationLoopProcessID_2 (SubMicroflow : 'CreateStartOptimizingEvent')
2020-02-10T14:09:34.87+0100 [APP/PROC/WEB/0] OUT Advanced stacktrace:

Ingo Bernsdorf · Answer 4 · 2020-02-10

I think, the mindsphere sso connector has some problems with the asynchronous call. I think, the mindsphere sso connector has some problems with the asynchronous call.

Ingo Bernsdorf · Answer 5 · 2020-02-10

Is there a possibility to increase the timeout value for the synchronous call?Is there a possibility to increase the timeout value for the synchronous call?