:test-connection-in-pool fails in a strange way

[11:54:03] <+pilhuhn> maeste hi
[11:54:06] <+pilhuhn> what does this mean:
[11:54:07] <+pilhuhn> [domain@localhost:9999 data-source=lalaDS] :test-connection-in-pool
[11:54:07] <+pilhuhn> {
[11:54:07] <+pilhuhn> "outcome" => "failed",
[11:54:07] <+pilhuhn> "failure-description" => "failed to invoke operation: failed to match pool. Check JndiName: lalaJNDI",
[11:54:57] <+maeste> that jndiName is not matched
[11:55:19] <+pilhuhn> matched by?
[11:55:34] <+maeste> by the runtime connection invoker
[11:55:35] <+pilhuhn> If it is invalid, creation of the datasource should have failed ?
[11:56:01] <+maeste> BTW maybe it'0s a bug when ds name and jndiName are not the same I'll check
[11:56:14] <+pilhuhn> [domain@localhost:9999 data-source=lalaDS] :read-resource
[11:56:14] <+pilhuhn> {
[11:56:14] <+pilhuhn> "outcome" => "success",
[11:56:14] <+pilhuhn> "result" => {
[11:56:14] <+pilhuhn> "background-validation" => undefined,
[11:56:14] <+pilhuhn> "background-validation-minutes" => undefined,
[11:56:14] <+pilhuhn> "blocking-timeout-wait-millis" => undefined,
[11:56:14] <+pilhuhn> "connection-url" => "jdbc:lala",
[11:56:14] <+pilhuhn> "driver-name" => "postgresql-9.0-801.jdbc4.jar",
[11:56:14] <+pilhuhn> "idle-timeout-minutes" => undefined,
[11:56:14] <+pilhuhn> "jndi-name" => "lalaJNDI",
[11:56:38] <+pilhuhn> I did define an invalid connection URL (on purpose)
[11:56:39] <+maeste> yup probably the problem is mine
[11:56:49] <+maeste> I'll have a look this afternoon
[11:57:53] ChanServ sets mode +v Jaikiran
[11:57:54] <+pilhuhn> ok