Skip to content

Commit 203a363

Browse files
committed
doc(jmx) Added notes on HTTP JMX access
- Clarified security of access of JMX information over HTTP - Signposted web proxy article for best practice of setting up eXist
1 parent 74738b6 commit 203a363

File tree

1 file changed

+14
-0
lines changed
  • src/main/xar-resources/data/jmx

1 file changed

+14
-0
lines changed

src/main/xar-resources/data/jmx/jmx.xml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,20 @@
167167
<para>For example, to get a report on current memory usage and running instances, use
168168
the following URL:</para>
169169
<programlisting>http://localhost:8080/exist/status?c=memory&amp;c=instances</programlisting>
170+
<note>
171+
<para>The JMX information is only accessible via the HTTP interface when either:</para>
172+
<itemizedlist>
173+
<listitem>
174+
<para>the client accesses the API on localhost</para>
175+
</listitem>
176+
<listitem>
177+
<para>a valid token is provided when accessing the API from a remote IP address</para>
178+
</listitem>
179+
</itemizedlist>
180+
</note>
181+
<note>
182+
<para>Use <link xlink:href="production_web_proxying">a web proxy</link> if you wish to provide this service separately from other eXist applications.</para>
183+
</note>
170184
<para>This returns something like:</para>
171185
<programlisting language="xml" xlink:href="listings/listing-8.xml"/>
172186
<para>The different JMX objects in eXist are organized into categories. One or more

0 commit comments

Comments
 (0)