1
0
-1
1 answer
- 10-1
Hi, looks like the main issue occurs when the 'Internal Server Error' happens. There should be detailed error messages and stacktrace in the logs to indicate the specific cause.
Add your comment...
Hi, looks like the main issue occurs when the 'Internal Server Error' happens. There should be detailed error messages and stacktrace in the logs to indicate the specific cause.
I have a process with an activity followed by a tool where some beanshell logic is put-in. When i run this process, fill the form in the activity and submit, i am getting 'Internal Server Error'. When i open the monitoring tab in designer UI, i see that the activity is stuck in 'open-running' state.
But the strange thing is, i see in the logs that the beanshell tool code is getting executed succesfully, when there is no sign of this tool being run in the monitor tab(The previous activity itself is still stuck in open-running state).
When does this happen? and how to fix this issue?