http://technology.amis.nl/2012/02/24/ejb-an-mdb-best-practices-on-weblogic/?utm_source=rss&utm_medium=rss&utm_campaign=ejb-an-mdb-best-practices-on-weblogic Tue, 11 Jun 2013 22:09:58 +0000 hourly 1 http://wordpress.org/?v=3.5.1 http://technology.amis.nl/2012/02/24/ejb-an-mdb-best-practices-on-weblogic/#comment-7035 Michel Schildmeijer Fri, 24 Feb 2012 10:42:12 +0000 http://technology.amis.nl/blog/?p=15390#comment-7035 Edwin
These are best practices for programmers of course. I think programmers should be aware and think about were their applications will land on. Also the more applications get a ” production status”, the less knowledge is available from the people ( in this case administrators ). . Of course, applications maybe could work perfectly, but from my experience I see too many times that there wasn’t thought about were and how the apps  are running when they are live, like on what infrastructure, cluster architecture, network architecture. But  It is of course a 2 way track , environment should be configured properly. I forgot to mention but this is about applications on a 10.3.2 platform, not the most stable release of WLS.

]]> http://technology.amis.nl/2012/02/24/ejb-an-mdb-best-practices-on-weblogic/#comment-7034 Edwin Biemond Fri, 24 Feb 2012 10:23:31 +0000 http://technology.amis.nl/blog/?p=15390#comment-7034 Thanks,
I am using a lot of Stateless EJB session bean and have never these problems on a wls cluster. on wls 10.3.4 it works perfectly and the cluster aware stubs are also working fine.
we did a lot of crash tests ( kill -9 and server migrations ) under a heavy load but never lost any transaction.
Maybe these values are now default values.
by the way make sure that they never use Object as datatype on  session bean facade cause this is not serializable

]]>