Integration installation and configuration error messages

You can refer to this information if an error occurs during installation, configuration, or start up.

Activation script fails

Example: The createOrderOnSuccess eventhandler factory setup throws an error.

Possible solutions are:

  • Refactor the factory default eventhandler with the existing eventhandler.
  • Run the activator script in override mode to use the eventhandler provided with the integration.

Java Null Pointer Exception

A Java Null Pointer Exception can occur when deploying the Sterling Configurator application EAR.

An error similar to the following is displayed:

<Error ErrorCode="java.lang.NullPointerException"
        ErrorDescription="java.lang.NullPointerException" ErrorRelatedMoreInfo="">
        <Attribute Name="ErrorCode" Value="java.lang.NullPointerException"/>
        <Attribute Name="ErrorDescription" Value="java.lang.NullPointerException"/>
        <Error ErrorCode="java.lang.NullPointerException"
            ErrorDescription="" ErrorRelatedMoreInfo="">
            <Stack>java.lang.NullPointerException
    at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:947)
    at com.sterlingcommerce.woodstock.util.frame.jdbc.SqlUtil.getProps(SqlUtil.java:1574)
    at com.yantra.yfc.util.YFCCommon.getDBTypeForPool(YFCCommon.java:435)
    at com.yantra.ycp.core.YCPConnHolder.&lt;init&gt;(YCPConnHolder.java:124)
    at com.yantra.ycp.core.YCPMultiConnHolder.getConnHolder(YCPMultiConnHolder.java:162)

When deploying the EAR to the application server, there are no memory parameters that are specified.

By default, the limit of 512mb is insufficient.

To resolve this issue, add values for min/max memory values within the Order Management WebSphere Application Server server.xml configuration file. This will allow the EAR to expand successfully during a restart.

A value of 4096mb is recommended.

Authentication failure

An authentication failure can occur when creating the QueueConnectionFactory AGENT_QCF.

An error similar to the following is displayed:

Please check if the supplied username and password are correct on the QueueManager to which you are connecting.

To resolve this issue, add the /opt/IBM/WebSphere/AppServer/lib library path within your WebSphere MQ JMS providers.

The path to this configuration within your Order Management WebSphere Application Server Administration Console settings is Resource > JMS > JMS Provider > WebSphere MQ messaging provider.

Then, place the additional library path within Native library path.

Java Initializer Exception

A Java Initializer Exception can occur when invoking the create_order service.

An error similar to the following is displayed:

java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at com.sterlingcommerce.woodstock.noapp.NoAppLoader.main(NoAppLoader.java:89)
Caused by: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.ensureError(J9VMInternals.java:147)

This issue is caused by the version of Java that is being used.

This version of Java ignores the class path being passed within the startIntegrationServer.sh command script.

To resolve this issue, ensure that the following paths are added to your Java class path:
/opt/IBM/WebSphere/AppServer/runtimes/*:/opt/IBM/WebSphere/AppServer/plugins/*:/opt/mqm/java/lib/*:/home/wasuser/IBM1/jar/guava/17_0/*

Once added, these commands will complete successfully.

Class Not Found Exception

An error similar to the following is displayed:

at com.yantra.omp.api.YFSApiImpl.createOrder(YFSApiImpl.java:658)
... 61 more
Caused by: java.lang.ClassNotFoundException: com.google.common.util.concurrent.internal.InternalFutureFailureAccess
at java.net.URLClassLoader.findClass(URLClassLoader.java:610)
at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:944)

This error can occur when the guava libraries are not found.

Resolve this issue by adding the guava libraries to your Java path, or directly to the startIntegration.sh script.

If you have already included the guava jar path and are still getting this error, then update the version of the guava libraries on your system.

WebSphere Commerce does not connect with IBM MQ

This error can occur when attempting to integrate later versions of WebSphere Commerce and WebSphere Application Server with Sterling Order Management.

This issue was observed with WebSphere Commerce 8.0.4.26 with WebSphere Application Server 8.5.5.18.

To resolve this issue, you can use an older version of WebSphere Commerce (such as 8.0.4.22) and WebSphere Application Server (such as 8.5.5.9).

You can then upgrade to the latest versions once the integration is successful.