Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Regular Contributor
Posts: 59
Registered: ‎05-10-2012
My Device: 8800
My Carrier: verizon

app becomes unresponsive, many errors in log, need help understanding them

Hello all

Here's my situation. I have developed and tested an app. Its compiled with JRE5.0.0 and one of the devices I used to test it was a Curve 8350 running os v5.0.0.973

It runs fine on that device.

The app consists of the deliverables from 2 Eclipse projects: MyApp and MyAppLibrary. MyApp depends on the project MyAppLibrary.

We have problems running the app on a Curve 8530 running os 5.0.0.593. There are so many strange messages in the log that I half wonder if that device has some kind of device failure.

When it first runs, MyApp is supposed to send some information to a web service and get a message in return.

The app is becoming unresponsive during this process and ulitmately its crashing. I've got the event log and have all kinds of questions abouit its contents.

First, even before I install my app, I see messages like this:

a Java Exception - ForcedStackTraceException - 12/3 14:42:01
| net_rim_app_manager(1) 127 1
| net_rim_cldc-28(4C97EBD9)
| DebugSupport
| logStackTraces
| 0x2CEF
| net_rim_cldc-8(4C97EBD9)
| ApplicationProcess
| logMessageQueueOverflow
| 0x83B0
| net_rim_cldc-8(4C97EBD9)
| ApplicationProcess
| postMessage
| 0x8075
| net_rim_cldc-8(4C97EBD9)
| ApplicationManagerImpl
| postMessage
| 0x480D
| net_rim_cldc-8(4C97EBD9)
| ApplicationManagerImpl
| <private>
| 0x738F
| net_rim_cldc-8(4C97EBD9)
| ApplicationManagerImpl
| <private>
| 0x683E
| net_rim_cldc-8(4C97EBD9)
| ApplicationManagerImpl
| <init>
| 0x76E7
| net_rim_app_manager(4C97EC2D)
| ApplicationManagerApp
| main
| 0x2F

What causes such an error?

There are 104 of these errors. Some of them contain references to MyApp and MyAppLibrary. I'm assuming this is from a previously installed version.

Is this message:

TCP-WiFi:bb,js,ss,bg,em,http://www.test.myapp.com/BB/5/MyApp_full.jad

generated by the installation of my app?

I'm assuming these messages:

a net.rim.browser - Dsta - 12/3 14:19:43
E net.rim.browser -
SBHelper___ERROR:injectServiceBooks()513088.sbr.ykz not found - 12/3
14:19:43
i net.rim.browser - SBHelper___INFO:injectServiceBooks()HOMENPC=513088
GID - 12/3 14:19:43
E net.rim.browser -
SBHelper___ERROR:getCompressedResourceAsDataBuffer: 513088.sbr.ykz not
found - 12/3 14:19:43

indicate a missing service book. Is this correct? I thought service books were transmitted to the device on an as needed basis. Am I mistaken? What effect would this missing service book have?

a System - CMM: MyAppLib(3618) no sig from 0x414252 -
12/3 14:16:57
a System - CMM: delete MyAppLib4(3612) scheduled - 12/3 14:16:56
a System - CMM: delete MyAppLib-3(8049) scheduled - 12/3 14:16:56
a System - CMM: delete MyAppLib-2(3615) scheduled - 12/3 14:16:56
a System - CMM: delete MyAppLib-1(8052) scheduled - 12/3 14:16:56
a System - CMM: delete MyAppLib(3618) scheduled - 12/3 14:16:56

There are about 24 of the "CCM: delete" meesages. What do they signify?

A little while after the delete messages, I see this:

a System - Process MyApp(135) queue overflow; oldest event
dropped - 12/3 14:16:05

Is there any way to determine what event is causing the quere to overflow and what event is being dropped?

Next I see these:

