| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to open MB Toolkit 6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| pdmenon |
 Posted: Sun Jan 09, 2011 11:56 pm Post subject: Unable to open MB Toolkit 6.1 |
 |
|
Voyager
Joined: 05 Apr 2010
Posts: 80
|
Today, I installed MB runtime and toolkit 6.1.
MB Runtime working fine, able to configure Configmgr, broker
But, I am unable to open MB Toolkit.
It pops out error like:
"JVM Terminated.Exit code=1"
How can I attach the error picture, which I am getting. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Mon Jan 10, 2011 12:09 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
google has many hits for that.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| pdmenon |
| Posted: Mon Jan 10, 2011 2:22 am Post subject: |
|
|
Voyager
Joined: 05 Apr 2010
Posts: 80
|
Dear Experts,
I just renamed "eclipse.exe" to "eclipse1.exe".
It just started working. May I know, what may be the reason for this sort of behaviour.
Thanks for your valuable time.  |
|
| Back to top |
|
|
| cresida |
| Posted: Mon Jan 10, 2011 2:23 am Post subject: |
|
|
Newbie
Joined: 02 Feb 2009
Posts: 7
|
* Defect 49194 Toolkit fails to start
When you try to start the toolkit a "JVM terminated Exit Code = 1" error is displayed, or the javaw.exe process takes 100% of the CPU and stops.
The problem might be due to the -Xshareclasses:singleJVM, keep switch in the eclipse.ini file. This switch creates a cache that provides a means of sharing all loaded classes, and places no restrictions on the JVMs that are sharing the class data. If the cache becomes corrupted, no new JVMs are allowed to connect to the cache. Existing JVMs can continue to function, but cannot update the cache.
Solution:
To resolve the problem, delete the corrupted cache. The cache is rebuilt the next time the product is launched. To delete the cache:
1. Open a command prompt.
2. Navigate to Message Broker Toolkit Directory/jdk/jre/bin.
3. Enter the following command:
On Microsoft Windows:
javaw.exe -Xshareclasses:destroy
On Linux:
./javaw -Xshareclasses:destroy
The product now starts successfully. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Jan 10, 2011 3:46 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
I just renamed "eclipse.exe" to "eclipse1.exe".
It just started working. May I know, what may be the reason for this sort of behaviour. |
why have you done that? why dont you ask the source of information of that rename why? or do you just rename executables on a random base if things are not working? 
i assume your java / eclispe environment is screwed up due to multiple installations with different versions and bad path settings. but thats just a guess.
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
