RE: Monitoring CXF Webservices
Actually I have one last issue...is it possible to not set this up as a server implememntation but to access it like the other java MX beans? Eg can I do something like: ThreadMXBean tMxBean = ManagementFactory.getThreadMXBean(); tMxBean.getTotalStartedThreadCount(); I'd rather not start up an RMI instance. When I do, I can't seem to stop tomcat anymore - it just hangs when I try to shut down. Any help is appreciated. -Tony -Original Message- From: Vespa, Anthony J Sent: Monday, November 12, 2007 12:28 PM To: cxf-user@incubator.apache.org Subject: RE: Monitoring CXF Webservices Thank you for these examples but I am not 100% on a couple things - do I need to set up an RMI server as below explicitly? Also when I try to convert the command line to a servlet, it doesn't seem to find the URL...from what you sent it looks like that the ports in both examples (config and code) should match? -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
RE: Monitoring CXF Webservices
In theory, if your server and consoler are in the same JVM you do not need to start a RMI server. But I don't think current CXF instrument manager provide this kind of feature. Anyway, you can fill a JIRA to add your wishes. Willem. -Original Message- From: Vespa, Anthony J [mailto:[EMAIL PROTECTED] Sent: Thu 11/15/2007 1:11 To: cxf-user@incubator.apache.org; Jiang, Ning (Willem) Subject: RE: Monitoring CXF Webservices Actually I have one last issue...is it possible to not set this up as a server implememntation but to access it like the other java MX beans? Eg can I do something like: ThreadMXBean tMxBean = ManagementFactory.getThreadMXBean(); tMxBean.getTotalStartedThreadCount(); I'd rather not start up an RMI instance. When I do, I can't seem to stop tomcat anymore - it just hangs when I try to shut down. Any help is appreciated. -Tony -Original Message- From: Vespa, Anthony J Sent: Monday, November 12, 2007 12:28 PM To: cxf-user@incubator.apache.org Subject: RE: Monitoring CXF Webservices Thank you for these examples but I am not 100% on a couple things - do I need to set up an RMI server as below explicitly? Also when I try to convert the command line to a servlet, it doesn't seem to find the URL...from what you sent it looks like that the ports in both examples (config and code) should match? -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
RE: Monitoring CXF Webservices
Hrm, in the servlet I wrote (basically turned that management class into a servlet) I just get blank output most of the time - it seems like it maybe one out of ten times it actually returns the endpoint info. Any thoughts? -Original Message- From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] Sent: Monday, November 12, 2007 12:47 PM To: cxf-user@incubator.apache.org Subject: RE: Monitoring CXF Webservices NO , you do not need to start up the RMI Server explicitly. Oh, the config file's URI is not match with the code (ManagementConsole.java). So you need to make sure the jmx server and client's URL are same. Willem. -Original Message- From: Vespa, Anthony J [mailto:[EMAIL PROTECTED] Sent: Tue 11/13/2007 1:28 To: cxf-user@incubator.apache.org Subject: RE: Monitoring CXF Webservices Thank you for these examples but I am not 100% on a couple things - do I need to set up an RMI server as below explicitly? Also when I try to convert the command line to a servlet, it doesn't seem to find the URL...from what you sent it looks like that the ports in both examples (config and code) should match? -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
RE: Monitoring CXF Webservices
Thank you for these examples but I am not 100% on a couple things - do I need to set up an RMI server as below explicitly? Also when I try to convert the command line to a servlet, it doesn't seem to find the URL...from what you sent it looks like that the ports in both examples (config and code) should match? -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/src/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/src/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
RE: Monitoring CXF Webservices
NO , you do not need to start up the RMI Server explicitly. Oh, the config file's URI is not match with the code (ManagementConsole.java). So you need to make sure the jmx server and client's URL are same. Willem. -Original Message- From: Vespa, Anthony J [mailto:[EMAIL PROTECTED] Sent: Tue 11/13/2007 1:28 To: cxf-user@incubator.apache.org Subject: RE: Monitoring CXF Webservices Thank you for these examples but I am not 100% on a couple things - do I need to set up an RMI server as below explicitly? Also when I try to convert the command line to a servlet, it doesn't seem to find the URL...from what you sent it looks like that the ports in both examples (config and code) should match? -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/src/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/src/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
Monitoring CXF Webservices
Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
Re: Monitoring CXF Webservices
Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony -- View this message in context: http://www.nabble.com/Monitoring-CXF-Webservices-tf4777853.html#a13667699 Sent from the cxf-user mailing list archive at Nabble.com.
RE: Monitoring CXF Webservices
That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony -- View this message in context: http://www.nabble.com/Monitoring-CXF-Webservices-tf4777853.html#a1366769 9 Sent from the cxf-user mailing list archive at Nabble.com.
RE: Monitoring CXF Webservices
Thank you for the tips! -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric data from JMX. Currently there is no sample or doc which talk about it . You can hack the console code[1] to find some information to write your own console. And you can find the configuration which could enable the JMX support on the server side here[2]. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/main/java/org/apache/cxf/management/utils/ManagementConsole.java [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/management/sr c/test/resources/managed-spring.xml Willem. Vespa, Anthony J wrote: That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config info, name etc) and do some trivial test besides just returning the whole WSDL or writing an additional function? Was just wondering if there was something baked in. I would envison this as something that would run in the same tomcat instance (like a another servlet) that I would access through an admin console I write. Thanks for any help! -Tony
