Fix (APAR): JR27912 Status: Fix Release: 6.0.2.3 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: JR27912 Byte size of APAR: 21730 Date: 2007-12-04 Abstract: WebServices-Bindings with all the encoding styles using Async Deferred Response Invocation with Multiple WSDL references fails with EBoolean (null) Exception while sending the Busi Description/symptom of problem: JR27912 resolves the following problem: ERROR DESCRIPTION: WS-Bindings with RPC literal style using Async Deferred Response, with Multiple WSDL references fails with EBoolean (null) exception while sending BG across modules with SOAP over HTTP. The exception seen is a follows: Caused by: com.ibm.websphere.sca.ServiceRuntimeException: java.lang.IllegalArgumentException: Unable to locate classifier with uri (null)EBoolean: caused by: java.lang.IllegalArgumentException: Unable to locate classifier with uri (null)EBoolean at com.ibm.wsspi.sca.webservice.bean.impl.WebServiceBeanImpl.proces sInvoke(WebServiceBeanImpl.java:283) at com.ibm.wsspi.sca.webservice.ejb.impl.WebServiceSessionBean.invo keWS(WebServiceSessionBean.java:147) at com.ibm.wsspi.sca.webservice.ejb.impl.WebServiceSessionBean.invo ke(WebServiceSessionBean.java:135) ... 37 more Caused by: java.lang.IllegalArgumentException: Unable to locate classifier with uri (null)EBoolean LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: Websphere Process Server 6.0.2.3 users using Async Deferred Response Invocation with multiple WSDL references. PROBLEM DESCRIPTION: WebServices-Bindings with all the encoding styles using Async Deferred Response Invocation with Multiple WSDL references fails with EBoolean (null) Exception while sending the BusinessGraph across the modules with SOAP over HTTP. Same error can be seen while sending the BusinessGraph and receiving Business Object inlined in WSDL with SOAP over JMS. RECOMMENDATION: None The ChangeSummary of a BusinessGraph contains a reference to the BusinessGraph itself, and the caused SOAP deserialization error. The circular reference creates a stack overflow error of Websphere Application Server webservice engine and breaks Websphere Process Server webservices. Sample Error Trace: at com.ibm.ws.tcp.channel.impl.WorkQueueManager. requestComplete(WorkQueueManager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO (WorkQueueManager.java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun (WorkQueueManager.java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run (WorkQueueManager.java:1039) at com.ibm.ws.util.ThreadPool$Worker.run (ThreadPool.java:1471) Caused by: com.ibm.websphere.sca.ServiceRuntimeException: java.lang.IllegalArgumentException: Unable to locate classifier with uri (null)EBoolean: caused by: java.lang.IllegalArgumentException: Unable to locate classifier with uri (null)EBoolean at com.ibm.wsspi.sca.webservice.bean.impl.WebServiceBeanImpl. processInvoke(WebServiceBeanImpl.java:283) at com.ibm.wsspi.sca.webservice.ejb.impl.WebServiceSessionBean. invokeWS(WebServiceSessionBean.java:147) at com.ibm.wsspi.sca.webservice.ejb.impl.WebServiceSessionBean. invoke(WebServiceSessionBean.java:135) ... 37 more Caused by: java.lang.IllegalArgumentException: Unable to locate classifier with uri (null)EBoolean at com.ibm.ws.sca.internal.webservice.mediator. DocumentMediator.getClassifier(DocumentMediator.java:154) at com.ibm.ws.sca.internal.webservice.mediator. RPCEncodedMediator.readRPCDataItem(RPCEncodedMediator.java:1089) at com.ibm.ws.sca.internal.webservice.mediator. RPCEncodedMediator.readRPCStruct(RPCEncodedMediator.java:1040) at com.ibm.ws.sca.internal.webservice.mediator. RPCEncodedMediator.readRPCDataItem(RPCEncodedMediator.java:1101) at com.ibm.ws.sca.internal.webservice.mediator. RPCEncodedMediator.readDataObject(RPCEncodedMediator.java:898) at com.ibm.ws.sca.internal.webservice.mediator. DocumentMediator.deserialize(DocumentMediator.java:583) at com.ibm.ws.sca.internal.webservice.mediator. DocumentMediator.deserialize(DocumentMediator.java:539) at com.ibm.ws.sca.internal.webservice.mediator. DocumentMediator.deserialize(DocumentMediator.java:416) at com.ibm.ws.sca.internal.webservice.mediator. RPCEncodedMediator.deserialize(RPCEncodedMediator.java:848) at com.ibm.ws.sca.internal.webservice.mediator. RPCEncodedMediator.deserialize(RPCEncodedMediator.java:765) at com.ibm.ws.sca.internal.webservice.mediator. DocumentMediator.deserialize(DocumentMediator.java:373) at com.ibm.ws.sca.internal.webservice.util. WebServiceLazyParsingUtil.parseBody (WebServiceLazyParsingUtil.java PROBLEM CONCLUSION: Interiem fix JR27912 allows the user to use Webservices Binding using Async Deferred Response Invocation along with multiple WSDL references. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: