Hi, Victor,
Do you deploy the application to the DAS or to another server instance? It looks like you deploy to an instance, because the error you shared with us contains "Please see
server.log for more details". This is logged on the side, which triggers the deployment, while the actual error happens on a remote server or instance. Usually, you would get this from the asadmin deploy command, the real error is then printed in the DAS server.log. But it seems you got this in the DAS server.log, then I assume DAS tried to deploy on a remote instance, logger the error with "Please see server.log for more details", while the real error is in the server.log of the instance it tried to deploy the application on.
If you want to deploy the application on an instance, the datasource must also be available on the instance. If you created the datasource using the Admin Console, it would automatically add the new JDBC resource to all instances. However, if you followed Hiroki's guide with asadmin commands, the datasource is only available on DAS.
If you want to make it available on an instance named, for example, instance1, you need to run this command too:
asadmin create-resource-ref --target instance1 jdbc/mysql
If you have a cluster of instances, use cluster name instead of instance1.
Ondro