1) missing help for this commands:

clear, container, evict, locate, putifabsent, remove, version


2) help rollback -> returns the following:

SYNOPSIS 
   start
DESCRIPTION
   Starts a batch

3) help for "begin" and "start" commands returns the same: "Begins a transaction" 
IMO the help for "start" command should mention a batch, not a transaction. It's confusing.

4) It is not clear to me what the "upgrade" command is supposed to do, even if I read the help for it. Can we extend the help to contain more information?

5) When "delete" key is pressed on the keyboard, some extra characters are printed out. Can we change this to make the interface more user friendly?

6) When inserting a key/value pair, it is not possible to specify only maxidle time, users must set either both expires and maxidle or none of them. This is IMO expected after reading the SYNOPSIS. The question is - doesn't it make sense to set only maxidle for entries?


7) It happends regularly that after several minitus a sessions expires and consecutive commands return "Invalid Session ID". JDG log shows the following: 

09:54:14,257 ERROR [org.infinispan.cli.interpreter.Interpreter] (pool-1-thread-3) ISPN019003: Interpreter error: java.lang.IllegalArgumentException: Invalid session ID
	at org.infinispan.cli.interpreter.Interpreter.validateSession(Interpreter.java:184) [infinispan-cli-server-5.2.0.Beta4-redhat-1.jar:5.2.0.Beta4-redhat-1]
	at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:145) [infinispan-cli-server-5.2.0.Beta4-redhat-1.jar:5.2.0.Beta4-redhat-1]
	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) [:1.6.0_30]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
	at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
	at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:270) [infinispan-core-5.2.0.Beta4-redhat-1.jar:5.2.0.Beta4-redhat-1]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) [rt.jar:1.6.0_30]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) [rt.jar:1.6.0_30]
	at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) [jboss-as-jmx-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
	at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) [jboss-as-jmx-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
	at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
	at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]

The workaround in such case is to re-connect the CLI to the server.

8) I cannot commit a transaction with "commit" command because I'm getting the following error: "Cannot retrieve a transaction manager for the cache"

JDG log shows the following:

10:18:25,342 ERROR [org.infinispan.cli.interpreter.Interpreter] (pool-1-thread-11) ISPN019003: Interpreter error: org.infinispan.cli.interpreter.result.StatementException: Cannot retrieve a transaction manager for the cache
	at org.infinispan.cli.interpreter.statement.BeginTransactionStatement.execute(BeginTransactionStatement.java:46) [infinispan-cli-server-5.2.0.Beta4-redhat-1.jar:5.2.0.Beta4-redhat-1]
	at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:156) [infinispan-cli-server-5.2.0.Beta4-redhat-1.jar:5.2.0.Beta4-redhat-1]
	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) [:1.6.0_30]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
	at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
	at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:270) [infinispan-core-5.2.0.Beta4-redhat-1.jar:5.2.0.Beta4-redhat-1]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) [rt.jar:1.6.0_30]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) [rt.jar:1.6.0_30]
	at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) [jboss-as-jmx-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
	at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) [jboss-as-jmx-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
	at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
	at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
   
I'm using default standalone.xml configuration. Is there anything I need to set up to make it work? When "info mamcachedCache" is issued, it contains the following among other things:
transactionManagerLookup=org.infinispan.transaction.lookup.GenericTransactionManagerLookup@9273085