My issues happened in SOA-P platform.
In this case you could probably open up a support case to get this resolved.
Anyway, if this happens on server start, it sounds like a timing issue - your application being deployed before jbpm.esb which contains the JbpmDS definition. Adding a dependency on this datasource should help to address this.