noice in SOAP reply

[ge0ffrey]

I tried JBoss WS 1.0.3 (patched on a 4.0.4-GA JBoss with a EJB3 profile) with a @WebService annotation on a @Stateless bean. The Stateless bean had a method String sayHello().

When I send a SOAP messages (using WTK 2.2), the reply contained noise (the numbers):

<...>
35
<...sayHello/>
7
<...>
0

Any idea what could be causing this?

[ge0ffrey]

I installed a pipeline between the client and server which shows the problem:

POST /seems-ejb/SeemsServiceImpl HTTP/1.1
User-Agent: Profile/MIDP-1.0 Configuration/CLDC-1.0
Content-Language: en-US
Content-Type: text/xml
SOAPAction: "
User-Agent: UNTRUSTED/1.0
Content-Length: 325
Host: geoffreydesktop:8081

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:tns="http://seems.kahosl.be/jaws">
<soap:Body>
<tns:sayHello>
</tns:sayHello>
</soap:Body>
</soap:Envelope>
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)/Tomcat-5.5
Set-Cookie: JSESSIONID=DAD82CAF9143C49861F34EFD5131AB5F; Path=/
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Mon, 16 Oct 2006 15:18:24 GMT

e2
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><ns1:sayHelloResponse xmlns:ns1='http://seems.kahosl.be/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'><ns1:result>Hello:)
d
</ns1:result>
17
</ns1:sayHelloResponse>
1a
</env:Body></env:Envelope>
0

[jason.greene]

Transfer-Encoding: chunked

This is a normal HTTP chunked message. The message is split into multiple chunks, each chunk starts with the length in hex, followed by the data. The end is signified by a 0 length chunk.

-Jason

[ge0ffrey]

Ah :)

Can I disable HTTP chunking?

[thomas.diesler]

[01:17:58] Thomas Diesler: so if the receiver cant handle it, it their problem?
[01:18:10] Jason Greene: yeah then they aren't HTTP/1.1 compliant
[01:18:20] Thomas Diesler: merci
[01:18:34] Jason Greene: in which case we can add them to the restricted agent list
[01:18:36] ? in tomcat
[01:18:42] ? which will downgrade them to 1.0
[01:19:18] Thomas Diesler: is this a tomcat feature?
[01:19:30] Jason Greene: yes its in the server.xml file
[01:19:56] ? there might be some other option to always disable chunked
[01:20:14] ? but that would cause tomcat to double before the entire response to get the length

[ge0ffrey]

Thanks,
I tried setting the "Connection: close" parameter on the client side for the HTTP connection, but that didn't work because the WTK webservices don't have any API to access the HttpConnection AFAIK