[JBoss JIRA] (ISPN-11838) Native CLI compiled with GraalVM
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11838:
--------------------------------------
Summary: Native CLI compiled with GraalVM
Key: ISPN-11838
URL: https://issues.redhat.com/browse/ISPN-11838
Project: Infinispan
Issue Type: Feature Request
Components: CLI
Affects Versions: 11.0.0.Dev05
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 11.0.0.CR1
We should be able to build a native CLI using GraalVM's `native-image`
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11625) CLI commands to interact with Operator
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11625?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11625:
-----------------------------------
Description:
The Infinispan Server CLI should be extended so that it can be used to control/configure the operator and custom resource definitions.
The CLI should act as a `kubectl` plugin, i.e. installed as `kubectl-infinispan` so that it can be invoked as `kubectl infinispan ...` or `oc infinispan ...`
The CLI should be able to perform the following operations:
* install the operator CRD
* create CRs (cache service, caches, etc)
* transparently connect to a running cluster to perform interactive operations
was:
The Infinispan Server CLI should be extended so that it can be used to control/configure the operator and custom resource definitions.
The CLI should act as a `kubectl` plugin, i.e. installed as `kubectl-infinispan` so that it can be invoked as `kubectl infinispan ...` or `oc infinispan ...`
The CLI should be able to perform the following operations:
* install the operator CRD
* create CRs (cache service, caches, etc)
* transparently connect to a running cluster to perform interactive operations
Investigate the possibility of building/shipping a native binary.
> CLI commands to interact with Operator
> --------------------------------------
>
> Key: ISPN-11625
> URL: https://issues.redhat.com/browse/ISPN-11625
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, Operator
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The Infinispan Server CLI should be extended so that it can be used to control/configure the operator and custom resource definitions.
> The CLI should act as a `kubectl` plugin, i.e. installed as `kubectl-infinispan` so that it can be invoked as `kubectl infinispan ...` or `oc infinispan ...`
> The CLI should be able to perform the following operations:
> * install the operator CRD
> * create CRs (cache service, caches, etc)
> * transparently connect to a running cluster to perform interactive operations
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-3575) Can not create newCache from baseCache from which to get the configuration inside EAP server
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-3575?page=com.atlassian.jira.plugin... ]
Tristan Tarrant closed ISPN-3575.
---------------------------------
Resolution: Out of Date
> Can not create newCache from baseCache from which to get the configuration inside EAP server
> --------------------------------------------------------------------------------------------
>
> Key: ISPN-3575
> URL: https://issues.redhat.com/browse/ISPN-3575
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 6.0.0.Beta1
> Reporter: Vitalii Chepeliuk
> Priority: Major
> Attachments: jboss-as-carmart-tx.war
>
>
> After deploying carmart-tx application on EAP server and running create command with like paramer, ISPN019016 error occurs
> [remoting://localhost:9999/DefaultCacheManager/]> create newCache like carcache
> ISPN019016: No such cache: 'carcache'
> [remoting://localhost:9999/DefaultCacheManager/]> cache
> ___defaultcache carcache
> [remoting://localhost:9999/DefaultCacheManager/]> cache carcache
> [remoting://localhost:9999/DefaultCacheManager/carcache]> create newCache like carcache
> ISPN019016: No such cache: 'carcache'
> [remoting://localhost:9999/DefaultCacheManager/carcache]> create newCache like carcache
> ISPN019016: No such cache: 'carcache'
> [remoting://localhost:9999/DefaultCacheManager/carcache]> cache carcache
> [remoting://localhost:9999/DefaultCacheManager/carcache]> get carnumbers
> {"java.util.ArrayList":["FML 23-25","1P3 2632","1B2 1111","6T4 2526","2B2 4946"]}
> [remoting://localhost:9999/DefaultCacheManager/carcache]> get "6T4+2526"
> {"org.jboss.as.quickstarts.datagrid.carmart.model.Car":{"brand":"Mazda MX-5","displacement":1.8,"type":"CABRIO","color":"red","numberPlate":"6T4 2526","country":"USA"}}
> [remoting://localhost:9999/DefaultCacheManager/carcache]> create newCache like carcache
> ISPN019016: No such cache: 'carcache'
> [remoting://localhost:9999/DefaultCacheManager/carcache]> cache newCache
> ISPN019016: No such cache: 'newCache'
> [remoting://localhost:9999/DefaultCacheManager/carcache]> cache
> ___defaultcache carcache
> [remoting://localhost:9999/DefaultCacheManager/carcache]> cache ___defaultcache
> [remoting://localhost:9999/DefaultCacheManager/___defaultcache]> cache
> ___defaultcache
> [remoting://localhost:9999/DefaultCacheManager/___defaultcache]> create newCache like ___defaultcache
> ISPN019016: No such cache: '___defaultcache'
> -------------------------------------------------------------------------------------------------------
> Here is stack trace from server
> 13:47:00,970 ERROR [org.infinispan.cli.interpreter.Interpreter] (pool-1-thread-1) ISPN019003: Interpreter error: java.lang.IllegalArgumentException: ISPN019016: No such cache: 'carcache'
> at org.infinispan.cli.interpreter.session.SessionImpl.createCache(SessionImpl.java:93) [infinispan-cli-server-6.0.0.Beta1.jar:6.0.0.Beta1]
> at org.infinispan.cli.interpreter.statement.CreateStatement.execute(CreateStatement.java:25) [infinispan-cli-server-6.0.0.Beta1.jar:6.0.0.Beta1]
> at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:150) [infinispan-cli-server-6.0.0.Beta1.jar:6.0.0.Beta1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:271) [infinispan-core-6.0.0.Beta1.jar:6.0.0.Beta1]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_25]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) [rt.jar:1.7.0_25]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:731)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:952)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$2.run(ServerInterceptorFactory.java:100)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$2.run(ServerInterceptorFactory.java:96)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
> at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_25]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:96)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11837) ContainerInfinispanServerDriver missing cluster size check
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-11837:
-----------------------------------
Summary: ContainerInfinispanServerDriver missing cluster size check
Key: ISPN-11837
URL: https://issues.redhat.com/browse/ISPN-11837
Project: Infinispan
Issue Type: Bug
Components: Test Suite
Affects Versions: 11.0.0.Dev05
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 11.0.0.CR1
The tests in {{server/tests}} that are executed in CONTAINER mode do not currently check to ensure that a cluster of {{InfinispanServerTestConfiguration#numServers}} is formed before the tests begin. This means that it's possible for some of the {{ClusteredIT}} tests to pass even if no cluster is formed between the containers.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-11830) Provide invocation based non blocking detection to test suite
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11830?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11830:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Provide invocation based non blocking detection to test suite
> -------------------------------------------------------------
>
> Key: ISPN-11830
> URL: https://issues.redhat.com/browse/ISPN-11830
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> Currently we support block hound based blocking detection on a per thread basis. But this isn't sufficient if a test wants to detect if a blocking operation in a more natural way. Instead a user would have to submit a task to a different thread just for that invocation. This is ugly and quite error prone as it changes how the code would normally work (ThreadLocal etc.)
> We should instead use the new dynamic thread predicate added in BlockHound 1.0.3 to support this.
> I have also logged https://github.com/reactor/BlockHound/issues/121 which makes part of the code uglier until we can upgrade to 1.0.4.RELEASE.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months