Non-remoting ModelControllerClient?

[pmm]

Is there a way to create a ModelControllerClient that doesn't use remoting but works "in-memory". I need to flush the credential cache as outlined in https://community.jboss.org/message/644710#644710 (for different reasons) and ModelControllerClient seems the way to go. However I'd like to have an option that doen't use sockets. We have multiple JBoss instances installed on the same server and I can't assume that the management port is always 9999.

[welle]

*bump*

[jaikiran]

Anders Welen wrote:

*bump*

The same question as the original poster?

I don't see a reason why the ModelControllerClient can't be used with different ports.

[welle]

Sorry for the late reply. I've been busy.

I basically want to use the ModelControllerClient from an application running within the same JVM as the JBoss 7 server. Is there a in-vm "connector" so we doesn't have to keep track of the current configured port?

[ctomc]

hi,

it is possible to do that, but it requires a bit work to make it work.

read http://management-platform.blogspot.com/2012/07/co-located-management-client-for.html

take a look at 6th mechanism how to manage AS7.

in short you need create service activator and that is part of your war, and via it you can get to all internal stuff.

--

tomaz

[welle]

Thanks, it seems like it would solve the "problem".