fyi.

The problem is the flush(). When this is taken out, all is OK.

Short answer: It's a Nokia bug

Long answer: You need to give more information about what devices you are using, and the nature of the problem. However, I have seen this problem before where the...

It's sent as a standard SMS, so the billing is exactly the same as if the user composed and sent the SMS using the phone.

I have an app. which works fine on the 7210 emulator (http 1.0) but not the Series 60 (http 1.1). The symptom is that with the latter emulator, my Java servlet receives no POST data, only the header....

You need to understand that the MIDP implementation on a given phone is hardwired to use either TCP/IP or WAP. You cannot change this.

Thus some phones (eg. P800) use TCP/IP, other phones (eg...

No

You're gonna have to read a primer on TCP/IP. The answer to your question is (and I suspect this isn't gonna help you much) ...

HTTP is a protocol which runs over ...
TCP which is another...

2 connections does *not* double the cost, in fact depending on your application it can reduce the cost.

On GPRS the customer is billed for bytes transmitted & received, irrespective of whether...

Series 40 and Series 60 use totally different http stacks. This means they have their own unique set of problems. Our product is an MSN IM client and we probably spent 50% of our development time on...

The correct question is "explain the difference between a GPRS WAP Access Point and a GPRS Internet Access Point".

Some J2ME phones implement http over WAP (eg. Nokia Series 40, Sharp GX10). Other...

Holding an http connection open doesn't work on Series 40, only on Series 60. We have an IM client for MSN (and Yahoo) and most of the problems we faced were on Series 40 and the intervention of the...

You can't change the mode from mMode to Internet. When Nokia implement J2ME, they decide whether they will implement the http API's over WAP or TCP/IP. On series 40 they opted for WAP, on Serise 60...

In addition to bvolk's comments, the biggest problem you'll face is teasing your data reliably and consistently through the operator's cWAP gateway.

The emulators are great for giving you a false...

Two comments ...

Using cookies to track sessions in J2ME is a *bad* idea. This is because on those handsets which implement http over WAP, most WAP gateways have the habit of munging or simply...

Not sure a Nokia forum is the best place to post a Sharp question, but anyways ...

> Has anyone ever seen this?
"Discontinued" sounds like an uncaught exception.

> Anyone know of a problem...

Switching to GET is generally a bad idea.
The Nokia bug coefficient for GET is even hgher than for POST.

I've seen various reports about the limit of a GET on different Nokia devices, but imho...

On the handsets you list, http traffic is routed via WAP. Therefore the headers are probably being added by the WAP gateway, not by the phone.

Hhhmmm
You've got a Null Pointer Exception in addCommand().

It looks like a plain old fashioned programming error. What does your call to addCommand() look like, and are any of its arguments null...

barryler you don;t give enough information about your problem.
Your configuration and a code fragment would help.

I'm gonna guess that the "Authorisation" message is not an http failure, but...

This is a password protected password store which is kinda similar.

http://www.javawi.de/

You might like to approach the author to see if he will permit you use of his code.

Try http://www.javacommerce.com/projects/popmail/index.html

This seems to do everything you need

We've just completed an Instant Messaging client which has many of the same requirements you mention.

Here are some learnings ...

1) Ignore the emulators. Their networking behaviour has nothing...

what do i need?
An emulator, a server, a connection between the emulator and the server

where do i need to put my servlet at?
on the server

do i need a local web server?
no. any server that...

Jalev is right. The problem only affects Series 40 devices. (Series 60 has a different set of bugs).

Be careful about the January date. I've just boght a new 6100 (it now being late June) and it...

I just wanna congratulate Kui for going the extra mile to help a fellow developer. I've seen too many posts here of the "I've got it working so you must be stupid" variety.

Well done Kui