Comments on: Tip: Clustering and your Servlet application http://madbean.com/2003/mb2003-36/ The other kind of micro blog Fri, 03 Sep 2010 09:45:27 +1000 http://wordpress.org/?v=2.8.4 hourly 1 By: Pete http://madbean.com/2003/mb2003-36/comment-page-1/#comment-348 Pete Thu, 26 May 2005 09:01:01 +0000 http://madbean.com/blog/2003-36#comment-348 <p>Absolutely right. I am currently debugging an app that is failing to cluster. I had to use an awk script to process all the java code inserting tests for instanceof java.io.serializable where ever session.setAttribute is invoked, and then test that each object was indeed serializable by writing/reading from a byte buffer. Its a nightmare (this is quite a large app). What suprises me about J2EE - what J2EE really needs - is a J2EE compiler that spots these faults and reports them. The bog ordinary java compiler is a bit thick when it comes to J2EE. I'm scratching my head now wondering how I can comprehensively discover where an object is not being updated with a call to session.setAttribute... it all depends on the paths the app takes through the code. A J2EE compiler could identify which variables were associated with session and warn me that they were being modified without being updated in session. I can't wait for J3EE. J2EE clusters stink :)</p> Absolutely right.
I am currently debugging an app that is failing to cluster. I had to use an awk script to process all the java code inserting
tests for instanceof java.io.serializable where ever session.setAttribute is invoked, and then test that each object was
indeed serializable by writing/reading from a byte buffer. Its a nightmare (this is quite a large app).
What suprises me about J2EE – what J2EE really needs – is a J2EE compiler that spots these faults and reports them. The
bog ordinary java compiler is a bit thick when it comes to J2EE.
I’m scratching my head now wondering how I can comprehensively discover where an object is not being updated with
a call to session.setAttribute… it all depends on the paths the app takes through the code. A J2EE compiler could identify
which variables were associated with session and warn me that they were being modified without being updated in
session.
I can’t wait for J3EE. J2EE clusters stink :)

]]> By: Malcolm Edgar http://madbean.com/2003/mb2003-36/comment-page-1/#comment-93 Malcolm Edgar Tue, 01 Jul 2003 23:37:47 +0000 http://madbean.com/blog/2003-36#comment-93 <p>On this topic there is an interesting article on JavaWorld using Cookies for session state management. I haven't used this, but its an interesting concept.</p> <p>http://www.javaworld.com/javaworld/jw-01-2001/jw-0126-servlets_p.html</p> <p>If you want take this further there is a good Apache commons codec library for doing Base64 encoding of Serialized objects.</p> On this topic there is an interesting article on JavaWorld using Cookies for session state management. I haven’t used this, but its an interesting concept.

http://www.javaworld.com/javaworld/jw-01-2001/jw-0126-servlets_p.html

If you want take this further there is a good Apache commons codec library for doing Base64 encoding of Serialized objects.

]]> By: Cameron Purdy http://madbean.com/2003/mb2003-36/comment-page-1/#comment-92 Cameron Purdy Fri, 27 Jun 2003 20:36:35 +0000 http://madbean.com/blog/2003-36#comment-92 <p>Two words: Tangosol Coherence</p> Two words: Tangosol Coherence

]]>