Bug 1339313 - Configure Hot Rod client with properties
Summary: Configure Hot Rod client with properties
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.6.1
Assignee: wfink
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1309749 1338942 1357934
TreeView+ depends on / blocked
 
Reported: 2016-05-24 16:29 UTC by wfink
Modified: 2025-02-10 03:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:49:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-6438 0 Major Resolved A Hot Rod client should be able to configure the same properties with hotrod-client.properties file as the programatic A... 2018-06-14 13:58:37 UTC
Red Hat Issue Tracker ISPN-6482 0 Major Resolved Allow to HR client to specify only trustore 2018-06-14 13:58:37 UTC
Red Hat Issue Tracker ISPN-6497 0 Major Resolved SSL cert password has to be same as keystore password 2018-06-14 13:58:37 UTC
Red Hat Issue Tracker JDG-211 0 Major Verified Configure Hot Rod client with properties 2018-06-14 13:58:37 UTC

Description wfink 2016-05-24 16:29:58 UTC 
If a HotRod client is initialized by a hotrod-client.properties file and the RemoteCacheManager() constructor it should be possible to all possible properties.

The properties for

SSL
FILE_STORE *
TRUST_STORE *
are not available with this configuration
Comment 3 wfink 2016-05-30 15:52:21 UTC 
PR send
https://github.com/infinispan/jdg/pull/974
Comment 5 Red Hat Bugzilla 2025-02-10 03:49:02 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.