September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4752) Implement native getAll/putAll operations in Hot Rod 2.0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4752?page=com.atlassian.jira.plugin.... ] Work on ISPN-4752 stopped by Galder Zamarreño. ---------------------------------------------- > Implement native getAll/putAll operations in Hot Rod 2.0 > -------------------------------------------------------- > > Key: ISPN-4752 > URL: https://issues.jboss.org/browse/ISPN-4752 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Final > > > To help make RemoteCache.getAll() and RemoteCache.putAll() operations more efficient. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4752) Implement native getAll/putAll operations in Hot Rod 2.0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4752?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4752: ----------------------------------- Fix Version/s: 7.1.0.Final (was: 8.0.0.Final) > Implement native getAll/putAll operations in Hot Rod 2.0 > -------------------------------------------------------- > > Key: ISPN-4752 > URL: https://issues.jboss.org/browse/ISPN-4752 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Final > > > To help make RemoteCache.getAll() and RemoteCache.putAll() operations more efficient. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4787) FD_SOCK timeout causing random test failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4787?page=com.atlassian.jira.plugin.... ] Dan Berindei reopened ISPN-4787: -------------------------------- > FD_SOCK timeout causing random test failures > -------------------------------------------- > > Key: ISPN-4787 > URL: https://issues.jboss.org/browse/ISPN-4787 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > When a test doesn't require failure detection, we remove the FD protocol from the JGroups stack, but we keep FD_SOCK. Normally this isn't a problem, but in rare occasions it can fail to open the ping socked and the cluster doesn't form: > {noformat} > 22:51:45,978 DEBUG (testng-GlobalKeySetTaskTest:) [FD_SOCK] NodeA-60950: VIEW_CHANGE received: [NodeA-60950] > 22:51:46,401 DEBUG (Incoming-1,NodeA-60950:) [FD_SOCK] NodeA-60950: VIEW_CHANGE received: [NodeA-60950, NodeB-24360] > 22:51:46,675 DEBUG (FD_SOCK pinger,NodeA-60950:) [FD_SOCK] NodeA-60950: ping_dest is NodeB-24360, pingable_mbrs=[NodeA-60950, NodeB-24360] > 22:51:46,803 DEBUG (testng-GlobalKeySetTaskTest:) [FD_SOCK] NodeB-24360: VIEW_CHANGE received: [NodeA-60950, NodeB-24360] > 22:51:47,149 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: ping_dest is NodeA-60950, pingable_mbrs=[NodeA-60950, NodeB-24360] > 22:51:49,113 WARN (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: creating the client socket failed: java.net.SocketTimeoutException > 22:51:49,116 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: could not create socket to NodeA-60950 (pinger thread is running) > 22:51:49,116 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: suspecting NodeA-60950 > 22:51:49,117 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: ping_dest is null, pingable_mbrs=[NodeB-24360] > 22:51:49,117 DEBUG (INT-2,NodeB-24360:) [FD_SOCK] NodeB-24360: suspecting [NodeA-60950] > 22:51:49,262 DEBUG (Incoming-1,NodeB-24360:) [FD_SOCK] NodeB-24360: VIEW_CHANGE received: [NodeB-24360] > 22:55:49,387 DEBUG (FD_SOCK pinger,NodeA-60950:) [FD_SOCK] 89fe2d3e-0b0a-dae8-a63a-6272ea5b7372: socket to NodeB-24360 was closed gracefully > {noformat} > We should increase {{FD_SOCK.sock_conn_timeout}} and remove FD_SOCK from the stack unless the test uses {{TransportFlags.withMerge()}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4787) FD_SOCK timeout causing random test failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4787?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-4787. -------------------------------- Resolution: Duplicate Issue > FD_SOCK timeout causing random test failures > -------------------------------------------- > > Key: ISPN-4787 > URL: https://issues.jboss.org/browse/ISPN-4787 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > When a test doesn't require failure detection, we remove the FD protocol from the JGroups stack, but we keep FD_SOCK. Normally this isn't a problem, but in rare occasions it can fail to open the ping socked and the cluster doesn't form: > {noformat} > 22:51:45,978 DEBUG (testng-GlobalKeySetTaskTest:) [FD_SOCK] NodeA-60950: VIEW_CHANGE received: [NodeA-60950] > 22:51:46,401 DEBUG (Incoming-1,NodeA-60950:) [FD_SOCK] NodeA-60950: VIEW_CHANGE received: [NodeA-60950, NodeB-24360] > 22:51:46,675 DEBUG (FD_SOCK pinger,NodeA-60950:) [FD_SOCK] NodeA-60950: ping_dest is NodeB-24360, pingable_mbrs=[NodeA-60950, NodeB-24360] > 22:51:46,803 DEBUG (testng-GlobalKeySetTaskTest:) [FD_SOCK] NodeB-24360: VIEW_CHANGE received: [NodeA-60950, NodeB-24360] > 22:51:47,149 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: ping_dest is NodeA-60950, pingable_mbrs=[NodeA-60950, NodeB-24360] > 22:51:49,113 WARN (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: creating the client socket failed: java.net.SocketTimeoutException > 22:51:49,116 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: could not create socket to NodeA-60950 (pinger thread is running) > 22:51:49,116 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: suspecting NodeA-60950 > 22:51:49,117 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: ping_dest is null, pingable_mbrs=[NodeB-24360] > 22:51:49,117 DEBUG (INT-2,NodeB-24360:) [FD_SOCK] NodeB-24360: suspecting [NodeA-60950] > 22:51:49,262 DEBUG (Incoming-1,NodeB-24360:) [FD_SOCK] NodeB-24360: VIEW_CHANGE received: [NodeB-24360] > 22:55:49,387 DEBUG (FD_SOCK pinger,NodeA-60950:) [FD_SOCK] 89fe2d3e-0b0a-dae8-a63a-6272ea5b7372: socket to NodeB-24360 was closed gracefully > {noformat} > We should increase {{FD_SOCK.sock_conn_timeout}} and remove FD_SOCK from the stack unless the test uses {{TransportFlags.withMerge()}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4787) FD_SOCK timeout causing random test failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4787?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-4787. -------------------------------- Resolution: Done Oops, duplicate of ISPN-4560 > FD_SOCK timeout causing random test failures > -------------------------------------------- > > Key: ISPN-4787 > URL: https://issues.jboss.org/browse/ISPN-4787 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > When a test doesn't require failure detection, we remove the FD protocol from the JGroups stack, but we keep FD_SOCK. Normally this isn't a problem, but in rare occasions it can fail to open the ping socked and the cluster doesn't form: > {noformat} > 22:51:45,978 DEBUG (testng-GlobalKeySetTaskTest:) [FD_SOCK] NodeA-60950: VIEW_CHANGE received: [NodeA-60950] > 22:51:46,401 DEBUG (Incoming-1,NodeA-60950:) [FD_SOCK] NodeA-60950: VIEW_CHANGE received: [NodeA-60950, NodeB-24360] > 22:51:46,675 DEBUG (FD_SOCK pinger,NodeA-60950:) [FD_SOCK] NodeA-60950: ping_dest is NodeB-24360, pingable_mbrs=[NodeA-60950, NodeB-24360] > 22:51:46,803 DEBUG (testng-GlobalKeySetTaskTest:) [FD_SOCK] NodeB-24360: VIEW_CHANGE received: [NodeA-60950, NodeB-24360] > 22:51:47,149 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: ping_dest is NodeA-60950, pingable_mbrs=[NodeA-60950, NodeB-24360] > 22:51:49,113 WARN (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: creating the client socket failed: java.net.SocketTimeoutException > 22:51:49,116 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: could not create socket to NodeA-60950 (pinger thread is running) > 22:51:49,116 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: suspecting NodeA-60950 > 22:51:49,117 DEBUG (FD_SOCK pinger,NodeB-24360:) [FD_SOCK] NodeB-24360: ping_dest is null, pingable_mbrs=[NodeB-24360] > 22:51:49,117 DEBUG (INT-2,NodeB-24360:) [FD_SOCK] NodeB-24360: suspecting [NodeA-60950] > 22:51:49,262 DEBUG (Incoming-1,NodeB-24360:) [FD_SOCK] NodeB-24360: VIEW_CHANGE received: [NodeB-24360] > 22:55:49,387 DEBUG (FD_SOCK pinger,NodeA-60950:) [FD_SOCK] 89fe2d3e-0b0a-dae8-a63a-6272ea5b7372: socket to NodeB-24360 was closed gracefully > {noformat} > We should increase {{FD_SOCK.sock_conn_timeout}} and remove FD_SOCK from the stack unless the test uses {{TransportFlags.withMerge()}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4780) Protostream should not require package name on imports

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4780?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-4780: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Protostream should not require package name on imports > ------------------------------------------------------ > > Key: ISPN-4780 > URL: https://issues.jboss.org/browse/ISPN-4780 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > {code:title=file1.proto} > package p; > message A { > optional int32 f1 = 1; > } > {code} > {code:title=file2.proto} > package org.infinispan; > import "file1.proto"; > message B { > required p.A ma = 1; > } > {code} > Does not work since protostream uses the package name + file name to resolve imports -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4790) Protostream must be able to compile the schemas incrementally

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4790?page=com.atlassian.jira.plugin.... ] Work on ISPN-4790 started by Adrian Nistor. ------------------------------------------- > Protostream must be able to compile the schemas incrementally > ------------------------------------------------------------- > > Key: ISPN-4790 > URL: https://issues.jboss.org/browse/ISPN-4790 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > Methods from SerializationContext currently expect a self-contained FileDescriptorSource that has all the needed depencies so it can be parsed and resolved in one go. This limitation should be lifted so users can compile incrementally. Files that cannot be compiled due to missing dependencies should be ignored in current step until future invocations. A callback mechanism could be used to deliver the actual status of the compilation to the caller instead of throwing exceptions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4790) Protostream must be able to compile the schemas incrementally

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4790?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4790: -------------------------------- Status: Open (was: New) > Protostream must be able to compile the schemas incrementally > ------------------------------------------------------------- > > Key: ISPN-4790 > URL: https://issues.jboss.org/browse/ISPN-4790 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > Methods from SerializationContext currently expect a self-contained FileDescriptorSource that has all the needed depencies so it can be parsed and resolved in one go. This limitation should be lifted so users can compile incrementally. Files that cannot be compiled due to missing dependencies should be ignored in current step until future invocations. A callback mechanism could be used to deliver the actual status of the compilation to the caller instead of throwing exceptions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4790) Protostream must be able to compile the schemas incrementally

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-4790: ----------------------------------- Summary: Protostream must be able to compile the schemas incrementally Key: ISPN-4790 URL: https://issues.jboss.org/browse/ISPN-4790 Project: Infinispan Issue Type: Enhancement Components: Remote Querying Affects Versions: 7.0.0.Beta2 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.CR1 Methods from SerializationContext currently expect a self-contained FileDescriptorSource that has all the needed depencies so it can be parsed and resolved in one go. This limitation should be lifted so users can compile incrementally. Files that cannot be compiled due to missing dependencies should be ignored in current step until future invocations. A callback mechanism could be used to deliver the actual status of the compilation to the caller instead of throwing exceptions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4780) Protostream should not require package name on imports

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4780?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4780: -------------------------------- Git Pull Request: https://github.com/infinispan/protostream/pull/7 (was: https://github.com/infinispan/protostream/pulls) > Protostream should not require package name on imports > ------------------------------------------------------ > > Key: ISPN-4780 > URL: https://issues.jboss.org/browse/ISPN-4780 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > {code:title=file1.proto} > package p; > message A { > optional int32 f1 = 1; > } > {code} > {code:title=file2.proto} > package org.infinispan; > import "file1.proto"; > message B { > required p.A ma = 1; > } > {code} > Does not work since protostream uses the package name + file name to resolve imports -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2014