we have a full ERP system developed with jBPM ( see press release http://www.camunda.com/pressemeldung.php?newsitem_id=800) and are running with mySQL 4.1.
So I can say, it no problem to work with mySQL (and in the background there is hibernate working which haqs also no real problems with mySQL).
What is your problem with mySQL?
I have no problems with MySQL but just tried to run the JBPM test cases that are in the JBPM starter kit.
Thanks to your feedback, I am more confident now about using JBPM in combination with MySQL.
Nevertheless, I think the JBPM development team should seriously take the time to fix the unit tests. Unit tests that do not work and comments in the readme saying that most cases probably fail to due date/time issues does not really inspire confidence.
There has been extensive testing of various db's (read the sourceforge forums). Could you tell us the
- version of the vm
- version of mysql
- version of jBPM
- which testcases fail
- amount of time you can donate to fix the tests ;-)
Besides this, I agree that it is not good to have these kinds of comments in the code but we work according to priorities. So if you can give us a reason, either via a jira issue with lots of votes, or via commercial support, we'd be happy to change priorities, really.
That reminds me, would jou be so kind to file a jira issue on this with the information requested above? That way we can track the issue.
I have created a task JBPM-437 which provides more details, with a reference to this thread. From what I can see so far, the issue might be purely an issue with cleanup of the database between test cases.
I can spend a little bit of time trying to see how system configuration affects the problem and will add that info to the jira issue as well.
Thanks for replying. I've downgraded it to minor (there is no normal :-( ) since it is not clear what caused this. If it is a real issue on our side (maybe others can run the testcases as well) we'll upgrade it again.