Re: [infinispan-dev] a nice HTML5 console for Infinispan & a question on MBean names...
Many thanks!
BTW does this exception ring any bells:
ERROR | qtp581815510-700 | ISPN019003: Interpreter error
java.lang.NullPointerException
at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:161)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:287)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
I can polish what I have so you can try it out locally if its any
help. I seem to get this whatever commands I execute.
Incidentally do the session IDs timeout after a while? Seems like I
saw that once or twice (though could be a hawtio bug :). If so I'm
wondering if it might be easier to have a new method
executeWithTemporarySessionId(cacheName, sql) or something like that
so we don't have to keep track of when a session ID is stale or have
to do 2 operations when we don't mind about the session ID (i.e. use
one session ID per operation)?.
On 21 March 2013 12:47, Tristan Tarrant <ttarrant(a)redhat.com> wrote:
On 03/21/2013 12:48 PM, James Strachan wrote:
> So as it turns out I've added a workaround to the MBean naming issue;
> I've just created a new custom UI for Infinispan inside hawtio. (Feel
> free to close the JIRA if you like).
>
> I've attached a little screenshot of what I've got so far in case
> anyone's interested.
>
> I'm now about to try add in CLI support...
>
Excellent stuff.
For the CLI, you need to invoke the createSessionId(String cacheName)
method on the Interpreter MBean and then use that session id for all
subsequent invocations on the execute(String sessionId, String script)
method.
The execute method returns a map which may contain the following:
OUTPUT the output of the execution of the script (roughly equivalent to
stdout)
ERROR errors which occurred during script execution (roughly equivalent
to stderr)
STACKTRACE a stacktrace in case of errors
CACHE the name of the currently selected cache for the script session
If you need help, just ask
Tristan
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
James
-------
Red Hat
Email: jstracha(a)redhat.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Open Source Integration