You try to start the WebSphere Message Broker Toolkit (version 7), but it never launches. The WebSphere Message Broker Toolkit has been installed correctly, and has previously started correctly.
The cursor might display as busy for several seconds.
The WebSphere Message Broker Toolkit startup splash screen is not displayed.
The workspace launcher window does not open.
The Java™ shared resources that are associated with the JVM of the WebSphere Message Broker Toolkit have become corrupted.
Diagnosing the problem
Javacore, heapdump, and snap trace files are located in your Toolkit Installation directory.
The javacore files show the failure as a "GPF" (General Protection Fault).
The snap trace files, when formatted, show that the failure is inside "j9shr" and that the following method never exits: "CM startup for cache".
Resolving the problem
To resolve this problem, complete the following steps:
- Back up your workspace resources to a safe location.
- Back up the following directory: C:\Documents and Settings\toolkit_admin_account\Local Settings\Application Data\javasharedresources\
- Remove the "sharedcc" and "IBMSDP" files from this directory. If there are several copies of these files, compare the file names with the cache names that are included in the snap trace.
- Restart your WebSphere Message Broker Toolkit.
It may take some time to restart the WebSphere Message Broker Toolkit, because Eclipse needs to re-initialize.
If you encounter any failures, restore the javasharedresources backup and contact IBM Support.
WMBT WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI