Greetings. I'm using the JBoss 3.2.3 and Tomcat 4.1.29 release. I created a servlet that returns a list of jobs running on my AS/400 server. Looking at the request client HTTP header, I do an XML/XSLT translation and send the appropriate stream to the device: HTML to a PC or WML to a WAP wireless device. My issue is this: using a PC, everything works OK. On my wireless device, I get a premature HTTP Error 503 - Service Unavailable.
By doing some logging to the JBoss console, while watching my wireless device, I see that the 503 is returned about 30 seconds after my request hits Tomcat. A few seconds later, my WML output is echoed to the console. If I could delay the sending of the 503 for about a minute, I'd be good to go.
I attempted to edit the /server/default/deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml file to increase the connectionTimeout attribute of the CoyoteConnector to "60000", but that had no effect.
Is there a guru around that can understand this weirdness?
Are You serving the WML as text or as WMLC(compiled) ? ...
Depending on Your mobile terminal(Device) capability and the WAPG(gateway) capability, You might have to serve the resource compiled in WBXML (Wireless Binary XML) ...
And are You setting Your response header accordingly ? ...