[JBoss JIRA] (ISPN-6497) SSL cert password has to be same as keystore password
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-6497?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek commented on ISPN-6497:
---------------------------------------
For ISPN server it works, as it uses wildfly realm, where it's implemented correctly
> SSL cert password has to be same as keystore password
> -----------------------------------------------------
>
> Key: ISPN-6497
> URL: https://issues.jboss.org/browse/ISPN-6497
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
>
> Keystore password can be different from certificate private key password stored in the keystore. Currently, when setting up SSL for client - server communication, only keystore password can be configured and thus if keystore has different password than certificate private key, initialization of the keystore fails.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-6497) SSL cert password has to be same as keystore password
by Vojtech Juranek (JIRA)
Vojtech Juranek created ISPN-6497:
-------------------------------------
Summary: SSL cert password has to be same as keystore password
Key: ISPN-6497
URL: https://issues.jboss.org/browse/ISPN-6497
Project: Infinispan
Issue Type: Bug
Components: Configuration, Server
Reporter: Vojtech Juranek
Assignee: Vojtech Juranek
Keystore password can be different from certificate private key password stored in the keystore. Currently, when setting up SSL for client - server communication, only keystore password can be configured and thus if keystore has different password than certificate private key, initialization of the keystore fails.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-6487) Fix typo in faqs 2.6.1
by ted won (JIRA)
[ https://issues.jboss.org/browse/ISPN-6487?page=com.atlassian.jira.plugin.... ]
ted won closed ISPN-6487.
-------------------------
Integrated into master.
> Fix typo in faqs 2.6.1
> ----------------------
>
> Key: ISPN-6487
> URL: https://issues.jboss.org/browse/ISPN-6487
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Core
> Affects Versions: 9.0.0.Alpha1
> Reporter: ted won
> Assignee: ted won
> Priority: Trivial
> Labels: documentation
> Fix For: 9.0.0.Alpha2, 9.0.0.Final
>
> Original Estimate: 1 hour
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> In documentation faqs 2.6.1, there is a typo in one sentence as below, the last word 'modes' should be fixed as 'nodes' to make sense correctly.
> "In a replicated cache all nodes in a cluster hold all keys i.e. if a key exists on one nodes, it will also exist on all other modes."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by Alexandre Nikolov (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
Alexandre Nikolov commented on ISPN-6071:
-----------------------------------------
Forgot to mention: I am running Infinispan 10.0.0.Final with the same problem.
> NullPointerException when executing RemoveExpiredCommand
> --------------------------------------------------------
>
> Key: ISPN-6071
> URL: https://issues.jboss.org/browse/ISPN-6071
> Project: Infinispan
> Issue Type: Bug
> Components: Expiration
> Affects Versions: 8.0.2.Final
> Reporter: Jason Hoetger
> Assignee: William Burns
> Fix For: 9.0.0.Alpha2, 8.1.4.Final, 8.2.2.Final
>
>
> I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
> {noformat}
> ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...]
> ...
> Caused by: java.lang.NullPointerException: null
> at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)
> {noformat}
> Here's RemoveExpiredCommand#setParameters(...):
> {code} @Override
> public void setParameters(int commandId, Object[] args) {
> if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
> int i = 0;
> commandInvocationId = (CommandInvocationId) args[i++];
> key = args[i++];
> value = args[i++];
> lifespan = (long) args[i++];
> }{code}
> Line 142 is the cast of assignment of {{args\[3\]}} to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the {{perform()}} method seems to anticipate null lifespans at line 72:
> {code} // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}{code}
> Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-5776) Restart cluster action
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5776?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-5776:
-------------------------------------------
Since we have already hooked up start/restart cluster op all we have to do here is to notify an admin that for caches that have a cache store configured - data will be loaded. I'll just raise that warning for now! In subsequent iterations, we can warn an admin which specific caches in a particular container deployed on the affected cluster have cache stores configured and will trigger cache store load.
> Restart cluster action
> ----------------------
>
> Key: ISPN-5776
> URL: https://issues.jboss.org/browse/ISPN-5776
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
>
> As an administrator, I want to gracefully restart the cluster. For caches which have a cache-store configured, I want their data to get preloaded without losing any data. Caches which do not have a cache store configured will initially contain no data.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-5775) Clean shutdown cluster action
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5775?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-5775:
-------------------------------------------
Since we have already hooked up stop cluster op all we have to do here is to warn an admin that for caches that do not have a cache store configured - data will be lost. I'll just raise that warning for now! In subsequent iterations, we can warn an admin which specific caches in a particular container deployed on the affected cluster do not have cache store configured.
> Clean shutdown cluster action
> -----------------------------
>
> Key: ISPN-5775
> URL: https://issues.jboss.org/browse/ISPN-5775
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
>
> As an administrator, I want to gracefully shutdown the cluster for maintenance. For caches which have a cache-store configured, I want their data to get persisted without losing any data. For caches that do not have a cache store configured, data will be lost - therefore, I want prior warning before proceeding
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-6487) Fix typo in faqs 2.6.1
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6487?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-6487:
-------------------------------------
Integrated in master. Thanks!
> Fix typo in faqs 2.6.1
> ----------------------
>
> Key: ISPN-6487
> URL: https://issues.jboss.org/browse/ISPN-6487
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Core
> Affects Versions: 9.0.0.Alpha1
> Reporter: ted won
> Assignee: ted won
> Priority: Trivial
> Labels: documentation
> Fix For: 9.0.0.Alpha2, 9.0.0.Final
>
> Original Estimate: 1 hour
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> In documentation faqs 2.6.1, there is a typo in one sentence as below, the last word 'modes' should be fixed as 'nodes' to make sense correctly.
> "In a replicated cache all nodes in a cluster hold all keys i.e. if a key exists on one nodes, it will also exist on all other modes."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months