Browse Prior Art Database

Reducing Network and Server Load when a Server JMS Queue is Used for Distributing Work across JVMs

IP.com Disclosure Number: IPCOM000220897D
Publication Date: 2012-Aug-14
Document File: 1 page(s) / 20K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method for replacing a Java* Message Service (JMS) queue with an in-memory version is disclosed. In the disclosed method, only one local queue is in use for an agent.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 74% of the total text.

Page 01 of 1

Reducing Network and Server Load when a Server JMS Queue is Used for Distributing Work across JVMs

Current architecture uses a Java* Message Service (JMS) queue for distributing work across Java Virtual Machines (JVMs*). Each unit of work must pass through the JMS queue and as a result puts load on the server and connecting network.

Disclosed is a method for replacing a JMS queue with an in-memory version, wherein only one JVM is in use for an agent. The agent migrates its workload to a shared JMS queue if multiple JVMs are started. When an agent starts, a check is performed to check whether the same agent is already running elsewhere via an existing server registry. If the agent is not running elsewhere, then an agent mode is set to use a local queue. All existing agent logic is then performed in the local queue to execute jobs.

In a scenario, if a JVM1 is found in the server registry for the same agent, then the agent attempts to contact the JVM1. If the agent fails to contact, then the JVM1 is presumed to be dead. This process is repeated for each JVM in the Server Registry. If no agents are alive, then the same agent acts in local mode.

In another scenario, if contact is established with the JVM1, then a new agent informs an existing agent to switch to a shared JMS mode via a Remote Method Invocation (RMI) call. If the existing agent is in local mode, then it will connect to the JMS and migrate its internal work queue to the server registry. All working thre...