Hi,

We encounter random issues by newly using <<gradlew "ofbiz --shutdown">> instead of, as before, <<gradlew terminateOfibz>> on the demo VM where 3 demos run.

The (small) inconvenience of "gradlew terminateOfibz" is that it kills all the demos started by Gradle (trunk and stable for now). So the lag is longer before they are all restarted.

Moreover the ASF status application

http://status.apache.org/pubsub/manage.cgi

was unable to report the HTTP 500 at

https://demo-trunk.ofbiz.apache.org/catalog/control/main

so it's maybe few days the issue happened (logs are cleared each day, we can't 
know)

I let the OFBiz trunk demo as is for now to ease for the Infra team to fix the 
status app., see

https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-14477

Your devoted

Jacques

Reply via email to