logicmail-devel

[Logicmail-devel] lockup issue with 1.9.0 builds

[Chris S. <cl...@se...>]

Has anyone else managed to get 1.9.0 to lock up their BB hard?  I was
giving it a test run last week to see if the new APIs would allow me to
get passed my MS Exchange SSL/TLS problem.

The first problem I saw was that LogicMail refused to get a list of
folders from my personal Courier-Imap server.  I suspect that the
problem has to do with either the number of folders (100+) or that the
names of some folders are longer than the token 8 or 15 chars.  I run
the same version of Courier-Imap at work with just a dozen folders and
LogicMail had no problem getting a directory listing for that one.

When attempting to send mail via the Exchange server, I received the
exception message:
  Unable to switch to TLS mode: (null)
I'm not sure which condition in Connection.java startTLS() that I'm hitting.

At some point, I tried repeatedly to connect to my personal imap server
and send via Exchange/SSL and then the BlackBerry locked up.  I had to
pull the battery to reset it.  Now, whenever I try to start up LogicMail
1.9.0 (any build from the past week), it appears to return to the same
spot.  Occasionally, it will throw up a dialog box:

    Uncaught exception: Module with handle [1823]
    and index [0] has no application entry point
            [OK]

I've tried downgrading to 1.1.x, which works. But after re-upgrading to
1.9.0, the broken behavior persists.

I purchased the signing keys and was able to build my own trunk version,
sign it and install it but it behaves the same way.  I tried renaming
the local build to LogicMail-1.9 via the project.properties file and the
problem still persists.

I used 'JavaLoader erase' to forcibly remove the bad modules from the
device but when I load 1.9.0 again, it pops up the same dialog box with
a different handle number.

- cls

Re: [Logicmail-devel] lockup issue with 1.9.0 builds

[Derek K. <dko...@lo...>]

You're definitely a braver guy than me.  I'm still running a 1.1 build on my 
own phone. :-)

The TLS support is pretty new, though it is also fairly simple.  However, what 
you really should be doing is testing this all on the simulator.  If you have 
a development environment setup in Eclipse, and run LogicMail that way, you 
can at least see what sort of lockup is actually happening.  You're obviously 
testing a case I've never run into, which means I probably can't debug it on 
my own.

The trunk (1.9/2.0) version has a lot of threading and asynchronous stuff under 
the covers, so there's definitely a chance you either triggered a deadlock or 
(maybe) an infinite loop.  Most of my own testing so far has been far more 
"scripted" than a real user on a real device.  (i.e. I don't navigate screens 
while stuff is loading, or trigger loading different things at once)  So any 
debugging help you can offer is greating appreciated.

As far as entry point issues, that could be something getting corrupted in the 
build process, but I can't say.  I had those sorts of issues a lot when I was 
first getthing things ironed out, but haven't seen them in a while.  But there 
are two tidbits you should know about this:
- LogicMail (devel) has two "entry points", one that runs at BlackBerry 
startup to initialize device notifications, and the one that runs when you 
actully click the icon to start the app.
- The way Eclipse builds the app is *different* from the way "ant" builds the 
app.  Any entry-point settings or startup issues may be unique to the way you 
were building the app.  These problematic builds...  were they done in Eclipse 
(/w plugin), the RIM JDE, or straight Ant?

-Derek

On Tuesday 01 September 2009 3:20:29 am Chris Seawood wrote:
> Has anyone else managed to get 1.9.0 to lock up their BB hard?  I was
> giving it a test run last week to see if the new APIs would allow me to
> get passed my MS Exchange SSL/TLS problem.
>
> The first problem I saw was that LogicMail refused to get a list of
> folders from my personal Courier-Imap server.  I suspect that the
> problem has to do with either the number of folders (100+) or that the
> names of some folders are longer than the token 8 or 15 chars.  I run
> the same version of Courier-Imap at work with just a dozen folders and
> LogicMail had no problem getting a directory listing for that one.
>
> When attempting to send mail via the Exchange server, I received the
> exception message:
>   Unable to switch to TLS mode: (null)
> I'm not sure which condition in Connection.java startTLS() that I'm
> hitting.
>
> At some point, I tried repeatedly to connect to my personal imap server
> and send via Exchange/SSL and then the BlackBerry locked up.  I had to
> pull the battery to reset it.  Now, whenever I try to start up LogicMail
> 1.9.0 (any build from the past week), it appears to return to the same
> spot.  Occasionally, it will throw up a dialog box:
>
>     Uncaught exception: Module with handle [1823]
>     and index [0] has no application entry point
>             [OK]
>
> I've tried downgrading to 1.1.x, which works. But after re-upgrading to
> 1.9.0, the broken behavior persists.
>
> I purchased the signing keys and was able to build my own trunk version,
> sign it and install it but it behaves the same way.  I tried renaming
> the local build to LogicMail-1.9 via the project.properties file and the
> problem still persists.
>
> I used 'JavaLoader erase' to forcibly remove the bad modules from the
> device but when I load 1.9.0 again, it pops up the same dialog box with
> a different handle number.
>
> - cls
>
> ---------------------------------------------------------------------------
>--- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day trial. Simplify your report design, integration and deployment - and
> focus on what you do best, core application coding. Discover what's new
> with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Logicmail-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logicmail-devel

