10-16-2008 03:02 AM
I have developed a midlet application which is working fine on Blackberry Simulator and other non blackberry Models.
But when I run it on real device it hangs up as it's not able to open HttpConnection.
I have tried many things such as:-
1. appending ;deviceside=true and ;deviceside=false to the url.
2. I have done APN settings . I have "Airtel India" data plan. APN: airtelgprs.com and Username/Password : blank
My Blackberry Model is BlackBerry 8700g
Any idea what else I can do.. Please help
10-16-2008 09:36 AM
What happens when you try to make the connection? Is an exception thrown? If so, what is it? Or does the application hang? If so, please see this link.
Support - Application stops responding when opening a connection
Article Number: DB-00159
10-17-2008 02:42 AM
My application just hangs.
I don't get any exception.
I display a progressbar in the main thread and spawn a separate thread to make Htpconnection to bring data from the server. After this my application stucks on the progress bar screen .
I receive a dialog box informing me that application is going to make an Httpconnection when I press "Allow" application stucks on the progressbar screen.
I have changed security permissions also and allowed everything.
I have no clue what I try next. Please help.
10-17-2008 01:31 PM
10-20-2008 03:01 AM
My application is able to open the connection , create the outputstream, write bytes on the ouptutstream, close and flush the outputstream.
After this when I try to open the inputstream on the same connection(just after flushing the outputstream) application hangs.
No exception is thrown it just hangs.
10-20-2008 03:19 AM
When I attach my device to JDE debug I get following prints.( I just came to know this method of debugging in blackberry)
CMM: BlackBerry$2d4$2e2TrackBall$2den_US$2dDLFBB(4323) no sig from 0x33 (--Does this line indicate something as this is not System.out.println)
opening inStream (--After this no System.out.println appears.)
No stack trace
JVM: bklt @23302: timer
JVM: bklt @23304: idle 2
JVM: bklt @23305: setTimer 13
GME Rx Cid: IPPP
GME Rx Cid: IPPP
JVM: bklt @24969: timer
JVM: bklt @24971: idle 15
JVM: bklt @24972: setTimer 15
GME Rx Cid: IPPP
JVM: bklt @26893: timer
JVM: bklt @26894: idle 15
JVM: bklt @27174: setTimer 15
JVM: bklt @29095: timer
JVM: bklt @29097: idle 15
JVM: bklt @29098: setTimer 15
JVM: bklt @31018: timer
JVM: bklt @31020: idle 15
JVM: bklt @32232: setTimer 15
JVM: bklt @34152: timer
JVM: bklt @34153: idle 15
JVM: bklt @34155: setTimer 15
10-20-2008 07:29 AM
Normally in these cases, besides posting the code pieces which tend to be short and about the same in most cases,
I'd suggest trying to look at the server and find out what it actually sees - does it get a complete request, does
it send a response? The BB code is usually quite simple but there are a lot of changes in the data, things in the
network path, and idiosyncracies of servers that can make for confusing results. Do you have access to the server or
can you redirect your request to a dummy server and just make sure you are getting a request to which a response can be made?
Packet capture can help too if the simple approach doesn't work and there are no obvious problems in the BB code.