[JBoss JIRA] (ISPN-3771) HotRod SSL is not working properly with IBM JDKs -- SSLHandshakeException
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3771?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3771:
--------------------------------
Labels: 630 (was: )
> HotRod SSL is not working properly with IBM JDKs -- SSLHandshakeException
> -------------------------------------------------------------------------
>
> Key: ISPN-3771
> URL: https://issues.jboss.org/browse/ISPN-3771
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0.Final
> Environment: Both RHEL x64 and x32 architecture using IBM JDK 6 or IBM JDK 7.
> Test is passing for Open-jdk and Oracle-jdk.
> Reporter: Tomas Sykora
> Assignee: Mircea Markus
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
> Attachments: hotRodSSLibmJDKsProblem
>
>
> For reproducing, run mvn clean verify -Psuite.examples -DfailIfNoTests=false -Dtest=ExampleConfigsTest#testSSLHotRodConfig in Infinispan-server testsuite, using IBM JDK 7.
> See attached file for stack trace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ISPN-3771) HotRod SSL is not working properly with IBM JDKs -- SSLHandshakeException
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3771?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3771:
--------------------------------
Assignee: Martin Gencur (was: Mircea Markus)
> HotRod SSL is not working properly with IBM JDKs -- SSLHandshakeException
> -------------------------------------------------------------------------
>
> Key: ISPN-3771
> URL: https://issues.jboss.org/browse/ISPN-3771
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0.Final
> Environment: Both RHEL x64 and x32 architecture using IBM JDK 6 or IBM JDK 7.
> Test is passing for Open-jdk and Oracle-jdk.
> Reporter: Tomas Sykora
> Assignee: Martin Gencur
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
> Attachments: hotRodSSLibmJDKsProblem
>
>
> For reproducing, run mvn clean verify -Psuite.examples -DfailIfNoTests=false -Dtest=ExampleConfigsTest#testSSLHotRodConfig in Infinispan-server testsuite, using IBM JDK 7.
> See attached file for stack trace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ISPN-3338) DistributionManager operations Locate key & Is key local are not working properly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3338?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3338:
--------------------------------
Labels: 630 (was: )
> DistributionManager operations Locate key & Is key local are not working properly
> ---------------------------------------------------------------------------------
>
> Key: ISPN-3338
> URL: https://issues.jboss.org/browse/ISPN-3338
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Environment: Tested localy Fedora16
> Reporter: Tomas Sykora
> Assignee: Mircea Markus
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> Testing infinispan-rhq-plugin (for InVM).
> DistributionManager operations Locate key & Is key local seem not to working properly. For a nonsense key Locate key operation is returning success with result of a label for cache "home node".
> Is key local operation for nonsense key is returning TRUE which is obviously wrong. This happens even on totally clear, entry-free, cache.
> Operation Could key be affected by a rehash is returning operation success with result false. This is questionable whether it should return failure or not. Again, for nonsense key.
> Please can anyone look at it?
> I don't think this is directly jon/plugin related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ISPN-4000) Delta view logging
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-4000?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-4000:
--------------------------------
Labels: 630 (was: )
> Delta view logging
> ------------------
>
> Key: ISPN-4000
> URL: https://issues.jboss.org/browse/ISPN-4000
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Takayoshi Kimura
> Assignee: Takayoshi Kimura
> Labels: 630
> Fix For: 7.0.0.Alpha1
>
>
> Currently on view change the only log we have is "INFO ISPN000094: Received new cluster view".
> {noformat}
> 11:36:27,355 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) ISPN000094: Received new cluster view: [localhost-7255|23] (24) [localhost-7255, localhost-51221, localhost-12479, localhost-1550, localhost-10300, localhost-11620, localhost-35337, localhost-40886, localhost-3020, localhost-51201, localhost-32626, localhost-17205, localhost-2984, localhost-45021, localhost-23189, localhost-9189, localhost-12902, localhost-38468, localhost-36454, localhost-63088 ...]
> {noformat}
> In a large cluster environment the view list is truncated at max.list.print_size sys prop value, 20 by default. We can increase it but it's still hard to see who is joined/left.
> It would be nice to see the delta on view change, like the following:
> {noformat}
> 11:36:27,355 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) Joined: [localhost-8582], Left: []
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ISPN-4000) Delta view logging
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-4000?page=com.atlassian.jira.plugin.... ]
Mircea Markus reassigned ISPN-4000:
-----------------------------------
Assignee: Mircea Markus (was: Takayoshi Kimura)
> Delta view logging
> ------------------
>
> Key: ISPN-4000
> URL: https://issues.jboss.org/browse/ISPN-4000
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Takayoshi Kimura
> Assignee: Mircea Markus
> Labels: 630
> Fix For: 7.0.0.Alpha1
>
>
> Currently on view change the only log we have is "INFO ISPN000094: Received new cluster view".
> {noformat}
> 11:36:27,355 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) ISPN000094: Received new cluster view: [localhost-7255|23] (24) [localhost-7255, localhost-51221, localhost-12479, localhost-1550, localhost-10300, localhost-11620, localhost-35337, localhost-40886, localhost-3020, localhost-51201, localhost-32626, localhost-17205, localhost-2984, localhost-45021, localhost-23189, localhost-9189, localhost-12902, localhost-38468, localhost-36454, localhost-63088 ...]
> {noformat}
> In a large cluster environment the view list is truncated at max.list.print_size sys prop value, 20 by default. We can increase it but it's still hard to see who is joined/left.
> It would be nice to see the delta on view change, like the following:
> {noformat}
> 11:36:27,355 DEBUG [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,localhost-13545) Joined: [localhost-8582], Left: []
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months