Microsoft Dynamics Ax developer's blog

Monday, November 06, 2006

Sidax 0.3.7 beta 11

download (35k)

  • It can handle a project renaming correctly now

  • Pause button at 'about' tab: you can stop the background processes so sidax doesn't affect profiler



PS: Axaptapedia is online again

11 comments:

Torben said...

Hi,

I have been trying out the 0.3.7 betas (10 and 11) these days and I'm experiencing strange freezes: When I shut down either full Axapta or just the Sidax Sidbar, Axapta freezes (I haven't tried letting it stay longer then 5 minutes yet though). I have to kill it then.

Funnily, as soon as I enable the Client-/Server- or Method-Trace options to see where it actually happens, everything suddenly runs fine.

The same happens if I enable the Debugger in Sidax::close(), then again Axapta/Sidax exits like I'm used to it.

Downgrading to 0.3.6 also solves the problem.

Any ideas at this point?

Max Belugin said...

I think, the problem is in the following: since beta 9 Sidax caches MainMenu for faster loading so in the SysLastValue - so it become too large.

I suppose Axapta doesn't wait until it is saved and quits and this cause a problem.

try beta 12 with possible fix
(cache is saved only once)

URL: http://erpkb.com/Axapta/Sidax/files?get=sidax0.3.7beta12.zip

Torben said...

Hi Max,

unfortunalety, this doesn't help me. I have waited until Sidax shows the full main menu, then tried to close the Sidax form. At that point axapta again freezes. Ctrl-Break doesn't show any reaction and the progress indicator in the bottom right of Axapta shows [computer] <= [server] (I'm working 3-Tier here).

On another note: If you are saving the Cache only once, how can I invalidate it.

What about making this caching optional?


Oh, before I forget it: Apart from this little problem here Sidax is a great tool.


Greetings,
Torben

Torben said...

Hi again,

one more thing: Even though Axapta freezes, the caching itself seems to work, after restarting Axapta I seem to have the full menu instantly.

Greetings,
Torben

Max Belugin said...

Can you reproduce this once again (sidax doesn't save now MainMenu cache unless you press refresh button explicitly, so when you load first time and immediately close sidax - you reproduce the situation in b11, but when you load sidax one again Main Menu is cached already and isn't saved at all)

Torben Nehmer said...

Hi Max,

unfortunalety, B12 doesn't get on track itself, here is what I tried:

1. Close old Sidax
2. Import new Sidax
3. Open new Sidax
4. After menu is loaded, close new sidax form - works.
5. Reopen Sidax
6. Close Axapta with opened Sidax - freezes
7. Kill Axapta
8. Reopen Axapta with auto-load of new Sidax
9. Close Axapta again - Axapta freezes

I have let Axapta "freeze" for 20 minutes with now reaction during that time. Axapat uses up all available CPU resources (of one core, to be precise) and the busy indicator in the bottom right is like "[local] <= [server]". All running in 3-Tier mode.

Any ideas?

Max Belugin said...

May be loading cause this problem. So try not to close ax immediately, but work for some time.

I have reproduced your probblem, but if I close ax after some time of work it works fine.

I think the case when you open Ax and immediately close it is not very often.

If it still hangs i will try to keep cache localy on user machine

Torben said...

Hi Max,

I can confirm this behavoir, where "some time" seems to be "several minutes".

I agree that having an Axapta client active for just a minute or so is not the usual case. However, it is not that rare either. Sometimes due to human error (clicked the wrong symbol starting up Axapta in USR instead of CUS layer) or in other times when testing new Plugins or other stuff loading at client startup. With the human-error-factor being much more prevalent.

Would it be an idea to add some simple visual feedback to Sidax while this loading sequence is in progress, perhaps together with an abort button? That would give you at least a way out in cases where you remeber to do so.

Greetings from Germany,
Torben

Max Belugin said...

sorry, i have no information about what axapta is doing. The only way to workaround i see is storing main menu cache in some other place - for example in file system (i can add an option to store in a local folder)

Torben said...

Hi again,

I have run a few tests, and in generally, Sidax runs better now.

Unfortunalety, as long as I have the new Sidax active, Axapta seems to freez occasionally just like it did originally on shutdown.

I am not 100% certain that this is related to Sidax as these freezes are very random in nature. They just *seem* to be related to some heavy load, but this is just a guess.

What makes me suspect Sidax is resposible is the fact that I never had such freezes before. With 0.3.6 I didn't have one for 2 development days now, where with 0.3.7 beta I had three freezes on a single day.

Any ideas?

Greetings,
Torben

Max Belugin said...

try beta 1