Bug 906008 - Can't access a non-clustered cache via HotRod
Summary: Can't access a non-clustered cache via HotRod
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER11
: 6.1.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-30 15:45 UTC by Mircea Markus
Modified: 2023-04-01 08:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Due to a bug in the Hot Rod server, non-clustered caches in JBoss Data Grid Server cannot be accessed remotely via Hot Rod. As a result, a NullPointerException is thrown when attempting to read/write data to a non-clustered cache via the Hot Rod protocol. As a workaround, configure the cache as either replicated, distributed or invalidated. After applying this workaround, the cache should be accessible normally via Hot Rod.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2773 0 Blocker Resolved Can't access a non-clustered cache via HotRod 2013-06-26 12:04:18 UTC

Description Mircea Markus 2013-01-30 15:45:28 UTC 
Description of problem:

see ISPN-2773.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Mircea Markus 2013-01-30 15:49:03 UTC 
This was introduced in ISPN 5.2.0.CR2/JGD 6.1 ER9.
As a workaround, one should mark the cache as either replicated,distributed or invalidated.
Comment 4 Martin Gencur 2013-02-20 16:01:03 UTC 
Verified by vchepeli.
Comment 6 Tristan Tarrant 2013-03-13 08:22:18 UTC 
Gemma, this is no longer an issue and should be excluded from the release notes.
Comment 7 gsheldon 2013-03-13 22:59:18 UTC 
Thanks Tristan. Have removed flag and will not included in the 6.1 Release Notes.
Note You need to log in before you can comment on or make changes to this bug.