-- 
---------------------------
Derek Konigsberg
dko...@lo...
---------------------------

Re: [Logicmail-devel] lockup issue with 1.9.0 builds

[Chris S. <cl...@se...>]

Yeah, I'm a firm believer in eating your own dogfood.  Plus, everyone
was raving about 1.9.0 in a previous thread and there were binary builds
so I had to try it out. :-)

The first 1.9.0 build was your binary build from last week (8/26?).  My
local builds are done using ant.

I just ran my local build in the simulator and it crashes with the
unhandled exception error when LogicMail attempts to get my folder list.

I can't figure out how to copy the stack trace but essentially, it looks
something fails when ImapProtocol::executeList tries to update the
status of the MailProgressHandler.  When I commented out all of those
calls, then the app stopped crashing at that point.

- cls

Derek Konigsberg said the following on 9/1/2009 3:16 AM:
> You're definitely a braver guy than me.  I'm still running a 1.1 build on my 
> own phone. :-)
> 
> The TLS support is pretty new, though it is also fairly simple.  However, what 
> you really should be doing is testing this all on the simulator.  If you have 
> a development environment setup in Eclipse, and run LogicMail that way, you 
> can at least see what sort of lockup is actually happening.  You're obviously 
> testing a case I've never run into, which means I probably can't debug it on 
> my own.
> 
> The trunk (1.9/2.0) version has a lot of threading and asynchronous stuff under 
> the covers, so there's definitely a chance you either triggered a deadlock or 
> (maybe) an infinite loop.  Most of my own testing so far has been far more 
> "scripted" than a real user on a real device.  (i.e. I don't navigate screens 
> while stuff is loading, or trigger loading different things at once)  So any 
> debugging help you can offer is greating appreciated.
> 
> As far as entry point issues, that could be something getting corrupted in the 
> build process, but I can't say.  I had those sorts of issues a lot when I was 
> first getthing things ironed out, but haven't seen them in a while.  But there 
> are two tidbits you should know about this:
> - LogicMail (devel) has two "entry points", one that runs at BlackBerry 
> startup to initialize device notifications, and the one that runs when you 
> actully click the icon to start the app.
> - The way Eclipse builds the app is *different* from the way "ant" builds the 
> app.  Any entry-point settings or startup issues may be unique to the way you 
> were building the app.  These problematic builds...  were they done in Eclipse 
> (/w plugin), the RIM JDE, or straight Ant?
> 
> -Derek
> 
> On Tuesday 01 September 2009 3:20:29 am Chris Seawood wrote:
>> Has anyone else managed to get 1.9.0 to lock up their BB hard?  I was
>> giving it a test run last week to see if the new APIs would allow me to
>> get passed my MS Exchange SSL/TLS problem.
>>
>> The first problem I saw was that LogicMail refused to get a list of
>> folders from my personal Courier-Imap server.  I suspect that the
>> problem has to do with either the number of folders (100+) or that the
>> names of some folders are longer than the token 8 or 15 chars.  I run
>> the same version of Courier-Imap at work with just a dozen folders and
>> LogicMail had no problem getting a directory listing for that one.
>>
>> When attempting to send mail via the Exchange server, I received the
>> exception message:
>>   Unable to switch to TLS mode: (null)
>> I'm not sure which condition in Connection.java startTLS() that I'm
>> hitting.
>>
>> At some point, I tried repeatedly to connect to my personal imap server
>> and send via Exchange/SSL and then the BlackBerry locked up.  I had to
>> pull the battery to reset it.  Now, whenever I try to start up LogicMail
>> 1.9.0 (any build from the past week), it appears to return to the same
>> spot.  Occasionally, it will throw up a dialog box:
>>
>>     Uncaught exception: Module with handle [1823]
>>     and index [0] has no application entry point
>>             [OK]
>>
>> I've tried downgrading to 1.1.x, which works. But after re-upgrading to
>> 1.9.0, the broken behavior persists.
>>
>> I purchased the signing keys and was able to build my own trunk version,
>> sign it and install it but it behaves the same way.  I tried renaming
>> the local build to LogicMail-1.9 via the project.properties file and the
>> problem still persists.
>>
>> I used 'JavaLoader erase' to forcibly remove the bad modules from the
>> device but when I load 1.9.0 again, it pops up the same dialog box with
>> a different handle number.
>>
>> - cls
>>
>> ---------------------------------------------------------------------------
>> --- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day trial. Simplify your report design, integration and deployment - and
>> focus on what you do best, core application coding. Discover what's new
>> with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Logicmail-devel mailing list
>> Log...@li...
>> https://lists.sourceforge.net/lists/listinfo/logicmail-devel
> 

