Hi,
We are having problems posting large chunks of data via tomcat ssl. We
are seeing that there is a limitation on how many characters can be
submitted depending where the request is coming from. This is happening
only when Tomcat is accessed over HTTPS. Problem does not occur when
accessing Tomcat directly over HTTP (port 8080).
See testing results below...
Testing within the server where tomcat is installed/
Total characters successful - 15k out of 15k - there is no limitation.
Any thing we post goes thru fine.
Testing directly to the server IP or DNS from out side the subnet (My
desktop)
Max post size successful - 9417 bytes any variable with length more than
that fails. All posted parameters show up as null.
Testing via F5 (load balanced set up)
Max characters successful - 6013 bytes from server and my desktop any
variable with length more than that fails. All posted parameters show up
as null.
Testing directly from server to server within the same subnet
(172.28.76.x)
Total characters successful - 12663 out of 15k (this one worked
partially when set to 15k but only 12663 made it through loosing 3k of
data. This was a different result than the rest...in the sense that
this is the only scenario where things got posted partially.
As you can see something is limiting the amount of character data being
allowed as we test from different subnets. SSL puts a load in the data
being transfer as well something else, we have adjusted during testing
to accommodate for the extra load in order to make work but we have not
identify what is limiting are adding additional data to the transfer
package.
I have attached the server.xml
Please help and advice us how to resolve this.
Thanks,
Jyothi
<!-- Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" at this level.
Documentation at /docs/config/server.html
-->
<Server port="8005" shutdown="SHUTDOWN">
<!--APR library loader. Documentation at /docs/apr.html -->
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="OFF" />
<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html -->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<!-- Global JNDI resources
Documentation at /docs/jndi-resources-howto.html
-->
<GlobalNamingResources>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users
-->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" Note: A "Service" is not itself a "Container",
so you may not define subcomponents such as "Valves" at this level.
Documentation at /docs/config/service.html
-->
<Service name="SupportAnalyst">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL HTTP/1.1 Connector on port 8080
-->
<Connector port="80" address="172.28.76.117" protocol="HTTP/1.1"
maxThreads="150" maxPostSize="-1" maxSavePostSize="32000"
connectionTimeout="20000" redirectPort="443" />
<!-- Define a SSL HTTP/1.1 Connector on port 443 This connector uses the
JSSE configuration, when using APR, the connector should be using the
OpenSSL style configuration described in the APR documentation -->
<Connector port="443" address="172.28.76.117" protocol="org.apache.coyote.http11.Http11NioProtocol"
SSLEnabled="true" maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" maxPostSize="-1" maxSavePostSize="32000"
keystoreFile= "E:\Java\jre1.6.0_02\lib\security\sacacerts" keystorePass="changeit" />
<!-- <Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="443" address="172.28.76.117" minSpareThreads="5" maxSpareThreads="75"
enableLookups="true" disableUploadTimeout="true"
acceptCount="100" maxThreads="200"
scheme="https" secure="true" SSLEnabled="true"
keystoreFile= "E:\Java\jre1.6.0_02\lib\security\sacacerts" keystorePass="changeit"
clientAuth="false" sslProtocol="TLS" /> -->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009" protocol="AJP/1.3" redirectPort="443" />
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host).
Documentation at /docs/config/engine.html -->
<!-- You should set jvmRoute to support load-balancing via AJP ie :
<Engine name="Standalone" defaultHost="172.28.76.117" jvmRoute="jvm1">
-->
<Engine name="SupportAnalyst" defaultHost="172.28.76.117">
<!--For clustering, please take a look at documentation at:
/docs/cluster-howto.html (simple how to)
/docs/config/cluster.html (reference documentation) -->
<!--
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
-->
<!-- The request dumper valve dumps useful debugging information about
the request and response data received and sent by Tomcat.
Documentation at: /docs/config/valve.html -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
<!-- Define the default virtual host
Note: XML Schema validation will not work with Xerces 2.2.
-->
<Host name="172.28.76.117" appBase="webapps/supportanalyst"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
</Host>
</Engine>
</Service>
<Service name="SelfService">
<Connector port="80" address="172.28.76.150" protocol="HTTP/1.1"
maxThreads="150" connectionTimeout="20000" maxPostSize="-1"
maxSavePostSize="32000" redirectPort="443" />
<Connector port="443" address="172.28.76.150" protocol="org.apache.coyote.http11.Http11NioProtocol"
SSLEnabled="true" maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" maxPostSize="-1" maxSavePostSize="32000"
keystoreFile= "E:\Java\jre1.6.0_02\lib\security\sscacerts" keystorePass="changeit" />
<!--
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="443" address="172.28.76.150" minSpareThreads="5" maxSpareThreads="75"
enableLookups="true" disableUploadTimeout="true"
acceptCount="100" maxThreads="200"
scheme="https" secure="true" SSLEnabled="true"
keystoreFile= "E:\Java\jre1.6.0_02\lib\security\sscacerts" keystorePass="changeit"
clientAuth="false" sslProtocol="TLS" />
-->
<Engine name="Selfservice" defaultHost="172.28.76.150">
<Host name="172.28.76.150" appBase="webapps/selfservice"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<!-- SingleSignOn valve, share authentication between web applications
Documentation at: /docs/config/valve.html -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
-->
<!-- Access log processes all example.
Documentation at: /docs/config/valve.html -->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
-->
</Host>
</Engine>
</Service>
</Server>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
