IBM Integration Bus, Version 10.0.0.0 Operating Systems:
AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
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.
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 Toolkiteclipse.ini file to use XULRunner instead of
WebKitGTK for browser support by completing the following steps:
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 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:
From the IBM Integration Toolkit, click Project > Clean.
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.