ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » [Solved] Mset file not displaying any properties

Post new topic  Reply to topic
 [Solved] Mset file not displaying any properties « View previous topic :: View next topic » 
Author Message
elvis_gn
PostPosted: Thu Jan 18, 2007 1:31 am    Post subject: [Solved] Mset file not displaying any properties Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi all,

Has anyone faced an issue that when you create the message set (mset) file, there are no properties or details displayed...the whole page is blank..

I thought the issue was the version and went ahead and updated the toolkit to whatever fixpacks are available as of date..current version shows 6.0.2.

The problem is there for perfectly working message sets imported, or ones created in the toolkit...

Any ideas ?

Regards.


Last edited by elvis_gn on Thu Jan 18, 2007 3:20 am; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Thu Jan 18, 2007 2:28 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Yes, I've seen it too.

I don't have an explanation or a fix - it only occurred in one machine for someone who didn't really need it fixed. My suspicion has been that it's an improperly installed toolkit.

Try the usual tricks with eclipse - start up with -clean, delete .metadata or create a new workspace (don't forget project interchange for exporting and importing all your projects).

Try increasing the java heap to the Toolkit.

If that doesn't work... try re-installing.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Thu Jan 18, 2007 3:19 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi Jeff,

Creating a new workspace worked, though I did not like the solution

Thanks.

Regards.
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Thu Jan 18, 2007 5:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

elvis_gn wrote:
Creating a new workspace worked, though I did not like the solution


Project Interchange Format is very good for just this situation. Export everything in your workspace into a PIF zip file. Delete .metadata. Restart the toolkit pointing at the same workspace - no projects. Import the PIF - all your projects are back and happy.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
special_agent_Queue
PostPosted: Thu Jan 18, 2007 6:42 am    Post subject: Reply with quote

Centurion

Joined: 27 Jul 2006
Posts: 102

I believe we are having the same problem. When opening the mset file, it shows up with empty areas. (All I see is a box for hierarchy and to the right of that a section for details, but nothing else shows). However, the message sets do work fine.

I tried creating a new workspace. I also tried that PIF tip. Neither worked. Any other suggestions?

Thanks.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jan 18, 2007 6:45 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

start up with -clean.

add more memory to the Java heap.

Reinstall the Toolkit...

Open a PMR...
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
pathipati
PostPosted: Thu Jan 18, 2007 6:46 am    Post subject: Reply with quote

Master

Joined: 03 Mar 2006
Posts: 296

I saw this problem too, but for me switching the perspectives or just restarting the Toolkit fixed the problem. It happened many times for me.
I guess this happens if our workspace goes very bigger..
Quote:
Any other suggestions?

Try this, close all your perspectives and then reopen the perspectives..
Back to top
View user's profile Send private message Yahoo Messenger
jefflowrey
PostPosted: Thu Jan 18, 2007 6:48 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

pathipati wrote:
I guess this happens if our workspace goes very bigger..


Add more memory to the Java heap...

-Xmx nnnnM -Xms ppppM , where nnnn > pppp > 256
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
pathipati
PostPosted: Thu Jan 18, 2007 6:59 am    Post subject: Reply with quote

Master

Joined: 03 Mar 2006
Posts: 296

Yes, I tried following settings in wmbt.ini/wid.ini files to reduce the restarting of my WMB & WID Toolkits number of times, which is working fine. But this didn't fixed message set problem.

Quote:
; Contract the heap if free space exceeds 30% (40% may be a better choice). Default was 60%.
VMArgs=-Xmaxf0.3
; Expand the heap if a garbage collection leaves less than 20% free. Default was 30%.
VMArgs=-Xminf0.2
; Set minimum heap to 512mb to reduce GCs (may be too high, depending on other processes running). Default was 128mb.
VMArgs=-Xms512m
; Enable part of GC to run concurrently, instead of locking up the process.
VMArgs=-Xgcpolicy:optavgpause
Back to top
View user's profile Send private message Yahoo Messenger
elvis_gn
PostPosted: Thu Jan 18, 2007 7:27 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi all,

There is a saying in my native language "Vellakan peratiye paand aayi" which would mean something like "I applied a faireness cream and ended up getting a blotch"...

I got the mset problem fixed, and tried importing back all my clearcase projects...and now I find that the fix pack adds new lines into the .project files, which is un-acceptable as the rest of the developers and the servers are still on the earlier version of the broker...

So I tried to revert back on the fixpack, and thats not possible now...So end of story, I need to reinstall the toolkit...

Regards.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » [Solved] Mset file not displaying any properties
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.