You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jbpm did not be opened with internal server error(error code: 500) in background running.
Jbpm server and drools guvnor editor was working.
When jbpm editor was opened in client side, any log was not printed in the forever logger.
Reason
The reasons of this issue may be problem of calling server method in meteor or jbpm rest api server is not working. However, the main reason is problem of calling server method in meteor because of symptom 2.
The text was updated successfully, but these errors were encountered:
Symptom
Jbpm did not be opened with internal server error(error code: 500) in background running.
Reason
The reasons of this issue may be problem of calling server method in meteor or jbpm rest api server is not working. However, the main reason is problem of calling server method in meteor because of symptom 2.
The text was updated successfully, but these errors were encountered: