PK84622: A LONG-RUNNING JAX-WS CLIENT MIGHT ENCOUNTER "AXISFAULT: TWO SERVICES CANNOT HAVE SAME NAME" ERROR

Fixes are available

APAR status

Closed as program error.

Error description

Multiple JAX-WS clients accessing the same webserivce which
calls the method  javax.xml.ws.Service.getPort() may cause the
following exception.

javax.xml.ws.WebServiceException: The ServiceClient cannot be
created.
  at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:178)
  at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:79)
  at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
getServiceClient(EndpointDescriptionImpl.java:1018)

...
 Caused by: org.apache.axis2.AxisFault:

org.apache.axis2.AxisFault: Two services cannot have same
name.  A service with the
HelloWorldWebService.HelloWorldPort1517705846
name already exists in the system.
 at
org.apache.axis2.client.ServiceClient.configureServiceClient(Ser
viceClient.java:142)
 at
org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:
125)
 at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
getServiceClient(EndpointDescriptionImpl.java:1015)
 at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
<init>(EndpointDescriptionImpl.java:232)
 at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
<init>(EndpointDescriptionImpl.java:189)
 at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.u
pdateEndpointDescription(ServiceDescriptionImpl.java:317)
 at
org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.u
pdateEndpoint(DescriptionFactoryImpl.java:241)
 at
org.apache.axis2.jaxws.description.DescriptionFactory.updateEndp
oint(DescriptionFactory.java:102)
 at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:242)
 at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:217)
 at javax.xml.ws.Service.getPort(Service.java:120)
 ...

Local fix

Target to be fix in next release

Put a synchronization block around calls to getPort()

or actual local solution was below:

Work around: Application is modified not to create a service
name in order not to throw error in systemOut.log.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of JAX-WS web servicves clients       *
*                  running in IBM WebSphere Application        *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: When running a JAX-WS client, a         *
*                      "org.apache.axis2.AxisFault: Two        *
*                      services cannot have same name" error   *
*                      might occur.                            *
****************************************************************
* RECOMMENDATION:  Install a fixpack that includes this APAR.  *
****************************************************************
A JAX-WS client might contain code like this:

Object endpoint = service.getPort(endpointClass);

where service is an instance of javax.xml.ws.Service. The
getPort() method returns a stub that the client invokes to
call the JAX-WS endpoint.

If a JAX-WS client runs over a long period of time, making many
calls to Service.getPort(), an error like this might occur:

org.apache.axis2.AxisFault: Two services cannot have same
name.  A service with the
HelloWorldWebService.HelloWorldPort1517705846
name already exists in the system.
 at
org.apache.axis2.client.ServiceClient.configureServiceClient(Ser
viceClient.java:142)
 at
org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:
125)
 at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
getServiceClient(EndpointDescriptionImpl.java:1015)
 at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
<init>(EndpointDescriptionImpl.java:232)
 at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
<init>(EndpointDescriptionImpl.java:189)
 at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.u
pdateEndpointDescription(ServiceDescriptionImpl.java:317)
 at
org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.u
pdateEndpoint(DescriptionFactoryImpl.java:241)
 at
org.apache.axis2.jaxws.description.DescriptionFactory.updateEndp
oint(DescriptionFactory.java:102)
 at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:242)
 at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:217)
 at javax.xml.ws.Service.getPort(Service.java:120)
 ...

Problem conclusion

The error is due to multiple threads simultaneously calling
an internal method in the JAX-WS engine. The method was
changed to be synchronized so that only one thread at a time
can call it.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.27 and 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
PK84622
Reported component name
WAS EXPRESS
Reported component ID
5724I6300
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-14
Closed date
2009-05-13
Last modified date
2009-08-19

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
WEBSERVIC FEATU
Fixed component ID
5724J0850

Applicable component levels

R610 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK84622: A LONG-RUNNING JAX-WS CLIENT MIGHT ENCOUNTER "AXISFAULT: TWO SERVICES CANNOT HAVE SAME NAME" ERROR

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

R610 PSY

Document Information

Share your feedback

Need support?