We struggled with a similar problem a couple years ago. In our case the root cause was a bug that was triggered if we set a timeout on a JDBC query and the query took longer than the given timeout. Some sort of problem cleaning up DB resources after the timeout fired. The workaround was to extend or eliminate the timeout, which was not a great answer, but better than an outright crash. The problem is fixed in SQL Anywhere 16. I don't know if SAP ever rolled it into an EBF for version 11.
↧