I just added the mx4j-tools jar (version 3.0.2) in my lib folder and also
enabled remote jmx access without authentication (using firewall to protect
access).
During startup I can see the two following log statements:

HttpAdaptor version 3.0.2 started on port 8081
mx4j successfuly loaded

So, it seems like everything is working fine. In netstat I can also see
that it is listening on that port, but when I try to open the web interface
(http://myhost:8081/), I just get an empty response (HTTP 200, but
content-length 0).
Tried several different paths (e.g. /server /serverbydomain /mbean), all
200 with an empty response.
There are no further logs related to mx4j.

Has anybody seen such a behavior before? Did I miss any mandatory
configuration?

Thanks

Reply via email to