PK88797: UNABLE TO CREATE JAX-WS CLIENT DUE TO AXISFAULT: TWO SERVICES CANNOT HAVE THE SAME NAME

Fixes are available

APAR status

Closed as program error.

Error description

In a multi-threaded client environment, this exception might
occur:

org.apache.axis2.AxisFault: Two services cannot have same
name.  A  service with the HelloWorldService.
HelloWorldPort name already exists in the system.
org.apache.axis2.engine.AxisConfiguration.addToAllServicesMap(Ax
isConfiguration.java:390)
at
org.apache.axis2.description.AxisServiceGroup.addService(AxisSer
viceGroup.java:110)
at
org.apache.axis2.engine.AxisConfiguration.addService(AxisConfigu
ration.java:293)
at
org.apache.axis2.client.ServiceClient.configureServiceClient(Ser
viceClient.java:176)
at
org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:
144)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
getServiceClient(EndpointDescriptionImpl.java:1086)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
<init>(EndpointDescriptionImpl.java:265)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
<init>(EndpointDescriptionImpl.java:216)
at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.u
pdateEndpointDescription(ServiceDescriptionImpl.java:504)
at
org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.u
pdateEndpoint(DescriptionFactoryImpl.java:354)
at
org.apache.axis2.jaxws.description.DescriptionFactory.updateEndp
oint(DescriptionFactory.java:178)
at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:555)
at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:470)
at javax.xml.ws.Service.getPort(Service.java:161)
...

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7 JAX-WS clients                    *
****************************************************************
* PROBLEM DESCRIPTION: An AxisFault occurs when a JAX-WS       *
*                      client invokes                          *
*                      javax.xml.ws.Service.getPort().         *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR and  *
*                  related APAR PK84622.                       *
****************************************************************
In a multi-threaded client environment, even with APAR PK84622
applied, an exception like this might occur:

"org.apache.axis2.AxisFault: Two services cannot have same
name. A service with the HelloWorldService.HelloWorldPort
name already exists in the system."

PK84622 fixed a problem when multiple clients were
trying to call the same web service. Multiple
threads tried to create an AxisService using a name that was
already taken to create a previous AxisService; each AxisService
represented the same web service. However, in this case, the
clients try to call different web services represented by
services and ports with identical localpart names, but defined
in different namespaces, or accessible through different
endpoint addresses.

For example, client A tries to call the web service
whose WSDL is defined like the following:

<wsdl:definitions targetNamespace="http://hello.world/"
  xmlns="http://schemas.xmlsoap.org/wsdl/"
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
  ...
  <service name="HelloWorldService">
    <port name="HelloWorldPort"
binding="tns:HelloWorldPortBinding">
      <soap:address
location="http://myhost.com/service/HelloWorld"/>
    </port>
  </service>
</definitions>

While client B tries to call a separate web service whose WSDL
looks like this:

<wsdl:definitions
targetNamespace="http://hello.world/different/namespace/"
  xmlns="http://schemas.xmlsoap.org/wsdl/"
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
  ...
  <service name="HelloWorldService">
    <port name="HelloWorldPort"
binding="tns:HelloWorldPortBinding">
      <soap:address
location="http://myhost.com/service/HelloWorldPortType"/>
    </port>
  </service>
</definitions>

Problem conclusion

Additional synchronization was added to the JAX-WS
engine to prevent multiple threads from attempting to create
different AxisService objects with the same name.

The same fix is included in Feature Pack for Web Services under
APAR PM20275.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK88797
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-12
Closed date
2009-06-25
Last modified date
2010-08-11

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK88797: UNABLE TO CREATE JAX-WS CLIENT DUE TO AXISFAULT: TWO SERVICES CANNOT HAVE THE SAME NAME

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?