Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 99937 invoked from network); 1 Oct 2004 13:47:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Oct 2004 13:47:18 -0000 Received: (qmail 58101 invoked by uid 500); 1 Oct 2004 13:46:45 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 58062 invoked by uid 500); 1 Oct 2004 13:46:44 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 58048 invoked by uid 99); 1 Oct 2004 13:46:44 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of woolfel@gmail.com designates 64.233.170.198 as permitted sender) Received: from [64.233.170.198] (HELO mproxy.gmail.com) (64.233.170.198) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 01 Oct 2004 06:46:43 -0700 Received: by mproxy.gmail.com with SMTP id 79so3643655rnk for ; Fri, 01 Oct 2004 06:46:41 -0700 (PDT) Received: by 10.38.70.21 with SMTP id s21mr1779383rna; Fri, 01 Oct 2004 06:46:41 -0700 (PDT) Received: by 10.38.164.30 with HTTP; Fri, 1 Oct 2004 06:46:41 -0700 (PDT) Message-ID: <27e674a90410010646280ee6e6@mail.gmail.com> Date: Fri, 1 Oct 2004 09:46:41 -0400 From: Peter Lin Reply-To: Peter Lin To: Tomcat Users List Subject: Re: WAP Gateway In-Reply-To: <20041001115616.55482.qmail@web8401.mail.in.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1096630261.4470.ezmlm@jakarta.apache.org> <20041001115616.55482.qmail@web8401.mail.in.yahoo.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N it depends on which wap gateway it is. the older wap gateways had a page limit, so the solution to that is to break pages into smaller chunks. It's hard to tell if the problem you see is related to that. back when i worked on WAP in 99, we figured out that openwave's WAP gateway had a limit of 1.4K. if the server tried to send a page that was greater than 1.4K, it wouldn't get through. this was going to microbrowsers running HDML/WML. I believe Nokia's WAP gateway had a similar limit back then. an easy way to test is to send a page that is less than 1K through the WAP gateway and see if it goes through. If that does, you can then gradually increase the size and figure out what the limit it is. hope that helps peter On Fri, 1 Oct 2004 12:56:16 +0100 (BST), Vijay Mathew wrote: > hello, > I am trying to send some data using POST from a > BlackBerry handheld device to a servlet deployed in > tomcat. everything works fine when i use the > BlackBerry simulator. But when i use the device and > connect with a WAP Gateway, tomcat hangs when large > packets are transmitted. Is there any special > configurations to be made in tomcat to enable it work > propertly with WAP gateways? > I am in need for an immediate solution. > thanks in advance > best regards > Vijay Mathew > > > ________________________________________________________________________ > Yahoo! India Matrimony: Find your life partner online > Go to: http://yahoo.shaadi.com/india-matrimony > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org