Resolving errors that occur when using the IBM Integration Toolkit

Use the advice given here to help you to resolve common problems that can occur when you use the IBM® Integration Toolkit.

About this task

IBM Integration Toolkit on RedHat 6.5 crashes with "JVM terminated. Exit code=160" error

Procedure

  • Scenario: When the IBM Integration Toolkit runs on Red Hat Linux® 6.5, and you click the Patterns Explorer view or you use the Tutorials Gallery, the IBM Integration Toolkit can crash with the following error:

    JVM terminated. Exit code=160

  • Explanation: Red Hat Linux 6.5 ships with WebKitGTK version webkitgtk.x86_64 1.2.6-5.el6, which can have problems with the Eclipse SWT browser.
  • Solution: To work around this problem, complete one of the following steps:
    • Upgrade Red Hat Enterprise Linux to 6.6 or later. Versions of Red Hat Enterprise Linux 6.6 and later ship with a version of WebKitGTK that does not exhibit the problem.
    • Update the IBM Integration Toolkit eclipse.ini file to use XULRunner instead of WebKitGTK for browser support by completing the following steps:
      1. Download XULRunner 10.0.4 ESR 64-bit from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/10.0.4esr/runtimes/xulrunner-10.0.4esr.en-US.linux-x86_64.tar.bz2.
      2. Expand the compressed file into a convenient directory. For example, /usr/lib/xulrunner_new.
      3. Add the following lines to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory:
        -Dorg.eclipse.swt.browser.XULRunnerPath=filepath/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
        For example:
        -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner_new/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
      4. Restart the IBM Integration Toolkit.

IBM Integration Toolkit on Linux becomes unresponsive after opening a DFDL or XSD file

Procedure

  • Scenario: When the IBM Integration Toolkit runs on Linux (for example, Red Hat Linux 7.x or 6.x) and you open a DFDL or XSD file in the DFDL editor or XML Schema Editor, the IBM Integration Toolkit can become unresponsive and might not shut down correctly. Killing the javaw process manually closes the IBM Integration Toolkit, and might result in a javacore file with the main thread in the following method: 
    org/eclipse/swt/internal/gtk/OS._gtk_enumerate_printers(Native Method)
  • Solution: This issue is caused by Eclipse Bug 153936 (Eclipse freezes when opening an editor). Complete one of the following steps to resolve the problem:
    • Add the following line to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory:
      -Dorg.eclipse.swt.internal.gtk.disablePrinting
    • Install the GTK2 32-bit drivers by running the following command from the command line: 
      sudo yum install gtk2.i686

Internal web browser in IBM Integration Toolkit does not work on Red Hat 7.1

Procedure

  • Scenario: When the IBM Integration Toolkit runs on Red Hat Linux 7.1 and you use any of the views that require an internal web browser, you might see one or more of the following error messages:
    • In the Pattern Specification editor:
      No internal web browser can be resolved. Pattern specifications is opened in default system web browser.
    • In the Tutorials Gallery view:
      No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
    • In the XML View tab in the DFDL Test - Logical Instance view:
      The default browser installed on your system is not compatible or environment variables need to be specified.
Consult the Welcome screen (Help and Welcome in the menu) for information about configuring your system.
  • Solution: To work around this problem, update the IBM Integration Toolkit eclipse.ini file to use XULRunner instead of WebKitGTK for browser support, by completing the following steps:
    1. Download XULRunner 10.0.4 ESR 64-bit from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/10.0.4esr/runtimes/xulrunner-10.0.4esr.en-US.linux-x86_64.tar.bz2
    2. Expand the compressed file into a convenient directory (such as /usr/lib/xulrunner_new).
    3. Add the following lines to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory: 
      -Dorg.eclipse.swt.browser.XULRunnerPath=<location of unzipped download file>/xulrunner 
-Dorg.eclipse.swt.browser.DefaultType=mozilla
      For example:
      -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner_new/xulrunner 
-Dorg.eclipse.swt.browser.DefaultType=mozilla
    4. Restart the IBM Integration Toolkit.
    5. If the IBM Integration Toolkit fails with an error saying JVM terminated. Exit code=160, run the following command before launching the toolkit in the same terminal window: 
      export LD_LIBRARY_PATH=<location of unzipped download file>/xulrunner:$LD_LIBRARY_PATH
      For example:
      export LD_LIBRARY_PATH=/usr/lib/xulrunner_new/xulrunner:$LD_LIBRARY_PATH

After you start the IBM Integration Toolkit, runtime functions do not work

