I could not agree more that bugs need to be prioritized.
I would have thought an issue that is causing quite a few people problems which is verifiable by a simple search of the forums would justify as at least a bit of priority. A simple search produced 227 results
This bug Shuts down the entire Executor, in many cases never to start again and people complain about it over and over in the forums.
Possibly could you guys have stayed teamed up with the original Activiti group if you are so far behind?
Awww, yes, I’m quite familiar with that document. Here is even a thread I posted almost 4 months ago trying to work through how to enable the debugger.
I might point out this thread is still unanswered to this day.
I’m so familiar with that Support Document after reading it at least a dozen times that I could probably give a Public talk on it.
It has never really helped us solve the issue, so if you guys are under the impression it is a work-around solution for everyone, I not sure it is.
Actually @Niall Your assumption could not be farther from the truth. As I just stated above, I’ve spent months trying to debug this problem with Camunda and hour upon hours searching Support Documents, Forums Posts, StackOverflow, Github, and about everything else I could think of. As mentioned, many of my posts about the subject have gone unanswered.
I have never heard of another option other than the JSoup. I originally did not want to use JSoup since it was an external resource; not internal to Camunda.
Adding more complexity to use External Resources only complicates platforms even more.
A simple search on any of the reviews sites will tell you users think Camunda is Overly Complex already so I wanted to keep things simple and internal.
I assume just about every single person who uses Camunda needs to connect to an external APIs, I wanted to use an internal feature of Camunda thinking it would be more stable. So I must have been wrong there.
@Niall @StephenOTT We are simply going to have to agree to disagree. I have even reread my post and I think it made perfect sense to go back to the source and deal with the person who originally helped diagnose the problem. I did not blame anyone, I simply ask questions of why this LARGE BUG has been ignored, when all my other posts were practically ignored, kinda like the original bug.
On the other hand, you guys seem quick to blame me and not take responsibility for ignoring a HUGE BUG that has cost so many of your loyal followers hours, days, and years of their lives.
@thorben did not seem offended in his response and no offense was meant, though I was trying to be direct.
Obviously, it worked and got your attention.
Please address the gaping wound, stop the bleeding of your loyal users and fix the Job Executor Bug!
It seems so simple, @StephenOTT is quite talented and has done the hard work.