Distributing Tasks in a Clustered Application Using JMS

Decoupling and delaying processing in a request-driven environment is one of the key strategies in creating a robust and scalable distributed application. Many services rely on clustering alone to ensure scalability, but they frequently run into trouble when newfound requirements keep application complexity growing.

Reader Feedback: Page 1 of 1

#8	John-Axel Strahlman commented on 10 Sep 2005 The source code for this article has been updated. You can access it by clicking on the source code link below the article. John-Axel
#7	mark sisson commented on 30 Aug 2005 I'm trying to find a download of sample code for this article but only found a SMALL link at the bottom of the article that is a link to a little snipet of code. Is there a full blown example that accompanies this article? It is exactly what I've been looking for !!! Thanks in advance. mark
#6	Charles Steinberg commented on 24 May 2005 John: A question related to the configuration database for WLI 8.1: I am looking for documentation on the sizing of the WLI Database, vs. the Application database. Do you have any information to help establish a baseline?
#5	John-Axel Strahlman commented on 28 Mar 2005 Meir, You need to configure JMS queues and write an MDB that does the asynchronous processing. The framework will only work on an application running on WebLogic Server 6.1 or newer. Drop me an email if you need more specific instructions. The link to the performance guide is missing a slash between products and wlserver, sorry about that. John-Axel
#4	meir commented on 24 Mar 2005 1.try to press on: http://dev2dev.bea.com/productswlserver/whitepapers/WL_JMS_Perform_GD.jsp and no response !!! 2.what kind of weblogic software needed to install? 3.how do i use this code: Listing 3: Framework sample usage DistributedLogger logger = new DistributedLogger(); String text = "Hello asynchronous execution!" logger.setText(text); TaskDistributor.execute( logger, //Command instance 1000, //delay true, //runEverywhere false, //persisted false, //enableXA 4); //delay. i mean from a "main" program that includes "weblogic" classes?
#3	Patricia Thomas commented on 14 Mar 2005 We're also using JMS for several asynchronous tasks, but never thought of using a generic command processor like this. Until now, we have used dedicated queues and MDBs for each task, but this is clearly a better and more manageable solution! Thanks!
#2	John-Axel Strahlman commented on 1 Mar 2005 Yes, all your CommandMessage classes need to be in the classpath of the server (or servers) that does the execution.
#1	Steve Rogers commented on 28 Feb 2005 I assume each new type of CommandMessage, like the DistributedLogger, have to be in the Classpath of the Server. Otherwise, can the serialized objects method be executed?