In the blog Software is too expensive to build cheaply..." (good blog name BTW), the author mentions his favorite weblogic bug, in a posting about Weblogic 8.1 sp3 being out. I thought that would be a fun thread, what's your favorite weblogic bug? I've been using weblogic since 4.5.1, and it's soooo hard to pick a favorite. Is it the one where putting a non-serialized object in the session in a cluster completely brings all session replication to a halt for all sessions? Perhaps our current 6.1 sp5 problem that causes weblogic to throw null pointer exceptions to anyone trying to log in while realm.refresh() is being called after a new user is added. Or the one that causes the application to revert to the initially deployed exploded .WAR, ignoring any updates that have happened since unless you delete all of the staged content between restarts, whch means your JSP's need to get recompiled again...want to precompile your JSP's? Sorry, there's a bug that causes a time roundoff in the precompiler so weblogic always thinks they are out of date and need precompiling... Deadlocks on connection pool obtaining were also fun.
Hopefully weblogic 8 will fare better for us. Weblogic 4.5.1 started to get really stable right around service pack 12-13...6.1 got pretty good after service pack 4...At least I've always liked BEA for putting full release notes, with the issue number for everything fixed, right on their website.
I'd absolutely go for the non-serialized objects in session bug, seen weblogic going for a grinding halt a couple of times just because they don't check if an object is serializable before distributing it to a remote server. :-)
This is Rob Meyer's weblog, a weblog focused on software development and system administration based on 10 years of experience. Want to explore further? You can find out more me or see the rest of my website.
Wondering if I've written on something in particular? Try searching:
You might want to take a look at some of the more requested postings (as judged by incoming traffic):
Want more? Subscribe to this site 
or contact me at rob at big dis dot com.
See my writings on: