[
https://issues.jboss.org/browse/JBWS-3724?page=com.atlassian.jira.plugin....
]
Julio Ynojosa commented on JBWS-3724:
-------------------------------------
The option you mention was discarded because in HTTP 1.0 new connections are open for each
request/response pair. And after each response the connection would be closed. This lead
to some big efficiency problems. I asked to several people and they do not recommend do
this.
I disabled Chunked encoding in client side, over HTTP 1.1 and i was hoping to do the same
in server side, keeping HTTP 1.1 because it means that chunked transfer encoding is an
option in HTTP 1.1
Disable HTTP chunked encoding in server side
--------------------------------------------
Key: JBWS-3724
URL:
https://issues.jboss.org/browse/JBWS-3724
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.4.0
Reporter: Julio Ynojosa
Priority: Minor
I've always seen that to disable chunking encoding is always related to client
configuration. How can it be disabled from server side? What configuration file can be
changed in JBoss or JBossWS to do that?
I disabled the "Chunked Transfer encoding" mechanism from clients to server
through a external library (AXIS2, client side). Now I need to do the same from server to
clients (server responses, i.e. server side) to ensure both requests and responses are
being sent without fragmentation.
According to documentation, I have configured the parameter "chunked size" to
zero (to get no fragmentation) in the "standard-jaxws-client-config.xml" file
and also updated JBossWS library to 3.4.0 version (higher version compatible with JBoss 5)
and yet I haven’t been able to deactivate the Chunking mechanism. It is reported that this
was an issue, but it was supposed to be solved since JBossWS 3.2.0
Is it anything additional that do I have to do in order to get this problem solved?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira