book
Article ID: KB0091907
calendar_today
Updated On:
Description
Resolution:
When using invokeGCC to run native services, note the following:
a) If a native service is deployed as default resource, a random cpp bridge is used to load the service library. This behavior is similar to the Windows Engine.
b) If a native service is deployed as grid library, in addition to specifying the required bridge grid library as its dependency, all other bridges on the same platform must be excluded by adding them to the conflict list.
For example, in a linux Engine, service calculator requires gcc34 as the bridge, specify the following in the service grid-library.xml file:
<dependency os="linux">
<grid-library-name>cppbridge-linux-gcc34</grid-library-name>
</dependency>
<conflict os="linux">
<grid-library-name>cppbridge-linux-gcc3</grid-library-name>
</conflict>
This guarantees that cppbridge-linux-gcc34 is used when running this service.
If it's grid-library.xml change is not desired, you can deploy STL neutral invoke by copying invokeGCC over invokeGCC3 and invokeGCC34 in Engine update directory.
Issue/Introduction
Running STL Neutral Invoke Process on Linux/Linux64 (only)