On 10 April 2013 14:26, Tristan Tarrant wrote:
> On 04/10/2013 03:19 PM, James Strachan wrote:
>>
>> after much dismay I started noodling all the junit test cases and
>> discovered the use of '";" as a terminator. And hey presto, adding ";"
>> on the end I can now actually execute commands :). Yay
On 04/10/2013 03:19 PM, James Strachan wrote:
> after much dismay I started noodling all the junit test cases and
> discovered the use of '";" as a terminator. And hey presto, adding ";"
> on the end I can now actually execute commands :). Yay! (You might
> want to make this a bit more clear on the
Ah thanks Tristan!
So I just spent a while trying all kinds of CLI statements and getting
various parsing errors & was pretty confused. I was thinking there
must be something wrong with my setup / classpath as none of the
commands I tried on the wiki worked:
https://community.jboss.org/wiki/Infini
Hi James,
Infinispan 5.3.0.Alpha1 has just been released which should provide much
better error information when parsing CLI commands and also supports the
"null" session for one-shot execution.
Can you please let me know if it satisfies your requirements ?
Trisan
On 03/27/2013 04:40 PM, Tris
On 03/27/2013 04:31 PM, James Strachan wrote:
> How about if we added a new JMX method which didn't take a session ID,
> but allowed you to pass in the codec (e.g. in hawtio's case "json")?
> Then from infinispan server side's perspective it can eagerly timeout
> sessions?
The "codec" in question h
On 27 March 2013 14:54, Tristan Tarrant wrote:
> On 03/27/2013 02:50 PM, James Strachan wrote:
>> On the hawtio server I emailed you off-list - can you enter any CLi
>> statements without getting the NPE?
> No. But I'll provide you with better debugging code soon.
>> It'd be nice to get a nicer pa
On 03/27/2013 02:50 PM, James Strachan wrote:
> On the hawtio server I emailed you off-list - can you enter any CLi
> statements without getting the NPE?
No. But I'll provide you with better debugging code soon.
>
> It'd be nice to get a nicer parser exception message than an NPE BTW
> :). "Incorre
On 27 March 2013 13:21, Tristan Tarrant wrote:
> On 03/22/2013 12:47 PM, James Strachan wrote:
>> Many thanks!
>>
>> BTW does this exception ring any bells:
>> ERROR | qtp581815510-700 | ISPN019003: Interpreter error
>> java.lang.NullPointerException
>> at org.infinispan.cli.interpreter.Interprete
On 03/22/2013 12:47 PM, James Strachan wrote:
> 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.NativeM
On 21 March 2013 12:47, Tristan Tarrant wrote:
> 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 ret
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.Nat
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
On 03/20/2013 04:03 PM, James Strachan wrote:
>
> If the order really is unimportant then noone will mind if we change
> it :) Though really tools tend to assume a certain order.
>
> Though really most JMX related tools build trees from the MBean
> property names; so order dictates how the tree is
On 03/20/2013 10:03 AM, James Strachan wrote:
> On 19 March 2013 17:55, Dennis Reed wrote:
>> This is an invalid use of the MBean names.
>>
>> The keys in an ObjectName are unordered. It is a bug to depend on a
>> specific ordering of the keys.
> If the order really is unimportant then noone will
On 20 Mar 2013, at 15:03, James Strachan wrote:
> On 19 March 2013 17:55, Dennis Reed wrote:
>> This is an invalid use of the MBean names.
>>
>> The keys in an ObjectName are unordered. It is a bug to depend on a
>> specific ordering of the keys.
>
> If the order really is unimportant then n
You need infinispan-cli-server.jar in the classpath.
Tristan
On 03/20/2013 04:19 PM, James Strachan wrote:
> So is the Interpreter MBean only available in 5.3.x? I'm using
> 5.2.5.Final with this configuration:
> https://github.com/hawtio/hawtio/blob/master/hawtio-web/src/test/resources/infinispa
So is the Interpreter MBean only available in 5.3.x? I'm using
5.2.5.Final with this configuration:
https://github.com/hawtio/hawtio/blob/master/hawtio-web/src/test/resources/infinispan-local.xml#L15
is there something else I need to do to get the Interpreter MBean to appear?
On 20 March 2013 10:
On 19 March 2013 17:55, Dennis Reed wrote:
> This is an invalid use of the MBean names.
>
> The keys in an ObjectName are unordered. It is a bug to depend on a
> specific ordering of the keys.
If the order really is unimportant then noone will mind if we change
it :) Though really tools tend to
On 20 March 2013 09:44, Tristan Tarrant wrote:
> On 03/19/2013 06:55 PM, Dennis Reed wrote:
>> This is an invalid use of the MBean names.
>>
>> The keys in an ObjectName are unordered. It is a bug to depend on a
>> specific ordering of the keys.
> Thanks Dennis, I was about to write that.
>> On 0
On 03/20/2013 11:35 AM, Manik Surtani wrote:
> As in, the JMX spec does not guarantee the order of ObjectName
> components?
Indeed.
> Does this mean that [1] is solved by an existing MBean?
>
> [1] https://issues.jboss.org/browse/ISPN-2926
Yes, each CacheManager gets an "Interpreter" MBean which
On 20 Mar 2013, at 09:44, Tristan Tarrant wrote:
> On 03/19/2013 06:55 PM, Dennis Reed wrote:
>> This is an invalid use of the MBean names.
>>
>> The keys in an ObjectName are unordered. It is a bug to depend on a
>> specific ordering of the keys.
> Thanks Dennis, I was about to write that.
A
On 03/19/2013 06:55 PM, Dennis Reed wrote:
> This is an invalid use of the MBean names.
>
> The keys in an ObjectName are unordered. It is a bug to depend on a
> specific ordering of the keys.
Thanks Dennis, I was about to write that.
> On 03/19/2013 10:07 AM, Manik Surtani wrote:
>>
>> On 27 Feb
This is an invalid use of the MBean names.
The keys in an ObjectName are unordered. It is a bug to depend on a
specific ordering of the keys.
-Dennis
On 03/19/2013 10:07 AM, Manik Surtani wrote:
> Hi James.
>
> Strange that no one else has responded to you on this list as yet; I'm all
> for r
Hi James.
Strange that no one else has responded to you on this list as yet; I'm all for
reorganising the JMX names to suit Hawt.io, but not by default since it will
affect our JON/RHQ plugins.
Care to create a JIRA in Infinispan to allow a JVM system parameter to swap the
JMX name components
24 matches
Mail list logo
