Bug with jdbc resources in the Admin Console?
Using Glassfish v2 UR1 on Windows 2003 Server with jdk 1.5.0_06 I've noticed the following on my clustered setup.
After creating the cluster and the jdbc resource, I assign the jdbc resource to the cluster and mark it enabled. Then when I start the cluster and browse the jndi tree from one of the instances within the cluster, the resource doesn't show up.
I have to go to the resource after the cluster is started where its targeting the cluster and its marked enabled, mark it disabled and then enabled again and Only then does it become available to the instances.
I have to do this every time I start the cluster. Does anyone else have this issue?
Sorry for the duplicate I meant to originally post as a question and I thought I could edit my post to be a question. This post can be removed to keep the second.
Message was edited by: areplogle