Lots of inodes in /tmp/auth using service:jmx:remoting-jmx:// with username and password
Issue
- Every call using service:jmx:remoting-jmx:// with username and password seems to create a new file under
<JBOSS_HOME>/tmp/auth
with a .challenge file ending.
The problem is that since we monitor the application using JMX, the maximum number of inodes on the machine gets exceeded really quickly. Is this a known issue ? What can we do to make JBoss clean this up/not create these files ? - When using remoting-jmx with authentication, the tmp/auth directory fills up with .challenge files
Environment
JBoss Enterprise Application Platform (EAP) 6.0.0 GA
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.