An operation with name '' already exists in this service
Here is a tip on how to avoid this type of exception with JAXWS but before let’s try to understand why your Service construciton fails… This exception occurs when your [...]
Here is a tip on how to avoid this type of exception with JAXWS but before let’s try to understand why your Service construciton fails… This exception occurs when your [...]
Just a quick note to show that the client factory choice is important with Apache CXF 2.1.4. The service interface definition : package org.ow2.petals.usecase.soapaddressing.server; import javax.jws.WebMethod; import javax.jws.WebService; /** * [...]
Here is a tip on the PEtALS JSR181 Service Engine (which is also available for all JSR181 annotated classes outside of PEtALS). Today, I spent some time on a customer [...]
This is a problem we met in the PEtALS SOAP Binding Component with large number of Axis2 Service Clients.
In this case, this error happens when too many sockets are open ant are waiting to be closed. Even if I have found some JIRAs about this problem and possible solutions, the only one which work for us is to cleanup the connection after each service call.
It is done like this :
|
… ServiceClient client = new ServiceClient(null, service); Options options = new Options(); … options.setCallTransportCleanup(true); client.setOptions(options);
OMElement outBodyElement = null; try { outBodyElement = serviceClient.sendReceive(soapAction, inBodyElement); } catch (AxisFault e) { throw e; } |
After 10 minutes test with 200 threads creating ‘one shot ‘ ServiceClient and almost 275000 service calls, all worked fine.