4 Replies Latest reply on Sep 20, 2016 4:34 PM by adee_j

Loading Jolokia with Infinispan Cache server

adee_j Sep 9, 2016 5:41 PM

Hi,

I want to use Jolokia to monitor my cache server's statistics. I used the jolokia.war and put it in the standalone/deployements folder. After the server is started I can see the following line in the logs -

16:25:17,428 INFO [org.jboss.as.server] (ServerService Thread Pool -- 17) WFLYSRV0010: Deployed "jolokia.war" (runtime-name : "jolokia.war")

I'm supposed to access it using the url http://localhost:<HTTP_PORT>/jolokia/. The port 8080 is assigned by the server for REST services. When I try to access jolokia on that, I get resource not found error. I'm using the 8.2.4.Final version of Infinispan.

Startup Log -

16:25:12,952 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

16:25:13,178 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

16:25:13,256 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: Infinispan Server 8.2.4.Final (WildFly Core 2.0.10.Final) starting

16:25:14,704 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

16:25:14,752 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.3.4.Final

16:25:14,762 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.4.Final

16:25:14,806 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.18.Final

16:25:14,831 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 25) WFLYNAM0001: Activating Naming Subsystem

16:25:14,837 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 29) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

16:25:14,978 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service

16:25:14,886 INFO [org.jboss.as.security] (ServerService Thread Pool -- 27) WFLYSEC0002: Activating Security Subsystem

16:25:15,085 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)

16:25:15,093 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final

16:25:14,952 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 20) Activating Infinispan subsystem.

16:25:14,949 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 19) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4

available processors

16:25:15,007 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 18) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

16:25:15,184 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2

16:25:15,683 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory D:\Project\DevTools\infinispan-serv

er-8.2.4.Final\standalone\deployments

16:25:15,684 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

16:25:15,696 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "jolokia.war" (runtime-name: "jolokia.war")

16:25:15,838 INFO [org.jboss.as.remoting] (MSC service thread 1-5) WFLYRMT0001: Listening on 127.0.0.1:9001

16:25:16,213 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final

16:25:16,639 INFO [org.infinispan.expiration.impl.ExpirationManagerImpl] (MSC service thread 1-3) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread

16:25:16,641 INFO [org.infinispan.expiration.impl.ExpirationManagerImpl] (MSC service thread 1-7) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread

16:25:16,643 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-7) DGISPN0001: Started default cache from local container

16:25:16,644 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) DGISPN0001: Started memcachedCache cache from local container

16:25:16,645 INFO [org.infinispan.server.endpoint] (MSC service thread 1-7) DGENDPT10000: REST starting

16:25:16,649 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10000: HotRodServer starting

16:25:16,651 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10001: HotRodServer listening on 127.0.0.1:11222

16:25:16,666 INFO [org.infinispan.expiration.impl.ExpirationManagerImpl] (MSC service thread 1-4) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread

16:25:16,670 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) DGISPN0001: Started namedCache cache from local container

16:25:16,669 INFO [org.infinispan.server.endpoint] (MSC service thread 1-8) DGENDPT10000: MemcachedServer starting

16:25:16,671 INFO [org.infinispan.server.endpoint] (MSC service thread 1-8) DGENDPT10001: MemcachedServer listening on 127.0.0.1:11211

16:25:16,667 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10000: WebSocketServer starting

16:25:16,675 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10001: WebSocketServer listening on 127.0.0.1:8181

16:25:16,738 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-7) DGISPN0001: Started ___protobuf_metadata cache from local container

16:25:16,770 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-7) DGISPN0001: Started ___script_cache cache from local container

16:25:17,409 INFO [org.infinispan.rest.NettyRestServer] (MSC service thread 1-7) ISPN012003: REST server starting, listening on 127.0.0.1:8282

16:25:17,409 INFO [org.infinispan.server.endpoint] (MSC service thread 1-7) DGENDPT10002: REST mapped to /rest

16:25:17,428 INFO [org.jboss.as.server] (ServerService Thread Pool -- 17) WFLYSRV0010: Deployed "jolokia.war" (runtime-name : "jolokia.war")

16:25:17,521 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

16:25:17,522 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

16:25:17,523 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Infinispan Server 8.2.4.Final (WildFly Core 2.0.10.Final) started in 4886ms - Started 179 of 188 services (50

services are lazy, passive or on-demand)

Kindly help. Thanks in advance.

1. Re: Loading Jolokia with Infinispan Cache server

sebastian.laskawiec Sep 12, 2016 1:10 AM (in response to adee_j)
Wildfly uses separate classloader per deployment. Since you're deploying Jolokia and you application separately, they can not see each other.

There are 2 ways to fix this:
Embed Jolokia into your application
Use Jolokia Java agent with WildFly boot. The easiest way to do it is to modify standalone.conf in $Wildfly/bin directory.
Actions
2. Re: Loading Jolokia with Infinispan Cache server

adee_j Sep 12, 2016 3:12 AM (in response to sebastian.laskawiec)

Thanks Sebastian,
Since I'm pretty new to Wildfly, can you please tell me if this information is present in the Jolokia or the Wildfly server documentation? I'm very much interested in the second method you suggested, i.e., to use the jvm-agent with Wildfly boot. A little info on how to modify standalone.conf may help too.

Kind regards
Actions
3. Re: Loading Jolokia with Infinispan Cache server

sebastian.laskawiec Sep 12, 2016 3:38 AM (in response to adee_j)

I don't think so. It is impossible to document every combination of WildFly and 3rd party software.

Sure, let me give you an example how to configure WF - in standalone.conf you probably have a line similar to this one:
#JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
Now change it to something like this:
JAVA_OPTS="$JAVA_OPTS -javaagent:/path/to/jolokia/jar/agent.jar=port=7777,host=localhost"

After starting WildFly, the Jolokia endpoint should be available here: http://localhost:7777. For more information, please refer to Jolokia documentation.
Actions
4. Re: Loading Jolokia with Infinispan Cache server

adee_j Sep 20, 2016 4:34 PM (in response to sebastian.laskawiec)

Thanks Sebastian for the help and sorry for the late reply. Your suggestion to deploy it as a java agent worked.

Regards
Y
Actions

Go to original post