[JBoss JIRA] (ISPN-6310) Endpoints registered via CLI have wrong JMX name
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6310?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6310:
----------------------------------
Component/s: Memcached
> Endpoints registered via CLI have wrong JMX name
> ------------------------------------------------
>
> Key: ISPN-6310
> URL: https://issues.jboss.org/browse/ISPN-6310
> Project: Infinispan
> Issue Type: Bug
> Components: CLI, Memcached, Server
> Affects Versions: 8.2.0.CR1
> Reporter: Martin Gencur
>
> When I register second Memcached (called "memcached2") endpoint via CLI, the resulting JMX name is
> {code}
> jboss.datagrid-infinispan2:type=Server,name=Memcached,component=Transport
> {code}
> This is wrong because when the endpoint is configured in domain.xml, the resulting address is different:
> {code}
> jboss.datagrid-infinispan:type=Server,name=Memcached-memcached2,component=Transport
> {code}
> I suppose the latter name is correct because all the other Infinispan MBeans can be found under that domain (jboss.datagrid-infinispan). OTOH, when CLI is used and the second endpoint added, the new doman jboss.datagrid-infinispan2 has only a single MBean under itself, and that is the new endpoint.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8539) Off Heap Expiration doesn't work with non EmbeddedMetadata
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8539?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8539:
----------------------------------
Component/s: Memcached
> Off Heap Expiration doesn't work with non EmbeddedMetadata
> ----------------------------------------------------------
>
> Key: ISPN-8539
> URL: https://issues.jboss.org/browse/ISPN-8539
> Project: Infinispan
> Issue Type: Bug
> Components: Memcached, Off Heap
> Affects Versions: 9.1.3.Final
> Reporter: William Burns
>
> Currently off heap just writes the custom metadata as serialized bytes. Unfortunately this isn't sufficient as it also would have to write the time it was accessed or created when using either expiration mode.
> We also may want to find out if we even need to persist all custom metadata. For example memcached metadata seems fine to just treat as embedded.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7143) Memcached connector fails if default cache is not configured
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7143?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7143:
----------------------------------
Component/s: Memcached
> Memcached connector fails if default cache is not configured
> ------------------------------------------------------------
>
> Key: ISPN-7143
> URL: https://issues.jboss.org/browse/ISPN-7143
> Project: Infinispan
> Issue Type: Bug
> Components: Memcached, Server
> Affects Versions: 9.0.0.Alpha4
> Reporter: Jakub Markos
>
> When core and endpoint configurations in clustered.xml config from server distribution are reduced to this:
> {code}
> <subsystem xmlns="urn:infinispan:server:core:9.0" default-cache-container="clustered">
> <cache-container name="clustered" default-cache="default" statistics="true">
> <transport lock-timeout="60000"/>
> <global-state/>
> <distributed-cache name="memcachedCache" mode="SYNC" segments="20" owners="2" remote-timeout="30000" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> </distributed-cache>
> </cache-container>
> </subsystem>
> <subsystem xmlns="urn:infinispan:server:endpoint:9.0">
> <memcached-connector socket-binding="memcached" cache-container="clustered" cache="memcachedCache"/>
> </subsystem>
> {code}
> the server throws this ERROR on startup:
> {code}
> 17:10:14,051 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) DGISPN0001: Started memcachedCache cache from clustered container
> 17:10:14,069 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datagrid-infinispan-endpoint"),
> ("memcached-connector" => "memcached-connector")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.datagrid-infinispan.clustered.default"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.datagrid-infinispan-endpoint.memcached.memcached-connector is missing [jboss.datagrid-infinispan.clustered.default]"]
> }
> 17:10:14,085 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.datagrid-infinispan.clustered.default (missing) dependents: [service jboss.datagrid-infinispan-endpoint.memcached.memcached-connector]
> 17:10:14,143 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:10090/management
> 17:10:14,143 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:10090
> 17:10:14,144 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: Infinispan Server 9.0.0-SNAPSHOT (WildFly Core 2.2.0.Final) started (with errors) in 7173ms - Started 177 of 222 services (1 services failed or missing dependencies, 110 services are lazy, passive or on-demand)
> {code}
> When a default cache is also defined, like
> {code}
> <subsystem xmlns="urn:infinispan:server:core:9.0" default-cache-container="clustered">
> <cache-container name="clustered" default-cache="default" statistics="true">
> <transport lock-timeout="60000"/>
> <global-state/>
>
> <distributed-cache name="default" mode="SYNC" segments="20" owners="2" remote-timeout="30000" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> </distributed-cache>
> <distributed-cache name="memcachedCache" mode="SYNC" segments="20" owners="2" remote-timeout="30000" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> </distributed-cache>
> </cache-container>
> </subsystem>
> {code}
> everything is OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7380) Tests from org.infinispan.server.memcached.MemcachedFunctionalTest fail on Solaris 10
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7380?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7380:
----------------------------------
Component/s: Memcached
> Tests from org.infinispan.server.memcached.MemcachedFunctionalTest fail on Solaris 10
> -------------------------------------------------------------------------------------
>
> Key: ISPN-7380
> URL: https://issues.jboss.org/browse/ISPN-7380
> Project: Infinispan
> Issue Type: Bug
> Components: Memcached, Server
> Affects Versions: 9.0.0.Beta1
> Reporter: Roman Macor
>
> org.infinispan.server.memcached.MemcachedFunctionalTest.testSetWithExpiryUnixTimeInPast
> Error Message
> Timed out waiting for operation - failing node: /127.0.0.1:16211
> Stacktrace
> net.spy.memcached.internal.CheckedOperationTimeoutException: Timed out waiting for operation - failing node: /127.0.0.1:16211
> at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:167)
> at org.infinispan.server.memcached.MemcachedFunctionalTest.testSetWithExpiryUnixTimeInPast(MemcachedFunctionalTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:348)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:38)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Standard Error
> 2017-01-22 03:51:44.771 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for k0-testSetWithExpiryUnixTimeInPast.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months