Hello,
One thing to note is that one needs the jboss-client.jar to access wildfly
via jmx remotely.
http://www.mastertheboss.com/jboss-server/wildfly-8/monitoring-wildfly-us...
At least that was the only way I could get it to work.
Cheers,
Thomas
Am 21.08.2017 6:22 nachm. schrieb "Stan Silvert" <ssilvert(a)redhat.com>:
We could also think about getting rid of jboss-cli-client.jar. It's not
used by jboss-cli.sh when you are running from /bin. It is copied to a
remote box when someone wants to use jboss-cli.sh remotely. Removing
it would save another 7M.
On 8/21/2017 10:05 AM, Bill Burke wrote:
FYI,
Our distro is 17M bigger because we include jboss.client.jar. This jar
is uber jar by Java clients that want to talk to server (stubs, jndi,
etc.), but its 17M.
Bill
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev