Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

第10章 Run Red Hat JBoss Data Grid in Library Mode (Single-Node Setup)

10.1. Run the Quickstart Class
リンクのコピー

Prerequisites

These quickstarts use the Infinispan quickstarts located at https://github.com/infinispan/infinispan-quickstart. The following procedure uses the infinispan-quickstart/embedded-cache quickstart.

Run the Quickstart Class

  1. Open the Quickstart.java File

    Open the file called Quickstart.java in the infinispan-quickstart/embedded-cache.

  2. Add the Quickstart Class

    Examining the Quickstart.java file we can see that this class creates a DefaultCacheManager and then obtains a local reference to the default cache, as no cache name is specified: 

    package org.infinispan.quickstart.embeddedcache;

import org.infinispan.Cache;
import org.infinispan.manager.DefaultCacheManager;

public class Quickstart {

   public static void main(String args[]) throws Exception {
      Cache<Object, Object> c = new DefaultCacheManager().getCache();
   }

}
    Copy to Clipboard Toggle word wrap

  3. Copy Dependencies and Compile Java Classes

    Use the following command to copy all project dependencies to a directory and compile the Java classes from your project: 

    $ mvn clean compile dependency:copy-dependencies -DstripVersion
    Copy to Clipboard Toggle word wrap

  4. Run the Main Method

    Use the following command to run the main method: 

    $ java -cp target/classes/:target/dependency/* package org.infinispan.quickstart.embeddedcache.Quickstart
    Copy to Clipboard Toggle word wrap

10.2. Use the Default Cache
リンクのコピー

10.2.1. Add and Remove Data from the Cache
リンクのコピー

Red Hat JBoss Data Grid offers an interface that is similar to the proposed JSR-107 API to access and alter data stored in a cache.

The following procedure is an example that defines what each line entered into the DefaultCacheQuickstart.java file does:

Add and Remove Data from the Cache

  1. Add an entry, replacing key and value with the desired key and value: 

    cache.put("key", "value");
    Copy to Clipboard Toggle word wrap

  2. Confirm that the entry is present in the cache: 

    assertEquals(1, cache.size());
assertTrue(cache.containsKey("key"));
    Copy to Clipboard Toggle word wrap

  3. Remove the entry from the cache: 

    Object v = cache.remove("key");
    Copy to Clipboard Toggle word wrap

  4. Confirm that the entry is no longer present in the cache: 

    assertEquals("value", v);
assertTrue(cache.isEmpty());
    Copy to Clipboard Toggle word wrap

10.2.2. Adding and Replacing a Key Value
リンクのコピー

Red Hat JBoss Data Grid offers a thread-safe data structure.

The following procedure is an example that defines what each line entered into the DefaultCacheQuickstart.java file does:

Adding and Replacing a Key Value

  1. Add an entry key with value as the key’s value. 

    cache.put("key", "value");
    Copy to Clipboard Toggle word wrap

Replacing a Key Value.

  1. The following code searches for keys (named key and key2). If the two specific keys beings searched for are not found, JBoss Data Grid creates two new keys with the specified key names and values. 

    cache.putIfAbsent("key", "newValue");
cache.putIfAbsent("key2", "value2");
    Copy to Clipboard Toggle word wrap

  2. The following code confirms that the value of the stored key equals the value we wanted to store. 

    assertEquals(cache.get("key"), "value");
assertEquals(cache.get("key2"), "value2");
    Copy to Clipboard Toggle word wrap

10.2.3. Removing Entries
リンクのコピー

Separate methods are used to remove entries depending on how JBoss Data Grid is used:

Library Mode

All of the following methods are found on org.infinispan.Cache and its subclasses.

  • remove(key) - remove a single key from the cache.
  • removeAsync(key) - remove a single key from the cache, asynchronously.
  • clear() - removes all of the mappings from the cache, leaving it empty once the call completes.
  • clearAsync() - asynchronously remove all of the mappings from the cache, leaving it empty once the call completes.
  • cache.evict(key) - remove the entry from the cache, moving it to the cache store if one is defined. With no cache store defined the entry is removed from the cache and is lost.

Remote Client-Server Mode

All of the following methods are found on org.infinispan.client.hotrod.RemoteCache and its subclasses.

  • remove(key) - remove a single key from the cache.
  • removeAsync(key) - remove a single key from the cache, asynchronously.
  • clear() - removes all of the mappings from the cache, leaving it empty once the call completes.
  • clearAsync() - asynchronously remove all of the mappings from the cache, leaving it empty once the call completes.
  • removeWithVersion(key, version) - remove a single key from the cache only if its current version matches the supplied version.
  • removeWithVersionAsync(key, value) - asynchronously remove a single key from the cache only if its current version matches the supplied version.

For additional information on any of the above methods refer to the API Documentation .

10.2.4. Placing and Retrieving Sets of Data
リンクのコピー

The AdvancedCache and RemoteCache interfaces include methods to either put or get a Map of existing data in bulk. These operations are typically much more efficient than an equivalent sequence of individual operations, especially when using them in server-client mode, as a single network operation occurs as opposed to multiple transactions.

When using the bulk operations the memory overhead is higher during the operation itself, as the get or put operation must accommodate for the full Map in a single execution.

The methods for each class are found below:

  • AdvancedCache:

    • Map<K,V>getAll(Set<?> keys) - returns a Map containing the values associated with the set of keys requested.
    • void putAll(Map<? extends K, ? extends V> map, Metadata metadata) - copies all of the mappings from the specified map to this cache, which takes an instance of Metadata to provide metadata information such as the lifespan, version, etc. on the entries being stored.

  • RemoteCache:

    • Map<K,V>getAll(Set<? extends K> keys) - returns a Map containing the values associated with the set of keys requested.
    • void putAll(Map<? extends K, ? extends V> map) - copies all of the mappings from the specified map to this cache.
    • void putAll(Map<? extends K, ? extends V> map, long lifespan, TimeUnit unit) - copies all of the mappings from the specified map to this cache, along with a lifespan before the entry is expired.
    • void putAll(Map<? extends K, ? extends V> map, long lifespan, TimeUnit lifespanUnit, long maxIdleTime, TimeUnit maxIdleTimeUnit) - copies all of the mappings from the specified map to this cache, along with both a timespan before the entries are expired and the maximum amount of time the entry is allowed to be idle before it is considered to be expired.

10.2.5. Adjust Data Life
リンクのコピー

Red Hat JBoss Data Grid entries are immortal by default, but these settings can be altered.

The following procedure is an example that defines what each line entered into the DefaultCacheQuickstart.java file does:

Adjust the Data Life

  1. Alter the key’s lifespan value: 

    cache.put("key", "value", 5, TimeUnit.SECONDS);
    Copy to Clipboard Toggle word wrap

  2. Check if the cache contains the key: 

    assertTrue(cache.containsKey("key"));
    Copy to Clipboard Toggle word wrap

  3. After the allocated lifespan time has expired, the key is no longer in the cache: 

    Thread.sleep(10000);
assertFalse(cache.containsKey("key"));
    Copy to Clipboard Toggle word wrap

10.2.6. Default Data Mortality
リンクのコピー

As a default, newly created entries do not have a life span or maximum idle time value set. Without these two values, a data entry will never expire and is therefore known as immortal data.

10.2.7. Register the Named Cache Using XML
リンクのコピー

To configure the named cache declaratively (using XML) rather than programmatically, configure the infinispan.xml file.

An example infinispan.xml file is located in https://github.com/jboss-developer/jboss-jdg-quickstarts/ within the secure-embedded-cache/src/main/resources/ folder, and the full schema is available in the docs/schema/ directory of the Red Hat JBoss Data Grid Library distribution.

トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat