BPM Build Error after updating from CE 7.2 SP03 to CE 7.2 SP09

[former_member251241]

Hi experts

We have several process developed on version CE 7.2 SP03. After upgrading to CE 7.2 SP09 most of the processes compile correctly except a couple of them with the error shown below.

I have updated NWDI track to match portal version, I've tried refreshing all mappings and even deleting every task and process in the project to figure out where the error could be, but I always got the same error.

BC-BMT-BPM-SRV com.sap.tc.glx.BpemTask execute() - Initiating data mapping validation.

Error: H:\ws7290\vendors.jdi\0\t2\5F8F7BE32A45149E8A44E8A75ACADC7E\default\logs\build.xml:81: java.lang.NullPointerException

  at org.apache.tools.ant.Task.perform(Task.java:373)

  at org.apache.tools.ant.Target.execute(Target.java:341)

  at org.apache.tools.ant.Target.performTasks(Target.java:369)

  at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)

  at org.apache.tools.ant.Project.executeTarget(Project.java:1185)

  at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:114)

  at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:57)

  at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:195)

  at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:167)

  at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)

  at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:403)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:149)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:87)

  at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)

  at com.sap.tc.devconf.internal.DCProxyMake.make(DCProxyMake.java:319)

  at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1448)

  at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1430)

  at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:3891)

  at com.sap.ide.dii05.lib.internal.commands.dc.BuildJob.build(BuildJob.java:370)

  at com.sap.ide.dii05.lib.internal.commands.dc.BuildJob.doInWorkerThread(BuildJob.java:181)

  at com.sap.ide.dii05.util.api.job.JdiJob$1.doInWorkerThread(JdiJob.java:77)

  at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3$1.run(InternalJdiJob.java:199)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)

  at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3.run(InternalJdiJob.java:208)

  at com.sap.ide.dii05.util.internal.job.BusyBackgroundIndicator.showWhile(BusyBackgroundIndicator.java:74)

  at com.sap.ide.dii05.util.internal.job.InternalJdiJob.internalRun(InternalJdiJob.java:189)

  at com.sap.ide.dii05.util.internal.job.InternalDiiJob.runInternal(InternalDiiJob.java:306)

  at com.sap.ide.dii05.util.internal.job.InternalDiiJob.runR(InternalDiiJob.java:204)

  at com.sap.ide.dii05.util.internal.job.InternalDiiJob.run(InternalDiiJob.java:192)

  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: java.lang.NullPointerException

  at com.sap.glx.paradigmInterface.util.BaseMappingsUtil.getMappingScope(BaseMappingsUtil.java:188)

  at com.sap.glx.paradigmInterface.util.BaseMappingsUtil.getScope(BaseMappingsUtil.java:175)

  at com.sap.glx.paradigmInterface.util.ContextFactory.createGlobalContextForMappableObject(ContextFactory.java:291)

  at com.sap.glx.paradigmInterface.mappings.MappableObjectContextProvider.createMappingContext(MappableObjectContextProvider.java:23)

  at com.sap.glx.paradigmInterface.mappings.MappingContextProvider.createMappingContext(MappingContextProvider.java:43)

  at com.sap.glx.paradigmInterface.mappings.MappingContextProvider.getMappingContext(MappingContextProvider.java:26)

  at com.sap.glx.paradigmInterface.mappings.TransformationContextProvider.getMappingContext(TransformationContextProvider.java:37)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider$3.getUncachedValue(CachingContextProvider.java:58)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider$3.getUncachedValue(CachingContextProvider.java:54)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider$Cache.get(CachingContextProvider.java:137)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider.getMappingContext(CachingContextProvider.java:88)

  at com.sap.mapping.dtmodel.validation.impl.MappingValidator.validate(MappingValidator.java:52)

  at com.sap.mapping.dtmodel.validation.impl.MappingValidator.validate(MappingValidator.java:34)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validate(DataMappingValidator.java:111)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validate(DataMappingValidator.java:103)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validateMappings(DataMappingValidator.java:90)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validate(DataMappingValidator.java:71)

  at com.sap.tc.glx.MappingValidator.validate(MappingValidator.java:72)

  at com.sap.tc.glx.BpemTask.execute(BpemTask.java:219)

  at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

  at org.apache.tools.ant.Task.perform(Task.java:364)

  ... 35 more

--- Nested Exception ---

java.lang.NullPointerException

  at com.sap.glx.paradigmInterface.util.BaseMappingsUtil.getMappingScope(BaseMappingsUtil.java:188)

  at com.sap.glx.paradigmInterface.util.BaseMappingsUtil.getScope(BaseMappingsUtil.java:175)

  at com.sap.glx.paradigmInterface.util.ContextFactory.createGlobalContextForMappableObject(ContextFactory.java:291)

  at com.sap.glx.paradigmInterface.mappings.MappableObjectContextProvider.createMappingContext(MappableObjectContextProvider.java:23)

  at com.sap.glx.paradigmInterface.mappings.MappingContextProvider.createMappingContext(MappingContextProvider.java:43)

  at com.sap.glx.paradigmInterface.mappings.MappingContextProvider.getMappingContext(MappingContextProvider.java:26)

  at com.sap.glx.paradigmInterface.mappings.TransformationContextProvider.getMappingContext(TransformationContextProvider.java:37)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider$3.getUncachedValue(CachingContextProvider.java:58)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider$3.getUncachedValue(CachingContextProvider.java:54)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider$Cache.get(CachingContextProvider.java:137)

  at com.sap.mapping.dtmodel.validation.CachingContextProvider.getMappingContext(CachingContextProvider.java:88)

  at com.sap.mapping.dtmodel.validation.impl.MappingValidator.validate(MappingValidator.java:52)

  at com.sap.mapping.dtmodel.validation.impl.MappingValidator.validate(MappingValidator.java:34)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validate(DataMappingValidator.java:111)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validate(DataMappingValidator.java:103)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validateMappings(DataMappingValidator.java:90)

  at com.sap.glx.paradigmInterface.bpmn.compiler.mapping.DataMappingValidator.validate(DataMappingValidator.java:71)

  at com.sap.tc.glx.MappingValidator.validate(MappingValidator.java:72)

  at com.sap.tc.glx.BpemTask.execute(BpemTask.java:219)

  at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

  at org.apache.tools.ant.Task.perform(Task.java:364)

  at org.apache.tools.ant.Target.execute(Target.java:341)

  at org.apache.tools.ant.Target.performTasks(Target.java:369)

  at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)

  at org.apache.tools.ant.Project.executeTarget(Project.java:1185)

  at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:114)

  at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:57)

  at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:195)

  at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:167)

  at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)

  at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:403)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:149)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:87)

  at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)

  at com.sap.tc.devconf.internal.DCProxyMake.make(DCProxyMake.java:319)

  at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1448)

  at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1430)

  at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:3891)

  at com.sap.ide.dii05.lib.internal.commands.dc.BuildJob.build(BuildJob.java:370)

  at com.sap.ide.dii05.lib.internal.commands.dc.BuildJob.doInWorkerThread(BuildJob.java:181)

  at com.sap.ide.dii05.util.api.job.JdiJob$1.doInWorkerThread(JdiJob.java:77)

  at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3$1.run(InternalJdiJob.java:199)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)

  at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3.run(InternalJdiJob.java:208)

  at com.sap.ide.dii05.util.internal.job.BusyBackgroundIndicator.showWhile(BusyBackgroundIndicator.java:74)

  at com.sap.ide.dii05.util.internal.job.InternalJdiJob.internalRun(InternalJdiJob.java:189)

  at com.sap.ide.dii05.util.internal.job.InternalDiiJob.runInternal(InternalDiiJob.java:306)

  at com.sap.ide.dii05.util.internal.job.InternalDiiJob.runR(InternalDiiJob.java:204)

  at com.sap.ide.dii05.util.internal.job.InternalDiiJob.run(InternalDiiJob.java:192)

  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Thanks in advance.

Javier

[former_member191643 · Accepted solution]

Hi Javier,

I don't think this is an issue with the upgrade. I understand that you have re-done your mappings again too, but this error is related to some context mapping. Check if you have used any built-in functions which need to be corrected. Make sure to 'Update' the process pool as and when the changes are made to the mappings.

Also, if none of this seems relevant, please check the nwa logs for exact cause. Access the nwa logs from here: http://<host>:<port>/nwa/logs

Set the filters to 'System logs and traces' and severity as 'error'.

Hope this helps.

Regards,

Sid.

[Former Member]

Hello,

We are facing same problem reported at the bigining of this forum. We had Netweaver 7.2 and now 7.4.

We migrate the nwdi track were we had the BPM project, and now the project appears as break in the track.

When I download the BPM projet to NWDS it does not show any error. But when buiding it, the error shows again.

I have checked mapping tasks, also every output and input mapping in every task and I dont see nothing wrong.

How to fix the BPM project ?

[ch_loos]

Hi Felipe,

please open a support ticket with SAP so that support can look into this.

In previous cases, the root cause was an inconsistency in the BPM model file which had to be fixed manually.

But this is only possible after thorough analysis.

Regards,

Christian

