WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Resolving error messages that occur when using the WebSphere Message Broker Toolkit

Use the advice given here to help you to resolve common problems that can occur when you use the WebSphere® Message Broker Toolkit.

Errors occur while you are using the WebSphere Message Broker Toolkit

  • Scenario: An error has occurred while you are using the WebSphere Message Broker Toolkit, and you want information to help you to diagnose the problem.
  • Solution: Some errors that occur in the WebSphere Message Broker 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

  • Scenario: You are accessing the help system through the WebSphere Message Broker 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 WebSphere Message Broker Toolkit displays an error message after the error has been fixed

  • Scenario: The WebSphere Message Broker Toolkit is in an inconsistent state, or displays an error message after the error has been fixed
  • Solution: Clean the workspace:
    1. From the WebSphere Message Broker 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

  • Scenario: You open an editor in the WebSphere Message Broker 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 WebSphere Message Broker Toolkit; do not load the file into an editor again until you have fixed the syntax errors.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:39


Task topicTask topic | Version 8.0.0.7 | au16602_