Need help/advice/info on displaying progress msg in multithreaded MIDP

Question

So I have this kind of MIDlet:
1. Using multi-threading feature to access remote web service/JAX-WS. The threads retrieve strings from GlassFish, connected to a MS SQL Server 2008 database.
2. The retrieved strings are to be stored within the MIDlet's RMS. Done perfectly until this phase.
3. The buggy thing is, WHILE the retrieving threads are alive/running and storing strings to RMS, I want to display some progress messages/bars to a Form by StringItem/TextField.
So I thought- it may be caused by the thread deadlocks, but it's not. WITHOUT the RMS storing strings, it flows OK.
(Because the progress msg alteration to the Form is done (I think) by my created threads, thus no deadlock occured.)
But WITH the RMS operating, it freezes on the "Confirmation/Yes-No" Form right before I press the Yes button.
Only when the whole threads are finished/terminated, it's then jumped to "Process Completed" Form.
(I get the feeling it jumped to each progress msg by miliseconds RIGHT AFTER all threads are finished, then to "Process Completed"
which is something I don't want to happen)
So I'm wondering how to get around this prob? Whose thread is it that operating the RMS?
Thanks.

Answer 1

hi, i have an application which takes pretty long to
run. The process basically consists of several sql
statements. My idea was to display a message box just
before the process starts saying something like "in
progress... please wait". Anyway i created a message
box using jdialog but the problem now is, it just
displays and empty box, the message is displayed only
when the process has finished running which is
useless. if i use the msg box elsewhere, it runs just
fine, only when it is placed before a block of long
running code (e.g a very big loop) it just does not
display the text.
Can anyone please advise me on this issue, thanks!If you don't want to get into threads and things like that, try the following?
1. Add some delay between the message box request and start of the query.
Like
for (int i = 0; i < 100000; i++) {} // you have to experiment with the limit. A second's worth should be enough to see if this makes any difference.
2 Add the method repaint(); after the message request.
3 Add the method repaint(); and delay after the message request but before the query request.
LIke
// message display request
repaint();
for (int i = 0; i < 100000; i++) {}
// query
What's interesting to me is that an empty box is drawn. So my guess is if enough time (a second say) is given, the message box will be drawn completely. (Of course, I'm not sure.)