Last updated on APRIL 22, 2016
Applies to:Oracle Web Services Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Web Services Policy Server
During a load- and performance-tests against a mock JAX-WS based webservice
provider (HotelService), using a test driver (SOAPUI), and both a composed service (Mediator/BPEL),
acting as consumer, and a standard JAX-WS based webservice consumer.
Request routing is done via OSB. Custom-made policies (called WESPE (WEb service Security and Policy
Enforcement)) are applied via a central OWSM PolicyManager.
The following scheme depicts the test setup.
Test scenario 2) test driver -> composed service <-> OSB <-> JAX-WS provider (HotelService)
Test scenario 2b) test driver -> JAX-WS consumer <-> OSB <-> JAX-WS provider (HotelService)
In test scenario 2b, on the JAX-WS consumer side(!!), it was observed the memory leak.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms