[JBoss JIRA] (HRJS-32) Cluster iteration tests randomly failing
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-32?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-32:
---------------------------------
Attachment: server-trace-logs.tgz
> Cluster iteration tests randomly failing
> ----------------------------------------
>
> Key: HRJS-32
> URL: https://issues.jboss.org/browse/HRJS-32
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Attachments: server-trace-logs.tgz, tmp-tests.log
>
>
> Example:
> {code}
> ~/0/i/js-client ❯❯❯ rm -drf tmp-tests.log && node node_modules/jasmine-node/lib/jasmine-node/cli.js spec/infinispan_cluster_spec.js --captureExceptions t_domain ✭ ✱
> ....F.....
> Failures:
> 1) Infinispan cluster client can iterate over entries in a cluster
> Message:
> Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it1', value : 'v1', done : false })>.
> Stacktrace:
> Error: Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it1', value : 'v1', done : false })>.
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
> at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
> at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
> at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
> 2) Infinispan cluster client can iterate over entries in a cluster
> Message:
> Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it2', value : 'v2', done : false })>.
> Stacktrace:
> Error: Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it2', value : 'v2', done : false })>.
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
> at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
> at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
> at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
> 3) Infinispan cluster client can iterate over entries in a cluster
> Message:
> Expected { done : true } to equal <jasmine.objectContaining({ key : 'cluster-it3', value : 'v3', done : false })>.
> Stacktrace:
> Error: Expected { done : true } to equal <jasmine.objectContaining({ key : 'cluster-it3', value : 'v3', done : false })>.
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
> at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
> at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
> at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
> Finished in 2.934 seconds
> 10 tests, 38 assertions, 3 failures, 0 skipped
> {code}
> Attached are client TRACE logs and server side TRACE logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-32) Cluster iteration tests randomly failing
by Galder Zamarreño (JIRA)
Galder Zamarreño created HRJS-32:
------------------------------------
Summary: Cluster iteration tests randomly failing
Key: HRJS-32
URL: https://issues.jboss.org/browse/HRJS-32
Project: Infinispan Javascript client
Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Galder Zamarreño
Attachments: tmp-tests.log
Example:
{code}
~/0/i/js-client ❯❯❯ rm -drf tmp-tests.log && node node_modules/jasmine-node/lib/jasmine-node/cli.js spec/infinispan_cluster_spec.js --captureExceptions t_domain ✭ ✱
....F.....
Failures:
1) Infinispan cluster client can iterate over entries in a cluster
Message:
Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it1', value : 'v1', done : false })>.
Stacktrace:
Error: Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it1', value : 'v1', done : false })>.
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
2) Infinispan cluster client can iterate over entries in a cluster
Message:
Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it2', value : 'v2', done : false })>.
Stacktrace:
Error: Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it2', value : 'v2', done : false })>.
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
3) Infinispan cluster client can iterate over entries in a cluster
Message:
Expected { done : true } to equal <jasmine.objectContaining({ key : 'cluster-it3', value : 'v3', done : false })>.
Stacktrace:
Error: Expected { done : true } to equal <jasmine.objectContaining({ key : 'cluster-it3', value : 'v3', done : false })>.
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
Finished in 2.934 seconds
10 tests, 38 assertions, 3 failures, 0 skipped
{code}
Attached are client TRACE logs and server side TRACE logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-32) Cluster iteration tests randomly failing
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-32?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-32:
---------------------------------
Attachment: tmp-tests.log
> Cluster iteration tests randomly failing
> ----------------------------------------
>
> Key: HRJS-32
> URL: https://issues.jboss.org/browse/HRJS-32
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Attachments: tmp-tests.log
>
>
> Example:
> {code}
> ~/0/i/js-client ❯❯❯ rm -drf tmp-tests.log && node node_modules/jasmine-node/lib/jasmine-node/cli.js spec/infinispan_cluster_spec.js --captureExceptions t_domain ✭ ✱
> ....F.....
> Failures:
> 1) Infinispan cluster client can iterate over entries in a cluster
> Message:
> Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it1', value : 'v1', done : false })>.
> Stacktrace:
> Error: Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it1', value : 'v1', done : false })>.
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
> at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
> at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
> at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
> 2) Infinispan cluster client can iterate over entries in a cluster
> Message:
> Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it2', value : 'v2', done : false })>.
> Stacktrace:
> Error: Expected { done : true, key : 'cluster-it1', value : 'v1' } to equal <jasmine.objectContaining({ key : 'cluster-it2', value : 'v2', done : false })>.
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
> at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
> at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
> at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
> 3) Infinispan cluster client can iterate over entries in a cluster
> Message:
> Expected { done : true } to equal <jasmine.objectContaining({ key : 'cluster-it3', value : 'v3', done : false })>.
> Stacktrace:
> Error: Expected { done : true } to equal <jasmine.objectContaining({ key : 'cluster-it3', value : 'v3', done : false })>.
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:274:43
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:503:39
> at Function._.map._.collect (/Users/g/0/infinispan/js-client/node_modules/underscore/underscore.js:172:24)
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:500:7
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:493:42
> at /Users/g/0/infinispan/js-client/spec/utils/testing.js:443:50
> at tryCallOne (/Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:37:12)
> at /Users/g/0/infinispan/js-client/node_modules/promise/lib/core.js:103:15
> Finished in 2.934 seconds
> 10 tests, 38 assertions, 3 failures, 0 skipped
> {code}
> Attached are client TRACE logs and server side TRACE logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7330) Administration console - cannot edit configuration twice without refresh
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7330?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic reassigned ISPN-7330:
-----------------------------------------
Assignee: Vladimir Blagojevic
> Administration console - cannot edit configuration twice without refresh
> ------------------------------------------------------------------------
>
> Key: ISPN-7330
> URL: https://issues.jboss.org/browse/ISPN-7330
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
>
> Steps to reproduce:
> Go to cache configuration -> e.g. Locking tab -> edit some of the settings like "Acquire Timeout" -> Apply changes -> confirm everything. Now stay still on the page and edit the e.g. Isolation level -> Apply changes and you get an error:
> {code}
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-5":"WFLYCTL0212: Duplicate resource [\n (\"profile\" => \"clustered\"),\n (\"subsystem\" => \"datagrid-infinispan\"),\n (\"cache-container\" => \"clustered\"),\n (\"configurations\" => \"CONFIGURATIONS\"),\n (\"replicated-cache-configuration\" => \"replicatedCache\"),\n (\"eviction\" => \"EVICTION\")\n]"}}
> {code}
> I haven't clicked through the whole UI, but it seems that it's also in other tabs. Also I'm not sure if it's related only in changes in SELECTs or also in INPUTs, sometimes I was very confused what's going on.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7331) Administration console - removing task before undeploying it should show an error
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7331?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic reassigned ISPN-7331:
-----------------------------------------
Assignee: Vladimir Blagojevic
> Administration console - removing task before undeploying it should show an error
> ---------------------------------------------------------------------------------
>
> Key: ISPN-7331
> URL: https://issues.jboss.org/browse/ISPN-7331
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Attachments: local-task.jar
>
>
> Steps to reproduce:
> Go to cache container -> Configuration -> Deployments -> upload some task (you can use the one in attachment) -> Deploy the task -> try clicking Remove
> The task is correctly not removed, since it's not undeployed yet. However, there used to be a popup windows which showed, why the task could not be removed. I think it should be put back since it's much more user-friendly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7332) XSite trying to replicate to site after site has been shutdown
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7332?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7332:
-----------------------------------
Attachment: xsite-bug.tgz
> XSite trying to replicate to site after site has been shutdown
> --------------------------------------------------------------
>
> Key: ISPN-7332
> URL: https://issues.jboss.org/browse/ISPN-7332
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.0.0.Beta1
> Reporter: Galder Zamarreño
> Attachments: xsite-bug.tgz
>
>
> In a 2-site scenario, with a server in each site, when the server in one of the sites goes down, and as a result the entire site is gone, the initial site might still try to replicate to the other site. Example:
> Sites: EARTH and MOON
> Servers: server-earth-one and server-moon-one respectively
> server-moon-one stops:
> {code}
> 2017-01-04 12:16:38,666 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050:
> Infinispan Server 9.0.0.Beta1 (WildFly Core 2.2.0.Final) stopped in 102ms
> {code}
> server-earth-one realises that and sets the correct view:
> {code}
> 2017-01-04 12:16:38,649 TRACE [org.jgroups.protocols.relay.RELAY2] (jgroups-3,_master:server-earth-one:EARTH)
> [Relayer _master:server-earth-one:EARTH] view: [_master:server-earth-one:EARTH|4] (1) [_master:server-earth-one:EARTH]
> {code}
> server-earth-one gets a put invocation
> {code}
> 2017-01-04 12:16:38,709 TRACE [org.infinispan.interceptors.impl.InvocationContextInterceptor] (HotRodServerHandler-8-1)
> Invoked with command PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15,
> value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false,
> valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}},
> successful=true} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3d9b13cf]
> {code}
> But for some reason, server-earth-one still tries to send it to the MOON site:
> {code}
> 2017-01-04 12:16:38,713 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (HotRodServerHandler-8-1)
> About to send to backups [MOON (sync, timeout=10000)], command SingleXSiteRpcCommand{command=PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15,
> value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false,
> valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}},
> successful=true}}
> {code}
> ^ That should not happen.
> Moreover, the JGroups layer detects there's no site already:
> {code}
> 2017-01-04 12:16:38,717 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerHandler-8-1)
> master:server-earth-one: no route to MOON: dropping message
> {code}
> But timeout needs to occur for the put to complete:
> {code}
> 2017-01-04 12:16:48,721 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerHandler-8-1)
> ISPN000202: Problems backing up data for cache xsiteCache to site MOON: org.infinispan.util.concurrent.TimeoutException:
> Timed out after 10 seconds waiting for a response from MOON (sync, timeout=10000)
> ...
> 2017-01-04 12:16:48,726 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-7-1)
> Encode msg EmptyResponse{version=25, messageId=21, cacheName='xsiteCache', clientIntel=3, operation=PUT, status=Success, topologyId=1}
> {code}
> I'm attaching full TRACE logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7332) XSite trying to replicate to site after site has been shutdown
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7332?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7332:
-----------------------------------
Description:
In a 2-site scenario, with a server in each site, when the server in one of the sites goes down, and as a result the entire site is gone, the initial site might still try to replicate to the other site. Example:
Sites: EARTH and MOON
Servers: server-earth-one and server-moon-one respectively
server-moon-one stops:
{code}
2017-01-04 12:16:38,666 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050:
Infinispan Server 9.0.0.Beta1 (WildFly Core 2.2.0.Final) stopped in 102ms
{code}
server-earth-one realises that and sets the correct view:
{code}
2017-01-04 12:16:38,649 TRACE [org.jgroups.protocols.relay.RELAY2] (jgroups-3,_master:server-earth-one:EARTH)
[Relayer _master:server-earth-one:EARTH] view: [_master:server-earth-one:EARTH|4] (1) [_master:server-earth-one:EARTH]
{code}
server-earth-one gets a put invocation
{code}
2017-01-04 12:16:38,709 TRACE [org.infinispan.interceptors.impl.InvocationContextInterceptor] (HotRodServerHandler-8-1)
Invoked with command PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15,
value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false,
valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}},
successful=true} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3d9b13cf]
{code}
But for some reason, server-earth-one still tries to send it to the MOON site:
{code}
2017-01-04 12:16:38,713 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (HotRodServerHandler-8-1)
About to send to backups [MOON (sync, timeout=10000)], command SingleXSiteRpcCommand{command=PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15,
value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false,
valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}},
successful=true}}
{code}
^ That should not happen.
Moreover, the JGroups layer detects there's no site already:
{code}
2017-01-04 12:16:38,717 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerHandler-8-1)
master:server-earth-one: no route to MOON: dropping message
{code}
But timeout needs to occur for the put to complete:
{code}
2017-01-04 12:16:48,721 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerHandler-8-1)
ISPN000202: Problems backing up data for cache xsiteCache to site MOON: org.infinispan.util.concurrent.TimeoutException:
Timed out after 10 seconds waiting for a response from MOON (sync, timeout=10000)
...
2017-01-04 12:16:48,726 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-7-1)
Encode msg EmptyResponse{version=25, messageId=21, cacheName='xsiteCache', clientIntel=3, operation=PUT, status=Success, topologyId=1}
{code}
I'm attaching full TRACE logs.
was:
In a 2-site scenario, with a server in each site, when the server in one of the sites goes down, and as a result the entire site is gone, the initial site might still try to replicate to the other site. Example:
Sites: EARTH and MOON
Servers: server-earth-one and server-moon-one respectively
server-moon-one stops:
{code}
2017-01-04 12:16:38,666 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: Infinispan Server 9.0.0.Beta1 (WildFly Core 2.2.0.Final) stopped in 102ms
{code}
server-earth-one realises that and sets the correct view:
{code}
2017-01-04 12:16:38,649 TRACE [org.jgroups.protocols.relay.RELAY2] (jgroups-3,_master:server-earth-one:EARTH) [Relayer _master:server-earth-one:EARTH] view: [_master:server-earth-one:EARTH|4] (1) [_master:server-earth-one:EARTH]
{code}
server-earth-one gets a put invocation
{code}
2017-01-04 12:16:38,709 TRACE [org.infinispan.interceptors.impl.InvocationContextInterceptor] (HotRodServerHandler-8-1) Invoked with command PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15, value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}}, successful=true} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3d9b13cf]
{code}
But for some reason, server-earth-one still tries to send it to the MOON site:
{code}
2017-01-04 12:16:38,713 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (HotRodServerHandler-8-1) About to send to backups [MOON (sync, timeout=10000)], command SingleXSiteRpcCommand{command=PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15, value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}}, successful=true}}
{code}
^ That should not happen.
Moreover, the JGroups layer detects there's no site already:
{code}
2017-01-04 12:16:38,717 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerHandler-8-1) master:server-earth-one: no route to MOON: dropping message
{code}
But timeout needs to occur for the put to complete:
{code}
2017-01-04 12:16:48,721 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerHandler-8-1) ISPN000202: Problems backing up data for cache xsiteCache to site MOON: org.infinispan.util.concurrent.TimeoutException: Timed out after 10 seconds waiting for a response from MOON (sync, timeout=10000)
...
2017-01-04 12:16:48,726 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-7-1) Encode msg EmptyResponse{version=25, messageId=21, cacheName='xsiteCache', clientIntel=3, operation=PUT, status=Success, topologyId=1}
{code}
I'm attaching full TRACE logs.
> XSite trying to replicate to site after site has been shutdown
> --------------------------------------------------------------
>
> Key: ISPN-7332
> URL: https://issues.jboss.org/browse/ISPN-7332
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.0.0.Beta1
> Reporter: Galder Zamarreño
>
> In a 2-site scenario, with a server in each site, when the server in one of the sites goes down, and as a result the entire site is gone, the initial site might still try to replicate to the other site. Example:
> Sites: EARTH and MOON
> Servers: server-earth-one and server-moon-one respectively
> server-moon-one stops:
> {code}
> 2017-01-04 12:16:38,666 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050:
> Infinispan Server 9.0.0.Beta1 (WildFly Core 2.2.0.Final) stopped in 102ms
> {code}
> server-earth-one realises that and sets the correct view:
> {code}
> 2017-01-04 12:16:38,649 TRACE [org.jgroups.protocols.relay.RELAY2] (jgroups-3,_master:server-earth-one:EARTH)
> [Relayer _master:server-earth-one:EARTH] view: [_master:server-earth-one:EARTH|4] (1) [_master:server-earth-one:EARTH]
> {code}
> server-earth-one gets a put invocation
> {code}
> 2017-01-04 12:16:38,709 TRACE [org.infinispan.interceptors.impl.InvocationContextInterceptor] (HotRodServerHandler-8-1)
> Invoked with command PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15,
> value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false,
> valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}},
> successful=true} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3d9b13cf]
> {code}
> But for some reason, server-earth-one still tries to send it to the MOON site:
> {code}
> 2017-01-04 12:16:38,713 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (HotRodServerHandler-8-1)
> About to send to backups [MOON (sync, timeout=10000)], command SingleXSiteRpcCommand{command=PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15,
> value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false,
> valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}},
> successful=true}}
> {code}
> ^ That should not happen.
> Moreover, the JGroups layer detects there's no site already:
> {code}
> 2017-01-04 12:16:38,717 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerHandler-8-1)
> master:server-earth-one: no route to MOON: dropping message
> {code}
> But timeout needs to occur for the put to complete:
> {code}
> 2017-01-04 12:16:48,721 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerHandler-8-1)
> ISPN000202: Problems backing up data for cache xsiteCache to site MOON: org.infinispan.util.concurrent.TimeoutException:
> Timed out after 10 seconds waiting for a response from MOON (sync, timeout=10000)
> ...
> 2017-01-04 12:16:48,726 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-7-1)
> Encode msg EmptyResponse{version=25, messageId=21, cacheName='xsiteCache', clientIntel=3, operation=PUT, status=Success, topologyId=1}
> {code}
> I'm attaching full TRACE logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7332) XSite trying to replicate to site after site has been shutdown
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-7332:
--------------------------------------
Summary: XSite trying to replicate to site after site has been shutdown
Key: ISPN-7332
URL: https://issues.jboss.org/browse/ISPN-7332
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.0.0.Beta1
Reporter: Galder Zamarreño
In a 2-site scenario, with a server in each site, when the server in one of the sites goes down, and as a result the entire site is gone, the initial site might still try to replicate to the other site. Example:
Sites: EARTH and MOON
Servers: server-earth-one and server-moon-one respectively
server-moon-one stops:
{code}
2017-01-04 12:16:38,666 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: Infinispan Server 9.0.0.Beta1 (WildFly Core 2.2.0.Final) stopped in 102ms
{code}
server-earth-one realises that and sets the correct view:
{code}
2017-01-04 12:16:38,649 TRACE [org.jgroups.protocols.relay.RELAY2] (jgroups-3,_master:server-earth-one:EARTH) [Relayer _master:server-earth-one:EARTH] view: [_master:server-earth-one:EARTH|4] (1) [_master:server-earth-one:EARTH]
{code}
server-earth-one gets a put invocation
{code}
2017-01-04 12:16:38,709 TRACE [org.infinispan.interceptors.impl.InvocationContextInterceptor] (HotRodServerHandler-8-1) Invoked with command PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15, value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}}, successful=true} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@3d9b13cf]
{code}
But for some reason, server-earth-one still tries to send it to the MOON site:
{code}
2017-01-04 12:16:38,713 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (HotRodServerHandler-8-1) About to send to backups [MOON (sync, timeout=10000)], command SingleXSiteRpcCommand{command=PutKeyValueCommand{key=org.infinispan.commons.marshall.WrappedByteArray@a3b01a15, value=org.infinispan.commons.marshall.WrappedByteArray@b68d6067, flags=[IGNORE_RETURN_VALUES], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=NumericVersion{version=4294967297}}, successful=true}}
{code}
^ That should not happen.
Moreover, the JGroups layer detects there's no site already:
{code}
2017-01-04 12:16:38,717 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerHandler-8-1) master:server-earth-one: no route to MOON: dropping message
{code}
But timeout needs to occur for the put to complete:
{code}
2017-01-04 12:16:48,721 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerHandler-8-1) ISPN000202: Problems backing up data for cache xsiteCache to site MOON: org.infinispan.util.concurrent.TimeoutException: Timed out after 10 seconds waiting for a response from MOON (sync, timeout=10000)
...
2017-01-04 12:16:48,726 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-7-1) Encode msg EmptyResponse{version=25, messageId=21, cacheName='xsiteCache', clientIntel=3, operation=PUT, status=Success, topologyId=1}
{code}
I'm attaching full TRACE logs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7331) Administration console - removing task before undeploying it should show an error
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-7331?page=com.atlassian.jira.plugin.... ]
Jiří Holuša updated ISPN-7331:
------------------------------
Attachment: local-task.jar
> Administration console - removing task before undeploying it should show an error
> ---------------------------------------------------------------------------------
>
> Key: ISPN-7331
> URL: https://issues.jboss.org/browse/ISPN-7331
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Beta1
> Reporter: Jiří Holuša
> Attachments: local-task.jar
>
>
> Steps to reproduce:
> Go to cache container -> Configuration -> Deployments -> upload some task (you can use the one in attachment) -> Deploy the task -> try clicking Remove
> The task is correctly not removed, since it's not undeployed yet. However, there used to be a popup windows which showed, why the task could not be removed. I think it should be put back since it's much more user-friendly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-7331) Administration console - removing task before undeploying it should show an error
by Jiří Holuša (JIRA)
Jiří Holuša created ISPN-7331:
---------------------------------
Summary: Administration console - removing task before undeploying it should show an error
Key: ISPN-7331
URL: https://issues.jboss.org/browse/ISPN-7331
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 9.0.0.Beta1
Reporter: Jiří Holuša
Steps to reproduce:
Go to cache container -> Configuration -> Deployments -> upload some task (you can use the one in attachment) -> Deploy the task -> try clicking Remove
The task is correctly not removed, since it's not undeployed yet. However, there used to be a popup windows which showed, why the task could not be removed. I think it should be put back since it's much more user-friendly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months