So weblogic clustering is... ehum actually I shouldn't have to say more, but I'm going to anyways. It's a beautiful thing, clustering that is... Weblogic, not so much.
Appearantly there are targeting issues with weblogic clustering. No, not the aim, fire, kill kind of targeting. The kind where you chose on which servers your resources are deployed. It's funny that such a rock solid implementation of an exhaustive and well designed framework would have issues at all, but it does. Resources like portals, connection pools and queues need to not only be deployed correctly and on your server of choice, but rather on a specific pattern including the weblogic admin server in some but not all entries.
Naturally one might wonder how I came of this information. Well the guy who originally set our domain up kinda just shook the box around and was really happy and pleased with the way all the pieces fell out. This today has the side effect of lost session data, class not found exceptions and other problems occuring in such random times and places that halloween seemed more real this year. BEA in their infinite wisdom does have the solution available online, tucked away where only google can find it. Nice that the advanced console has features to detect and repport the very well known configuration errors leading to this issue.
Cluster me sideways, Batman, Weblogic has faults? Not so, little Robin, meerely unimplemented feautures and unfinished bug-fixes.
