Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.2.4
-
None
-
None
Description
I've updated the ws-security\ut sample and added the management dependency in the pom and updated the wssec.xml for the server:
<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="threaded" value="false" />
<property name="daemon" value="false" />
<property name="JMXServiceURL" value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi" />
</bean>
<!-- Wiring the counter repository -->
<bean id="CounterRepository" class="org.apache.cxf.management.counters.CounterRepository">
<property name="bus" ref="cxf" />
</bean>
Run the server with: mvn -Pserver
Run the client with: mvn -Pclient
8 invocations will occur.
Now, change the UTPasswordCallback.java of the client (done already in attachment)
public UTPasswordCallback()
{ passwords.put("Alice", "ecilACHANGED"); passwords.put("abcd", "dcbaCHANGED"); }and run the client again. There is no update in the Performance.Counter MBean.
I also noticed that the Performance.Counter MBean is not visible in the JConsole till the first request is processed.
When my first run is with invalid passwords, the Performance.Counter MBean is not added in the JConsole.
Attachments
Attachments
Issue Links
- is related to
-
CXF-2502 decoupled WS-A and WS-Sec does not result in faults back to clients
- Closed