Right, ok, this makes sense. And what about if it runs in another tomcat
instance (or if it's a standalone application)? Is the url something like
service:jmx:rmi:///jndi/rmi://:/jmxrmi,
where port is the value specified by -Dcom.sun.management.jmxremote.port?
Thanks,
Michele
Mikolaj Rydzewski
Michele Mazzucco wrote:
I understand this. What I don't understand is, how can I access (inside
a web application or program) the mbeans exposed by another web
application? Do you have any chunk of code to show me?
If you want to access another webapp's mbeans (but running in the same
Tomcat
Hi Mikolaj,
I understand this. What I don't understand is, how can I access (inside
a web application or program) the mbeans exposed by another web
application? Do you have any chunk of code to show me?
Thanks,
Michele
Mikolaj Rydzewski wrote:
> Michele Mazzucco wrote:
>> right, that's the respo
Michele Mazzucco wrote:
right, that's the response to my question :).
Now, I've got a web application exposing some mbeans. How can I access
them from outside (another web application deployed on the same machine,
for example)?
Enable remote JXM access. Just like when working with jconsole.
Hi Peter,
right, that's the response to my question :).
Now, I've got a web application exposing some mbeans. How can I access
them from outside (another web application deployed on the same machine,
for example)?
Michele
Peter Rossbach wrote:
> HI Michele,
>
> please, read the sun jmx docs.
>
HI Michele,
please, read the sun jmx docs.
The default jmx server from java 5 starts a rmi registry and starts a
jmx server socket.
Currently the jmx server socket port change with every start from
your jvm. You can't
control the port or binding an ip address from command line. Please,
re
I'm sorry Peter, but you didn't reply to my questions ;): with the out
of the box configuration, what happens if I want to connect this way:
JMXServiceURL url = new JMXServiceURL(
"service:jmx:rmi:///jndi/rmi://localhost:/server");
JMXConnector jmxc = JMXConnectorFact
Hi,
Am 14.09.2006 um 16:25 schrieb Michele Mazzucco:
Thanks Peter.
Peter Rossbach wrote:
Hi,
I don't know about this experiment, but it seems not finished.
Please,
use sun jdk command line args to start your jmx adapter.
I though tomcat used mx4j.
Only with JDK 1.4. See JDK 1.4 Compat
Thanks Peter.
Peter Rossbach wrote:
> Hi,
>
> I don't know about this experiment, but it seems not finished. Please,
> use sun jdk command line args to start your jmx adapter.
I though tomcat used mx4j.
> One of the strange things of the current Java 5 JVM is: You can only set
> the naming por
Hi,
I don't know about this experiment, but it seems not finished.
Please, use sun jdk command line args to start your jmx adapter.
One of the strange things of the current Java 5 JVM is: You can only
set the naming port and not the real communication port :-(
This is obviously bad for peop
Hi Peter,
thanks. But what about "out of the box" configuration?, the
org.apache.tomcat.servlets.jmxremote.JmxRemoteServlet creates a rmi
registry on port 1099 and a jmx service url at
service:jmx:rmi://rmiHost/jndi/rmi://localhost:1099/jndiPath. So the
question is, is rmi the default jmx protocol
Hi,
please read the docs
http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html
Regards
Peter
Am 14.09.2006 um 11:23 schrieb Michele Mazzucco:
Hi all,
which kind of JMX connector does tomcat uses, rmi? If it is rmi, which
port is it used? In which class is the JMX agent started?
Thanks,
Hi all,
which kind of JMX connector does tomcat uses, rmi? If it is rmi, which
port is it used? In which class is the JMX agent started?
Thanks,
Michele
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-m
13 matches
Mail list logo
