Package org.gridgain.grid.spi.communication.jms

Contains JMS-based implementation for communication SPI.

See:
Description

Interface Summary

GridJmsCommunicationSpiMBean

Management bean that provides read-only access to the JMS communication SPI configuration.

Class Summary

GridJmsCommunicationSpi

JMS implementation of GridCommunicationSpi.

Package org.gridgain.grid.spi.communication.jms Description

Contains JMS-based implementation for communication SPI. For more information on communication SPI see Communication SPI on Wiki.

Contains Tangosol Coherence implementation for communication SPI.

Note: JMS provider is not shipped with GridGain. If you don't have JMS, you need to download it separately. To download JMS provider see http://en.wikipedia.org/wiki/Java_Message_Service#JMS_Provider_Implementations for more details. Once installed, JMS provider should be available on the classpath for GridGain. If you use [GRIDGAIN_HOME]/bin/gridgain.{sh|bat} script to start a grid node you can simply add JMS JARs to [GRIDGAIN_HOME]/bin/setenv.{sh|bat} scripts that's used to set up class path for the main scripts.

Note: When using JMS-based SPIs (communication or discovery) you cannot start multiple GridGain instances in the same VM due to possible limitations of JMS providers. GridGain runtime will detect this situation and prevent GridGain from starting in such case.

See Also:

Documentation
Email Support
Issue Tracking
Online Forums