a System - CMM: MyAppLib-4(3612) no sig from 0x54545252
- 12/3 14:14:33
a System - CMM: MyAppLib-3(8049) no sig from 0x54545252
- 12/3 14:14:33
a System - CMM: MyAppLib-2(3615) no sig from 0x54545252
- 12/3 14:14:33
a System - CMM: MyAppLib-1(8052) no sig from 0x54545252
- 12/3 14:14:33
a System - CMM: MyAppLib(3618) no sig from 0x545252 -
12/3 14:14:33
a System - CMM: MyAppLib-1(8052) no sig from 0x545252 -
12/3 14:14:33
a System - CMM: MyAppLib-1(8052) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyAppLib-2(3615) no sig from 0x545252 -
12/3 14:14:33
a System - CMM: MyAppLib-2(3615) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyAppLib-3(8049) no sig from 0x545252 -
12/3 14:14:33
a System - CMM: MyAppLib-3(8049) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyAppLib-4(3612) no sig from 0x545252 -
12/3 14:14:33
a System - CMM: MyAppLib-4(3612) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-1(3670) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-2(3642) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-3(8064) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-4(3627) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-5(8061) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-6(3624) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-7(8058) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-8(3621) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-9(8055) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-10(3675) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-11(8112) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-12(3684) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-13(3688) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-14(8123) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-15(8085) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-16(3648) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-17(8082) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-18(3645) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-19(8079) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-20(8076) no sig from 0x33 - 12/3 14:14:33
a System - CMM: MyApp-21(3639) no sig from 0x33 - 12/3 14:14:32
a System - CMM: MyApp-22(8073) no sig from 0x33 - 12/3 14:14:32
a System - CMM: MyApp-23(3636) no sig from 0x33 - 12/3 14:14:32
a System - CMM: MyApp-24(8070) no sig from 0x33 - 12/3 14:14:32
a System - CMM: MyApp-25(3633) no sig from 0x33 - 12/3 14:14:32
a System - CMM: MyApp-26(8067) no sig from 0x33 - 12/3 14:14:32
a System - CMM: MyApp-27(3630) no sig from 0x33 - 12/3 14:14:32

They also occur mentioning other apps on the device like DocsToGoCommon47, WordToGo47, SheetToGo47,
THK2_v42_320x240, SlideshowToGo47, Sudoku_v42_320x240, SheetToGo47Resource_en, SheetToGo47Resource_en_GB and a variety of others.


The app does register for push notification, and I do see:

W net.rim.blackberry.api.push - Berr java.lang.IllegalStateException:

How can I determine if that's from MyApp?

Are there any kind of diagnostics available to determine the health of a device?  These errors are so strange, I wonder if the device itself is having some kind of failure.

Developer
Posts: 19,636
Registered: ‎07-14-2008
My Device: Not Specified

Re: app becomes unresponsive, many errors in log, need help understanding them

Sorry, I suspect this is an application problem unfortunately.

 

I think you have some processing that is holding the Event Thread, and blocking the Event Thread processing.  The OS can't tell what Thread it is, so it dumps everything out.  That is why you get so many Thread stack traces in your Event Log.

 

You need to look for processing the either updates the UI frequently, or takes a long time when updating the UI.

 

If you go through all the Threads, looking for ones that are in your code (look at the very first entry to see), one of these is almost certain to be the culprit.

 

I suspect that you might be seeing on the 8350 because it is the slowest device you have tested on. 

 

You also need to review carefully the problem with the IllegalStateException from the push Thread.  This is again almost certain to be a coding bug, I suspect from the push Thread which is running in the background you attempt to update elements of the UI.  You can however probably debug this to see where the problem is.

Highlighted
Developer
Posts: 16,992
Registered: ‎07-29-2008
My Device: Z10 LE, Z30, Passport
My Carrier: O2 Germany

Re: app becomes unresponsive, many errors in log, need help understanding them

review this video:
http://supportforums.blackberry.com/t5/Java-Development/What-is-the-Event-Thread/ta-p/446865
----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Developer
Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified

Re: app becomes unresponsive, many errors in log, need help understanding them

If I'm reading the trace correctly, you've got 40+ threads running at the time of the queue overflow.

 

What is your application doing that it requries 40 threads?

 

Regular Contributor
Posts: 59
Registered: ‎05-10-2012
My Device: 8800
My Carrier: verizon

Re: app becomes unresponsive, many errors in log, need help understanding them

I don't have 40 threads running in my app. I have found out that push registration is goofed up and i'm looking at that.

just curious, what did you see that indicated 40 threads?
Regular Contributor
Posts: 59
Registered: ‎05-10-2012
My Device: 8800
My Carrier: verizon

Re: app becomes unresponsive, many errors in log, need help understanding them

Just a little update.....I found that push registration was being done from the Event thread.

 

Once I moved it into its own thread, I found that the push app id had expired.

 

I suspect push registration is consuming a bunch of resources while it waits to fail and that's what causing my strange event logs.

 

I've commented out push registration/usage and sent it to the user with the device that behaves badly.  We'll see....