Bug 1163637 - Create a cache and set "locking" and "state-transfer" configuration without restarting a server instance using JON console
Summary: Create a cache and set "locking" and "state-transfer" configuration without r...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: JON Plugin
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 6.5.0
Assignee: William Burns
QA Contact: Martin Gencur
URL:
Whiteboard:
: 1091841 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-13 08:02 UTC by ksuzumur
Modified: 2025-02-10 03:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:43:33 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)

Description ksuzumur 2014-11-13 08:02:35 UTC 
Description of problem:
Our customer wants to create the following cache configuration without restarting a server instance using JON console.

-------------
 <distributed-cache name="test-dist-cache" owners="2" segments="90" l1-lifespan="0" mode="SYNC" remote-timeout="180000" start="EAGER">
    <locking acquire-timeout="60000"/>
    <state-transfer timeout="3600000"/>
  </distributed-cache>
-------------

But we can not set "locking" and "state-transfer" configuration in JON console.

Version-Release number of selected component (if applicable):
jon-server-3.2.0.GA
jboss-datagrid-6.3.1-server      
jon-plugin-pack-eap-3.2.0.GA
jon-plugin-pack-jdg-3.2.0.GA-update-03

Actual results:
There are no the configuration about "locking" and "state-transfer" in JON console.

Expected results:
There are the configuration about "locking" and "state-transfer" in JON console.

Additional info:
Comment 3 Tristan Tarrant 2015-03-25 12:31:08 UTC 
*** Bug 1091841 has been marked as a duplicate of this bug. ***
Comment 4 Red Hat Bugzilla 2025-02-10 03:43:33 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.