| Author |
Message
|
| wbintegrator |
 Posted: Wed Dec 06, 2006 6:55 am Post subject: Cleaning/rebuiding messageflow project takes hours |
 |
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
HI all,
We'recently come across a very annoying issue: whenever cleaning a messageflow project , the rebuilding process takes hours! The project references two message set projects with about 10 MXSDs each.
Using MS Broker v6.0.0.2
Any ideas? is there any known issues with the number of flows in a message flow project or, similiarly, the number of mxsds in a message set project that might cuase such building delays?
Thanks  |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Dec 06, 2006 9:28 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| I'm interested. How big are your mxsd files? What message style are you modelling? |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Wed Dec 06, 2006 10:53 pm Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
The mxsds are up to 350 KB, XML format.
I forgot to mention that most of the time building, the process is stuck on esqls, saying: Building changed ESQ file: *.esql (* the name of the esql),
taking about 10-20 minutes for each.
I noticed that flows that reference mxsds only from mapping nodes are usually processed in seconds, while those that access mxsd fields from esql get stuck for MUCH longer. This could be because of the large number of mxsds in the refernced message set project, but I don't really know...
I hope someone will come up with something helpful.. |
|
| Back to top |
|
|
| Mercury |
| Posted: Wed Dec 06, 2006 11:40 pm Post subject: |
|
|
Apprentice
Joined: 24 Jun 2006
Posts: 32
Location: Hyderabad
|
Even I faced this kind of problem with MB6
Instead of using Build Automatically or Rebuild or Clean options
use Build Working Set option to build .This may reduce some build time |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 07, 2006 2:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
First thing, always make sure you have increased the JVM max heap for the Toolkit.
Secondly, what's the CPU usage when the toolkit is processing these ESQL files?
Thirdly - you are running the most recent FP of Toolkit, right?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Thu Dec 07, 2006 3:57 am Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
yes, we are running the toolkit with the most recent updates.
as for the heap and cpu.. The toolkit uses about all the memory available and the cpu over 95% when building.
It a pentium 4 with 1G memory, not so bad for any IDE I guess, though Broker toolkit is quite a moster  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 07, 2006 4:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you've got large message sets and messages, then 1G may not be sufficient to build them all in a single workspace.
Again, though, make sure that you have specifically modified the startup of the WMBT to increase the JVM max heap available to the Toolkit. It may save time to increase the min heap as well - although it will increase the startup time of the Toolkit.
Merecury's suggestion of creating Working Sets for different projects is a good one - it will help quite a bit in making sure that you're only building the things you absolutely need to.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| GRIFF |
| Posted: Mon Dec 11, 2006 11:04 am Post subject: |
|
|
Acolyte
Joined: 19 Sep 2005
Posts: 64
Location: VA
|
wbintegrator,
Just wanted to let you know you are not alone. Our shop has definitely noticed the same behavior and we have tried the usual items but have not found a solution as of yet. Please post anything that you find to be helpful with this issue and I will do the same.
Thanks,
GRIFF |
|
| Back to top |
|
|
|
|
