I think this is related to issue 4002:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=4002
Which has been fixed in 2.1
What I did to get around this was undeploy my app, then bring the cluster up, disable / enable the jdbc resource and then deploy the application to the cluster.
Depending on the app, sometimes you can just mark it disabled before starting the cluster and just enable it after the jndi resources are available and it may work.
HTH,
Andrew
[Message sent by forum member 'areplogle' (areplogle)]
http://forums.java.net/jive/thread.jspa?messageID=317938