I have a new information. With the JMX Agent, i find this error:
[Remoting "endpoint" task-2] DEBUG org.jboss.remoting.remote.client - Client authentication failed for mechanism JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException: C:\JBoss\jboss-as-7.1.1.Final\standalone\tmp\auth\challenge-2169748 (No such file or directory)]
However, the PATH "C:\JBoss\jboss-as-7.1.1.Final\" is false(I'm in CentOS). I want to change this PATH but i don"t know where i can find it ...
The memory leak you are encountering is a known issue, upgrading to AS 7.1.3 should cover that scenario although there is a second leak that will be fixed in AS 7.2.0.
Regarding the SASL message, that message is just a DEBUG message. I am assuming you are running JBoss AS on Windows and the agent on CentOS - that message is fine it just shows that using the local authentication mechanisms was attempted but failed and it should then have automatically moved on to use a supported authentication mechanism.
Ok, thanks for your answer. So I going to wait Jboss AS 7.1.3 (or 7.2.0 if the bug persist) and begin to make Jboss template for the supervision.
However, my Jboss AS are running on Linux. For the moment, i tested my supervision only on CentOS. So, i don"t know why i have this PATH ... It's strange ! ^^
So, thanks for your information .
Could you give me the JIRA issue about this memory leak please ?
I'm trying to get Zabbix monitor Jboss 7 and I'm encountering the same problem:
"Jboss used a Remoting-jmx protocol while Zabbix JMX Agent used rmi protocol to connect about JMX Server"
Can you tell me how did you manager to change the JMX agent of Zabbix to allow connection with remoting-jmx protocol between Zabbix and Jboss please. Or at least point me to the documentation you used.
I would be very grateful.
Thanks and regards.