Re: [Logicmail-devel] lockup issue with 1.9.0 builds

[Derek K. <dko...@lo...>]

Ahh, the joys of you being on the west coast (and me on the east coast), 
and us both doing most of this after work...  Puts a day lag between us 
:-)  Though it reminds me of when I spent a summer durring college in San 
Diego, and was delighted that I could still chat /w my night-owl 
east-coast friends and still get to bed at a reasonable hour.

On Tue, 1 Sep 2009, Chris Seawood wrote:
> Yeah, I'm a firm believer in eating your own dogfood.  Plus, everyone
> was raving about 1.9.0 in a previous thread and there were binary builds
> so I had to try it out. :-)

I'm very close to that point myself with trunk (1.9).  My main hesitation 
had to do with the fact that I haven't put much effort yet into ironing 
out all the error conditions that can arise from a flaky network, which is 
a mostly non-existant problem at home.  I do periodically load the lastest 
build onto my older 8820 and test it over Wi-Fi, however.  Though right 
now I'm discovering some random/minor UI quirks as a side-effect of my 
attempt to support Storm and conventional UIs from the same source tree. 
Hopefully those will be ironed out soon enough, and there aren't many of 
them.  (I just wish it was less annoying to switch back and forth in the 
dev tools.)

> The first 1.9.0 build was your binary build from last week (8/26?).  My
> local builds are done using ant.
The build server (obviously) uses ant as well, so they should match up 
fairly well.  Though anything's possible.  Mixing and matching Eclipse and 
Ant builds on a real device could very well cause entry-point issues, 
however.

> I just ran my local build in the simulator and it crashes with the
> unhandled exception error when LogicMail attempts to get my folder list.
>
> I can't figure out how to copy the stack trace but essentially, it looks
> something fails when ImapProtocol::executeList tries to update the
> status of the MailProgressHandler.  When I commented out all of those
> calls, then the app stopped crashing at that point.

The inability to get your usual Java-style stack trace has to be my #1 pet 
peeve in the world of BlackBerry software development.  Especially, of 
course, when the "user" isn't willing/able to run the app in the simulator 
from a development IDE.

That being said, the code you're hitting is fairly recent.  My wild guess 
would be that I'm incorrectly calculating something in regards to progress 
reporting, or you're hitting some strange condition when it tries updating 
the status bar in the GUI.  I actually did some work this past weekend on 
how the status bar gets displayed, so I'd make sure you have that before 
moving forward.  Once you're past that point, some more direct debugging 
would be extremely helpful.  The Eclipse debugger makes it fairly easy to 
see what line of code the exception was thrown from, usually, though not 
necessarily what on the line caused the error.  So it never hurts to set a 
breakpoint right before it and step through.

I'll have to test some of that later myself, of course.  The output of the 
folder listing is one of those items that gets cached, so I'm probably not 
re-running that code very often.

P.S. I recently realized that if I keep focusing 100% on nitpick issues 
(of which I'm aware of plenty, and have been keeping a to-do list) then 
I'm never going to make real progress, so I'm currently focusing on 
the infrastructure code for offline message caching.  (that and connection 
management being the two key big-ticket items necessary for release...)
Someday I'll figure out a way of making my TO-DO list more visible, since 
its a more convenient way to work right now than Trac tickets.  (maybe if 
Tomboy Notes ever stabilizes their web service project)

-- 
----------------------------
  Derek Konigsberg
  dko...@lo...
----------------------------