When that happens can you log in to the console and test the datasource on the one server that has a problem?
Does the log of that server show that datasoruce being deployed?
how can I try?
it's up and bind via JNDI tree.
but application doesn't see the jndi path
It's very strange
If this isn't a regular error, you can try untargeting and retargeting this datasource and retry (I prefer rather restart the server). But if this is a regular error, I suggest you investigate if isn't there another resource with the same jndi name.
It's not a regular error, I've try to re-targetting the JDBC,and isn't present any other JNDI duplicate name.
I solved with re-creation of the server in another machine of the cluster.