PM18738: JAX-RPC WEB SERVICE HANDLER IS NOT INVOKED.

Fixes are available

APAR status

Closed as program error.

Error description

After upgrading WebSphere Application Server to v6.1.0.29,
JAX-RPC handlers configured in a web service Dynamic
Interface Invocation (DII) client do not get invoked.

This problem does not result in a specific exception.  Rather,
the application might encounter unpredictable behavior which is
caused by the JAX-RPC handler not getting invoked.

Local fix

Instead of doing a no argument call to Service.createCall,
try using this:

Service.createCall(portTypeName, operationQName)

Do not call Call.setPortTypeName(portType), or
Call.setOperationName(operationQName).

Here's an example of the modified code in WebserviceClientCall:
 ServiceFactory sf = ServiceFactory.newInstance();
 QName serviceQname = new QName(targetNamespace, serviceName);
 QName portTypeName = new QName(targetNamespace,portType);
 QName operationQName = new QName(targetNamespace,
   operationName);
 javax.xml.rpc.Service service =
   (javax.xml.rpc.Service)sf.createService(serviceQname);
 javax.xml.rpc.Call call =
   service.createCall(portTypeName,operationQName);
 //Don't need to do this -> call.setOperationName(new
 //   QName(targetNamespace, operationName));
 call.setProperty(Call.OPERATION_STYLE_PROPERTY,
   operationStyle);
 call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");
 call.setProperty(Call.SOAPACTION_URI_PROPERTY,targetNamespace);
 call.setProperty(Call.SOAPACTION_USE_PROPERTY,
   Boolean.TRUE);
 call.setTargetEndpointAddress(endPointAddress);
 //Don't need to do this -> call.setPortTypeName(new
 //   QName (targetNamespace,portType));

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0 and JAX-RPC DII        *
*                  clients.                                    *
*                                                              *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: JAX-RPC Web service handlers may not    *
*                      get invoked for DII clients after       *
*                      upgrading to WebSphere Application      *
*                      Server V6.1.0.29.                       *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR.     *
****************************************************************
After upgrading WebSphere Application Server to v6.1.0.29,
JAX-RPC handlers configured in a web service Dynamic
Interface Invocation (DII) client do not get invoked.

This may happen if the DII client has all of the following
characteristics:
a) It does not specify a WSDL file
b) It does not specify a portName on the call to
Service.createCall()
c) It uses Call.setPortTypeName to set the portName
d) It configures JAX-RPC handlers in the handlerChain using
the same portName set in c) above.

Here is an example of the failing client:

javax.xml.rpc.Service service =
(javax.xml.rpc.Service)sf.createService(serviceQname);
javax.xml.rpc.Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
HandlerRegistry hr=service.getHandlerRegistry();
List<HandlerInfo> list = new ArrayList<HandlerInfo>();
HandlerInfo hi=new HandlerInfo(SampleHandler.class,null,null);
list.add(hi);
hr.setHandlerChain(portName, list);
call.invoke(input);

In this case, the SampleHandler would not get invoked on the
client.

This problem does not result in a specific exception.  Rather,
the application might encounter unpredictable behavior which is
caused by the JAX-RPC handler not getting invoked.

Problem conclusion

The failure in this case is happening because of the use of
Call.setPortTypeName to set the portName.  Under most
circumstances the portName is set when the Call object is
created, either by passing it to Service.callCreate or by
deriving it from the WSDL.

Prior to V6.1.0.29, Call.setPortTypeName could be used to set
or reset the portName after the Call object was created.  APAR
PK93531 removed this capability on the grounds that the
portTypeName and portName are actually two different things
and should not be interchanged.  However, this has caused some
compatibility issues.

The fix is to allow Call.setPortTypeName to be used to set the
portName only if the portName has not already been derived
from the WSDL or passed as a parameter to Service.createCall.
If the portName is already established, setPortTypeName will
not overwrite it.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.15 and 6.1.0.35.  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
PM18738
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-07-19
Closed date
2010-09-07
Last modified date
2010-09-07

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM18738: JAX-RPC WEB SERVICE HANDLER IS NOT INVOKED.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?