Hello, Your problem is solved in CXF 2.2.5.
This NullPointerException you have with version 2.2.4 has been fixed by commit 830533 : "[CXF-2505, CXF-2502, CXF-2489] Bunch of fixes for WS-A + WS-Sec + Mgmt" that is included in version 2.2.5. Cyrille -- Cyrille Le Clerc [email protected] http://blog.xebia.fr http://fisheye6.atlassian.com/browse/cxf/trunk/rt/management/src/main/java/org/apache/cxf/management/interceptor/AbstractMessageResponseTimeInterceptor.java?r1=830533&r2=760073 On Tue, Nov 24, 2009 at 5:56 PM, Sergey Beryozkin <[email protected]> wrote: > > Hi > > Cyrille has recently opened > > http://issues.apache.org/jira/browse/CXF-2541 > > cheers, Sergey > > ----- Original Message ----- From: "devylon" <[email protected]> > To: <[email protected]> > Sent: Tuesday, November 24, 2009 4:51 PM > Subject: JAX-RS service and JMX Performance Monitoring > > >> >> I'm just wondering if the JMX performance monitoring has an issue with JAX-RS >> services. >> My project contains soap web-services as well as jax-rs services. >> >> i enabled jmx monitoring in my spring context: >> <bean id="org.apache.cxf.management.InstrumentationManager" >> class="org.apache.cxf.management.jmx.InstrumentationManagerImpl"> >> <property name="bus" ref="cxf" /> >> <property name="enabled" value="true" /> >> <property name="usePlatformMBeanServer" value="true" /> >> </bean> >> <bean id="CounterRepository" >> class="org.apache.cxf.management.counters.CounterRepository" > >> <property name="bus" ref="cxf" /> >> </bean> >> >> when ever i invoke the soap web-service operation everything is fine. BUT >> when i call a jax-rs service i got an exception in my stacktrace: >> 2009-11-24 16:59:19,715 WARN | >> org.apache.cxf.common.logging.LogUtils.doLog(345) | Interceptor has thrown >> exception, unwinding now >> java.lang.NullPointerException >> at >> org.apache.cxf.management.interceptor.AbstractMessageResponseTimeInterceptor.increaseCounter(AbstractMessageResponseTimeInterceptor.java:111) >> at >> org.apache.cxf.management.interceptor.AbstractMessageResponseTimeInterceptor.endHandlingMessage(AbstractMessageResponseTimeInterceptor.java:74) >> at >> org.apache.cxf.management.interceptor.ResponseTimeMessageOutInterceptor.handleMessage(ResponseTimeMessageOutInterceptor.java:42) >> at >> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) >> at >> org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:74) >> at >> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) >> at >> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:104) >> at >> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98) >> at >> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:392) >> at >> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:133) >> at >> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142) >> at >> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:50) >> >> is this a bug in cxf ? i'm using version 2.2.4 >> >> best, >> ingo >> -- >> View this message in context: >> http://old.nabble.com/JAX-RS-service-and-JMX-Performance-Monitoring-tp26498558p26498558.html >> Sent from the cxf-user mailing list archive at Nabble.com. >> >