Procedure

  • Scenario: After you start the IBM Integration Toolkit, runtime functions including tutorials, patterns, the Flow Exerciser, and integration node administration do not work correctly.
  • Explanation: This error occurs if you start the IBM Integration Toolkit by using one of the following commands to start Eclipse:
    • On Windows: eclipse.exe
    • On Linux: ./eclipse
  • Solution: Always start the IBM Integration Toolkit by using one of the following methods:
    • On Windows:
      • Use the Windows menu option.
      • From the IBM Integration Console, type iib toolkit.
    • On Linux:
      • From the command environment, type ./iib toolkit.

Errors occur while you are using the IBM Integration Toolkit

Procedure

  • Scenario: An error has occurred while you are using the IBM Integration Toolkit, and you want information to help you to diagnose the problem.
  • Solution: Some errors that occur in the IBM Integration Toolkit are logged in the .log file in your workspace\.metadata directory.
    You can view this log by switching to the Plug-in Development perspective, and clicking the Error Log tab in the lower-right pane. The log shows in which plug-in the error occurred, and gives further information.

    You can also use trace to try and determine the cause of your problem. See Using trace for more information about tracing.

An error message is displayed when you start the Flow Exerciser

Procedure

  • Scenario: Either your IBM Integration Toolkit is Version 10.0.0.1 (or later) and your integration node is Version 10.0.0.0, or your IBM Integration Toolkit is Version 10.0.0.0 and your integration node is Version 10.0.0.1 (or later). You open a message flow in the message flow editor and start the Flow Exerciser. The flow deploys correctly, but the progress window displays a failure message. The error contains the following text: 
    BIP2210E: Invalid configuration message: attribute name 'testRecordMode' not valid for target object 'object_name'
  • Solution: If the IBM Integration Toolkit is Version 10.0.0.0, you can use the Flow Exerciser only with an integration node that is Version 10.0.0.0. If the IBM Integration Toolkit is Version 10.0.0.1 (or later), you can use the Flow Exerciser only with an integration node that is Version 10.0.0.1 (or later).
    To check the version of an integration node within the IBM Integration Toolkit, click on the integration node in the Integration Nodes view, and then look in the Properties view.

    For more information about installing fix packs and upgrading integration nodes to use the fix pack code, see Applying service to IBM Integration Bus.

Windows platform

The plug-in repository cannot be found when you are installing a plug-in into the IBM Integration Toolkit

Procedure

  • Scenario: You are installing a plug-in into the IBM Integration Toolkit and an error message is issued stating that no repository that contains the plug-in can be found.
  • Solution: Ensure that you start the IBM Integration Toolkit by right clicking it in the Start menu and selecting Run as administrator.
Windows platform

MSVCP120.dll missing message is issued

Procedure

  • Scenario: You are using the IBM Integration Toolkit and a pop-up window is seen that states mqsisetsecurity.exe has stopped working. Clicking the details in the pop-up window shows that the MSVCP120.dll file is missing.
  • Solution: Download and install the Microsoft Visual C++ 2010 Redistributable Package.

An error is issued when you access the help system

Procedure

  • Scenario: You are accessing the help system through the IBM Integration Toolkit, and an error message is issued stating that the Web page that you requested is not available offline.
  • Explanation: This error might occur if you previously had a connection to a Web-based version of the help system and lost it, or if you have Work Offline selected in your Internet Explorer options.
  • Solution: Click Connect to load the help system.

The IBM Integration Toolkit displays an error message after the error has been fixed

Procedure

  • Scenario: The IBM Integration Toolkit is in an inconsistent state, or displays an error message after the error has been fixed
  • Solution: Clean the workspace:
    1. From the IBM Integration Toolkit, click Project > Clean.
    2. Click Clean all projects and Finish.

      This action cleans the whole workspace of any internal files, which are then re-created so that none of your data is lost.

The message Unable to create part: filename.extension is issued

Procedure

  • Scenario: You open an editor in the IBM Integration Toolkit, and an error message is raised stating that a file cannot be created.
    This problem is caused by one of following situations:
  • Explanation 1: The given file is not associated with a recognized editor.
    • Solution 1: Right-click the file and choose the default editor to open it, or choose another editor if the default editor cannot open it.
  • Explanation 2: The given file contains syntax errors and cannot be loaded into the chosen editor. However, if you then try to open a valid file, you get the same error message repeatedly.
    • Solution 2: Restart the IBM Integration Toolkit; do not load the file into an editor again until you have fixed the syntax errors.