Direct links to fixes
APAR status
Closed as program error.
Error description
Environment: ------------ BPM Advanced 8.0.1.2 WAS 8.0.0.9 Scenario: --------- Client has an application containing a web service import binding and tries to call a remote web service. Behavior: --------- On response handling the below error is thrown: [13.07.16 13:47:04:945 CEST] FFDC Exception:java.lang.IllegalArgumentException SourceId:com.ibm.ws.sca.internal.message.impl.MessageDispatcher Impl.processMessageWithPCI ProbeId:720 Reporter:com.ibm.ws.sca.internal.message.impl.MessageDispatcher Impl@355 54065 java.lang.IllegalArgumentException: The 'no null' constraint is violated at org.eclipse.emf.common.util.BasicEList.validate(BasicEList. java:172) at org.eclipse.emf.ecore.util.EcoreEList.validate(EcoreEList. java:59) at org.eclipse.emf.common.util.BasicEList.addAllUnique(Basic EList.java: 774) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.doAdd AllUnique(NotifyingListImpl.java:494) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.add AllUnique(NotifyingListImpl.java:467) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.add AllUnique(NotifyingListImpl.java:396) at org.eclipse.emf.common.util.BasicEList.addAll(BasicEList. java:688) at com.ibm.wsspi.sca.scdl.impl.OperationTypeAdapterImpl.get ExceptionTypes(OperationTypeAdapterImpl.java:138) at com.ibm.ws.bpm.session.policy.SessionHandler.isOneWay Operation(SessionHandler.java:904) at com.ibm.ws.bpm.session.policy.SessionHandler.getSession OperationType(SessionHandler.java:391) at com.ibm.ws.bpm.session.policy.SessionHandler.processMessage (SessionHandler.java:211) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl. processMessageWithPCI(MessageDispatcherImpl.java:785) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl. processMessage(MessageDispatcherImpl.java:1626) at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl. process(ManagedMessageImpl.java:990) at com.ibm.ws.sibx.mediation.flowaction.impl.sca.SCAInvocation Action.invokeSync(SCAInvocationAction.java:554) Cause: ------ It has been figured out that the type definition in the wsdl that defines the web service contains an element wit a null namespace. This did lead to the above exception.
Local fix
Workaround: Add a namespace to the type definition that contain a null namespace, and ensure that this namespace gets taken in account by type definitions that use the changed type definition and as well within subsequent message definition as needed.
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM Business Process Manager (BPM) * * Advanced * **************************************************************** * PROBLEM DESCRIPTION: When you use a web service binding * * that has a special WSDL definition * * and is in the lazy parsing mode, you * * might receive the following error: * * Exception:java.lang.IllegalArgumentExce * * ption * * SourceId:com.ibm.ws.sca.internal.messag * * e.impl.MessageDispatcher * * Impl.processMessageWithPCI * * ProbeId:720 * * Reporter:com.ibm.ws.sca.internal.messag * * e.impl.MessageDispatcher * * Impl@355 54065 * * java.lang.IllegalArgumentException: * * The 'no null' constraint is * * violated * * at * * org.eclipse.emf.common.util.BasicEList. * * validate(BasicEList. * * java:172) * * at * * org.eclipse.emf.ecore.util.EcoreEList.v * * alidate(EcoreEList. * * java:59) * * at * * org.eclipse.emf.common.util.BasicEList. * * addAllUnique(Basic * * EList.java: 774) * * at * * org.eclipse.emf.common.notify.impl.Noti * * fyingListImpl.doAdd * * AllUnique(NotifyingListImpl.java:494) * * at * * org.eclipse.emf.common.notify.impl.Noti * * fyingListImpl.add * * AllUnique(NotifyingListImpl.java:467) * * at * * org.eclipse.emf.common.notify.impl.Noti * * fyingListImpl.add * * AllUnique(NotifyingListImpl.java:396) * * at * * org.eclipse.emf.common.util.BasicEList. * * addAll(BasicEList. * * java:688) * * at * * com.ibm.wsspi.sca.scdl.impl.OperationTy * * peAdapterImpl.get * * ExceptionTypes(OperationTypeAdapterImpl * * .java:138) * * at * * com.ibm.ws.bpm.session.policy.SessionHa * * ndler.isOneWay * * Operation(SessionHandler.java:904) * * at * * com.ibm.ws.bpm.session.policy.SessionHa * * ndler.getSession * * OperationType(SessionHandler.java:391) * * at * * com.ibm.ws.bpm.session.policy.SessionHa * * ndler.processMessage * * (SessionHandler.java:211) * * at * * com.ibm.ws.sca.internal.message.impl.Me * * ssageDispatcherImpl. * * processMessageWithPCI(MessageDispatcher * * Impl.java:785) * * at * * com.ibm.ws.sca.internal.message.impl.Me * * ssageDispatcherImpl. * * processMessage(MessageDispatcherImpl.ja * * va:1626) * * at * * com.ibm.ws.sca.internal.message.impl.Ma * * nagedMessageImpl. * * process(ManagedMessageImpl.java:990) * * at * * com.ibm.ws.sibx.mediation.flowaction.im * * pl.sca.SCAInvocation * * Action.invokeSync(SCAInvocationAction.j * * ava:554) * **************************************************************** * RECOMMENDATION: * **************************************************************** An element defined with a null namespace in the <schema> section of a WSDL schema can't be loaded by business object in lazy parsing mode, for example <xsd:schema> <xsd:element name="element01" type="tns02:Element01Type"/> </xsd:schema> The element01 element would not be loaded by a business object in the lazy parsing mode.
Problem conclusion
A fix is available for IBM BPM V8.0.1.2 that ensures the elements defined with a null namespace in the <schema> section of a WSDL schema can be loaded in lazy parsing mode. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR56542: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR56542, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Temporary fix
Comments
APAR Information
APAR number
JR56542
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-23
Closed date
2016-09-06
Last modified date
2016-09-06
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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
06 September 2016