Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.158 is neither permitted
 nor denied by domain of bauer.gernot@gmail.com)
Date: Fri, 30 Jul 2010 05:13:16 -0700 (PDT)
From: gbauer <bauer.gernot@gmail.com>
To: users@cxf.apache.org
Message-ID: <1280491996864-2259459.post@n5.nabble.com>
In-Reply-To: <004901cb2f3a$9924b740$cb6e25c0$@org>
References: <1280418259849-2256734.post@n5.nabble.com>
 <004901cb2f3a$9924b740$cb6e25c0$@org>
Subject: RE: Using JMX to start and stop web services
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hello!

Sorry for omitting important information, I was in a rush yesterday. I am
using CXF v2.2.9 and JaxWs as frontend. I create the endpoints by using
Spring and I deploy the application as war on a tomcat6 servlet container.
My configuration is pretty similar to the example configuration on the CXF
homepage (my web.xml[1] and beans.xml[2]).

I had a look at your testcase and it worked as one would expect.
Nevertheless when I stop and start my endpoint by using JMX, I cannot access
it even though getState returns "STARTED" again. It is not listed under
"Available SOAP services" when I access the servlet by using my browser and
every attempt to connect to the service results in "HTTP response '404: Not
Found'".

I managed to achieve a workaround by using Tomcat's JMX interface and
calling reload() in the Catalina/WebModule branch. However, I am not sure
about the side effects of this operation and still wondering if it is
possible to restart a single endpoint without reloading the whole webmodule.

Kind regards,
Gernot

[1] http://pastebin.com/nTh81SY8
[2] http://pastebin.com/yLN8ExFZ


dvaleri wrote:
> 
> Which type of service are you trying to control (what frontend) and what
> version of CXF are you using?
> 
> This JIRA ticket[1] dealt with similar functionality; however, the tests
> may
> not actually cover checking if the service is listening again and may only
> check that the JMX state is correct.  See ManagedClientServerTest.java [2]
> for an example that uses JMX to control a published endpoint from the
> JAX-WS
> frontend.
> 
> [1] https://issues.apache.org/jira/browse/CXF-2740 
> [2]
> https://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/j
> ava/org/apache/cxf/systest/management/ManagedClientServerTest.java
> 
> -----Original Message-----
> From: gbauer [mailto:bauer.gernot@gmail.com] 
> Sent: Thursday, July 29, 2010 11:44 AM
> To: users@cxf.apache.org
> Subject: Using JMX to start and stop web services
> 
> 
> Hello!
> 
> I want to use JMX to temporarily disable an endpoint and enable it
> afterwards. I managed to configure JMX according to
> http://cxf.apache.org/docs/jmx-management.html and I am able to stop the
> service by using the stop-method available in the jmx console (as seen on
> one screenshot in the link above). However, if i want to restart the
> service
> using start(), the endpoint doesn't seem to get republished.
> 
> Is this a bug or did I miss something (which would be quite likely since
> im
> fairly new to CXF)?
> 
> King regards and
> 
> TIA,
> Gernot
> -- 
> View this message in context:
> http://cxf.547215.n5.nabble.com/Using-JMX-to-start-and-stop-web-services-tp2
> 256734p2256734.html
> Sent from the cxf-user mailing list archive at Nabble.com.
> 
> 
> 
-- 
View this message in context: http://cxf.547215.n5.nabble.com/Using-JMX-to-start-and-stop-web-services-tp2256734p2259459.html
Sent from the cxf-user mailing list archive at Nabble.com.