[Former Member]

Hi Christian !

We opened a support ticket last thursday. I asked if I could see the SAP note mentioned above, but so far they just asked me to send them the list of SC used.

Is there a way to send a "please do not forget me message" to SAP support ?

Regards,

[former_member251241]

Hi everyone

I could not figure out exactly  what the error was provoked by. However I found that mc/META-INF/servicereferences.servicerefs file was corrupted. After refreshing everything I mentioned in the initial post. I had to delete every "service reference" in my project and refresh automated activities pointing my services. Actually when I initially tried to remove the references, the studio fails with a null pointer exception, so I had to "fix" "servicereferences.servicerefs" by hand copying the definition from another project.

Finally that's the way the problem was "solved".

Regards.

Javier

[Former Member]

Hi,

I finally created a new DC, copied the xsd and exported the process definition of the old DC and imported it into the new one. This way I don't have to do the modelling once again, but triggers, data mapping etc still has to be done once again. Simply copying the source files wasn't successful. This way is fine for me as we have a seperate server installation for the upgrade. It may not work if the new DC with same namespaces as "old" DC has to be deployed on the same server.

Regards,

Anja

[ch_loos]

see SAP note 1841928

[Former Member]

Thanks Christian. But I cannot access the note: 'Document is not released'.

Does it require a special migration procedure to get the sources from one SP to another? For another project I updated the SCAs in NWDI to 7.31SPS06, checked out the BPM-sources and could compile it without problems. I found a document that mentions a migration wizard that starts automatically when checking out sources from NWDI that where created with an older version than the NWDS. But this wizard doesn't start in my case.

Thanks for any hints.

Regards,

Anja

[Former Member]

Unfortunately, I also can not open this note because it is not released yet.

Christian, could you send text of this note to my mail (amchuglin@gmail.com) or reply on this topic.

Thank you!

[Former Member]

Anja,

Could you send the link to this document?

I tried to checked out the BPM-sources in old and in new version NWDS but get the same error in both cases.

[ch_loos]

Hi Anja,

You're right - the note is not yet published for some reason.

I've asked the colleagues to look into this.

Basically, the reason for the error is that in the newer version has more strict validations on the process model.

If there are boundary events with no activities attached, the build will fail now whereas it worked fine with the older version.

If you can't or don't want to change the process model(s) manually you can create a OSS message and ask SAP support how to fix the problem with a script.

Regards,

Christian

[Former Member]

Christian,

Could you explain how I can identify boundary events with no activities attached. I use boundary event only at one activity in one my process in BPM-DC. I tried to delete boundary event, then I deleted activity, after that I deleted the process from DC. In each cases I got the build error:

Build stopped due to an error: java.lang.NullPointerException: while trying to invoke the method com.sap.glx.ide.model.galaxy.workflow.Activity.getScope() of a null object returned from com.sap.glx.ide.model.galaxy.workflow.BoundaryEvent.getActivity()

Last week I created OSS message and sent to SAP Support my problem DC. Now I'm waitng recomendation or solution from SAP Support.

Regards,

Alexander

[ch_loos]

Hi Alexander,

we can only provide product support via the official OSS channel.

Please send me your OSS ticket number by direct message and I'll make sure it gets routed to the right people.

There could also be another reason for this error so support needs to take a look at it.

Thanks for your understanding.

Christian

[Former Member]

Thank you very much!

Unfortunately I can only send Direct Messages to Friends / Connections (people following me).

My ticket number is "BPM build failed after update ( 644640 / 2014 )"

Best regards,

Alexander

[Former Member]

Hi,

I have the same issue and one of my DC (bpm) doesn't build ufter update SAP EP 7.3SP07 to 7.3SP11.

In CBS UI I see more detailed log, main cause is:

Caused by:

java.lang.NullPointerException: while trying to invoke the method com.sap.glx.ide.model.galaxy.workflow.Activity.getScope() of a null object returned from com.sap.glx.ide.model.galaxy.workflow.BoundaryEvent.getActivity()

I try to delete boundary event on activity, delete activity, delete process, delete all processes in my bpm DC and still got this error.

Do anyone solve this problem?

Thanks and best regards,

Alexander

[Former Member]

Hi,

I encounter the same error message during building BPM-DC after updating the SCs in NWDI from 7.2SP03 to 7.2SP09. Did you find a solution and can you please describe how to solve this issue? I experienced same as you: I deleted all processes and still got the error, so it's not related to process model mapping.

Thanks.

Regards,

Anja

[Former Member]

Hi,

Do you solve this problem?

[Former Member]

Hi Javier,

Did it got resolved? Is yes how?

Thanks

Manish