ClientAbortException again.

[Kristian Rink-3]

Hi all;

unfortunately dealing with that friend again:

[...]
ClientAbortException:  java.io.IOException: Connection reset by peer
        at
org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:412)
        at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:417)
        at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339)
        at org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer.java:437)
        at org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:424)
        at
org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutputStream.java:145)
        at
de.planconnect.webui.projekt.controllers.WebUIDocumentController.getPlanList(WebUIDocumentController.java:68)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
[...]



Scenario: Downloading a > 10 MB file using a Spring MVC controller in a
webapp inside glassfish v2u2, fronted by an apache2 installation. I've
earlier been hinted that this possibly is just an MSIE issue not causing
any trouble, but in this case however, it does, and it does keep the
file from being transmitted correctly. As far as I see things (i.o.w. as
far as our network infrastructure is involved), there's no real reason
for this issue. On the customer side, in this (worst) case, there's
however no administrator / system maintainer at hand to check what could
possibly cause this problem.

Trying to get this sorted out, could this be caused by

- bandwidth problems on our side,

- issues in our application logic (i.e. local file access),

- configuration of application server and proxy - does
"ClientAbortException" mean the _client_ ,i.o.w. the end users browser,
or just the reverse apache2 proxy being "client" to the backend system,
has caused a "Connection reset by peer"?

Feels like clutching at straws, but I am running out of ideas on that
one... :/

Thanks in advance for any comments, best regards...
Kristian



--
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu@... * icq: 48874445 * fon: ++49 176 2447 2771 "One
dreaming alone, it will be only a dream; many dreaming together is the
beginning of a new reality." (Hundertwasser)


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

adding mod_jk in the title to brings the experts :-)

Kristian Rink wrote:

> Hi all;
>
> unfortunately dealing with that friend again:
>
> [...]
> ClientAbortException:  java.io.IOException: Connection reset by peer
> at
> org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:412)
> at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:417)
> at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339)
> at org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer.java:437)
> at org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:424)
> at
> org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutputStream.java:145)
> at
> de.planconnect.webui.projekt.controllers.WebUIDocumentController.getPlanList(WebUIDocumentController.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> [...]
>

This exception happens when the client close the connection before the
WebContainer has finished writing the response. Do you have a
firewall/proxy in between GlassFish and your client that can decide to
close the connection? You are using mod_jk right? Grizzly doesn't seems
to be in the picture here....

>
>
> Scenario: Downloading a > 10 MB file using a Spring MVC controller in a
> webapp inside glassfish v2u2, fronted by an apache2 installation. I've
> earlier been hinted that this possibly is just an MSIE issue not causing
> any trouble, but in this case however, it does, and it does keep the
> file from being transmitted correctly. As far as I see things (i.o.w. as
> far as our network infrastructure is involved), there's no real reason
> for this issue. On the customer side, in this (worst) case, there's
> however no administrator / system maintainer at hand to check what could
> possibly cause this problem.

I'm not an expert with mod_jk, so I cannot help as I would like. There
might be a time out valu on the Apache side?

>
> Trying to get this sorted out, could this be caused by
>
> - bandwidth problems on our side,
>
> - issues in our application logic (i.e. local file access),
>
> - configuration of application server and proxy - does
> "ClientAbortException" mean the _client_ ,i.o.w. the end users browser,
> or just the reverse apache2 proxy being "client" to the backend system,
> has caused a "Connection reset by peer"?

It is really because the connection get closed between the client and
the server, and the server was in the process of writing the response.

Hope that help.

A+

-- Jeanfrancois



>
> Feels like clutching at straws, but I am running out of ideas on that
> one... :/
>
> Thanks in advance for any comments, best regards...
> Kristian
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kristian Rink-3]

Salut Jeanfrancois;

and at first thanks a bunch for your comments on that, much appreciated.

Jeanfrancois Arcand schrieb:
>> [...] ClientAbortException:  java.io.IOException: Connection reset
>> by peer at
>>
org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:412)
>>  at
>> org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:417)
>>  at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339)
>>  at
>> org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer.java:437)
>>  at
>> org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:424)
>>  at
>>
org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutputStream.java:145)
>>  at
>>
de.planconnect.webui.projekt.controllers.WebUIDocumentController.getPlanList(WebUIDocumentController.java:68)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> [...]
> This exception happens when the client close the connection before
> the WebContainer has finished writing the response. Do you have a
> firewall/proxy in between GlassFish and your client that can decide
> to close the connection? You are using mod_jk right? Grizzly doesn't
> seems to be in the picture here....

Well no, actually not - at least not consciously. Doesn't glassfish
require some tomcat jars to be installed in order to allow for JK
protocol connections? If so, mod_jk is definitely out I guess, at least
unless this doesn't come with gfv2u2 out of the box...

We used to make use of mod_jk when these applications were still running
in tomcat6 but switched to mod_proxy altogether with moving them to
glassfish. About firewall/proxy - yes, there's the apache2/mod_proxy
reverse setup, and there is a border router/firewall which _shouldn't_
mess with this, at least according to its log files and configuration... :/

Another thing however is that we're using Spring MVC in this app, but I
so far am unaware that Spring comes pre-packaged with tomcat code - I'll
better check that, just to make sure...


> I'm not an expert with mod_jk, so I cannot help as I would like.
> There might be a time out valu on the Apache side?

Yes I thought about that as well. Situation however is that it seems to
randomly happen - sometimes just a couple of seconds after transmission
started, sometimes a few minutes after having next to 100 megs pushed
down the line... Our external border has pretty strict timeout
configurations per default which have been raised to more sane levels as
nothing worked initially using this box... :)


> It is really because the connection get closed between the client and
> the server, and the server was in the process of writing the
> response.
>
> Hope that help.

It does indeed, more things to ponder about. Maybe I'll get across this,
posted the same to an apache2 list, let's see what happens there. I have
seen the same behaviour using tomcat6 both along with mod_proxy and
mod_jk for that matters... First thing now is I'll make completely sure
that mod_jk is disabled and not in use for that anymore. And then I'll
see what else to do...

Thanks for your patience, best regards.
Kristian



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

kawazu wrote:
> Salut Jeanfrancois;
>
> and at first thanks a bunch for your comments on that, much appreciated.

you are welcome!

>
> Jeanfrancois Arcand schrieb:
>>> [...] ClientAbortException:  java.io.IOException: Connection reset
>>> by peer at
>>>
> org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:412)
>>>  at
>>> org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:417)
>>>  at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339)
>>>  at
>>> org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer.java:437)
>>>  at
>>> org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:424)
>>>  at
>>>
> org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutputStream.java:145)
>>>  at
>>>
> de.planconnect.webui.projekt.controllers.WebUIDocumentController.getPlanList(WebUIDocumentController.java:68)
>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>> [...]
>> This exception happens when the client close the connection before
>> the WebContainer has finished writing the response. Do you have a
>> firewall/proxy in between GlassFish and your client that can decide
>> to close the connection? You are using mod_jk right? Grizzly doesn't
>> seems to be in the picture here....
>
> Well no, actually not - at least not consciously. Doesn't glassfish
> require some tomcat jars to be installed in order to allow for JK
> protocol connections? If so, mod_jk is definitely out I guess, at least
> unless this doesn't come with gfv2u2 out of the box...
>
> We used to make use of mod_jk when these applications were still running
> in tomcat6 but switched to mod_proxy altogether with moving them to
> glassfish. About firewall/proxy - yes, there's the apache2/mod_proxy
> reverse setup, and there is a border router/firewall which _shouldn't_
> mess with this, at least according to its log files and configuration... :/

OK you are using mod_proxy. Can you share you config file? I'm just
curious to to see if that could be the problem.

>
> Another thing however is that we're using Spring MVC in this app, but I
> so far am unaware that Spring comes pre-packaged with tomcat code - I'll
> better check that, just to make sure...
>
>

Can you share your domain.xml? If you can't send it publicly, just send
it to jfarcand at apache dot org and I will take a look.

>> I'm not an expert with mod_jk, so I cannot help as I would like.
>> There might be a time out valu on the Apache side?
>
> Yes I thought about that as well. Situation however is that it seems to
> randomly happen - sometimes just a couple of seconds after transmission
> started, sometimes a few minutes after having next to 100 megs pushed
> down the line... Our external border has pretty strict timeout
> configurations per default which have been raised to more sane levels as
> nothing worked initially using this box... :)
>
>
>> It is really because the connection get closed between the client and
>> the server, and the server was in the process of writing the
>> response.
>>
>> Hope that help.
>
> It does indeed, more things to ponder about. Maybe I'll get across this,
> posted the same to an apache2 list, let's see what happens there. I have
> seen the same behaviour using tomcat6 both along with mod_proxy and
> mod_jk for that matters... First thing now is I'll make completely sure
> that mod_jk is disabled and not in use for that anymore. And then I'll
> see what else to do...

OK let me know what those folks thinks :-)

A+

-- Jeanfrancois

>
> Thanks for your patience, best regards.
> Kristian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kristian Rink-3]

Salut Jeanfrancois;

and first off, thanks loads for your ongoing support on that... Somehow
I still have hope to get this one resolved this time. :)



Jeanfrancois Arcand schrieb:
> OK you are using mod_proxy. Can you share you config file? I'm just
> curious to to see if that could be the problem.

The mod_proxy configuration itself is pretty much straightforward, I
followed several reverse-proxy-setup instructions on that, here:

[--/etc/apache2/mods-enabled/proxy.conf---]

ProxyRequests Off

<Proxy our.external.ip.addr >
                Order deny,allow
                Deny from all
</Proxy>

ProxyVia Off

[--/--]


The apache2 virtual host in question for this has the following
proxying-related configuration:


[--/etc/apache2/sites-enabled/main--]

ProxyPreserveHost On
ProxyPass /webprojekt/ http://192.168.1.242:8080/webprojekt/
ProxyPassReverse /webprojekt/ http://192.168.1.242:8080/webprojekt/
ProxyPass /web/ http://192.168.1.242:8080/web/
ProxyPassReverse /web/ http://192.168.1.242:8080/web/

[--/--]

We do have, as a matter of fact, mod_jk enabled on our apache2 to front
another application which still runs tomcat but there aren't any mod_jk
/ worker / JkMount configurations for any glassfish related resources...



>> Another thing however is that we're using Spring MVC in this app, but I
>> so far am unaware that Spring comes pre-packaged with tomcat code - I'll
>> better check that, just to make sure...
>
> Can you share your domain.xml? If you can't send it publicly, just send
> it to jfarcand at apache dot org and I will take a look.

No problem, got it attached after X'ing out the only thing I so far
consider somehow sensible in there (our JDBC environment). Thanks a
bunch in advance for taking care of this...


[apache2 responses]
> OK let me know what those folks thinks :-)

Nothing so far, unfortunately. :( As a matter of fact I have seen the
same outcome earlier trying to resolve the same problem related to our
tomcat6 installation and never really got over it up to now... :/


Anyway, thanks a bunch for your patience, best regards from
Dresden/Germany...
Kristian


--
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu@... * icq: 48874445 * fon: ++49 176 2447 2771 "One
dreaming alone, it will be only a dream; many dreaming together is the
beginning of a new reality." (Hundertwasser)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kristian Rink-3]

Kristian Rink schrieb:

>>> Another thing however is that we're using Spring MVC in this app, but I
>>> so far am unaware that Spring comes pre-packaged with tomcat code - I'll
>>> better check that, just to make sure...
>> Can you share your domain.xml? If you can't send it publicly, just send
>> it to jfarcand at apache dot org and I will take a look.
>
> No problem, got it attached after X'ing out the only thing I so far
> consider somehow sensible in there (our JDBC environment). Thanks a
> bunch in advance for taking care of this...

(...would have been better to actually attach the file rather than just
mentioning it - here it is...).

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE domain PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 9.1 Domain//EN" "http://www.sun.com/software/appserver/dtds/sun-domain_1_3.dtd">
<!--
   Copyright 1997-2007 Sun Microsystems, Inc.  All rights reserved.
   Use is subject to license terms.
-->
<!-- Generated from default-domain.xml.template -->
<!-- Avoid manual edits of this file. Run "asadmin verify-domain-xml" otherwise.-->
<domain application-root="${com.sun.aas.instanceRoot}/applications" log-root="${com.sun.aas.instanceRoot}/logs">
  <applications>
    <j2ee-application availability-enabled="false" directory-deployed="false" enabled="true" java-web-start-enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/__ejb_container_timer_app" name="__ejb_container_timer_app" object-type="system-all"/>
    <j2ee-application availability-enabled="false" directory-deployed="false" enabled="true" java-web-start-enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/MEjbApp" name="MEjbApp" object-type="system-all"/>
    <j2ee-application availability-enabled="false" directory-deployed="false" enabled="true" java-web-start-enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/__JWSappclients" name="__JWSappclients" object-type="system-all"/>
    <web-module availability-enabled="false" context-root="/web1" directory-deployed="true" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/adminapp/adminapp_war" name="adminapp" object-type="system-admin">
      <!-- System Web Module - DO NOT DELETE! -->
    </web-module>
    <web-module availability-enabled="false" context-root="" directory-deployed="true" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/admingui/adminGUI_war" name="admingui" object-type="system-admin">
      <!-- System Web Module - DO NOT DELETE! -->
    </web-module>
    <web-module availability-enabled="false" context-root="/__wstx-services" directory-deployed="true" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/wstx-services" name="WSTXServices" object-type="system-all"/>
    <lifecycle-module class-name="com.sun.jbi.framework.sun.SunASJBIBootstrap" classpath="${com.sun.aas.installRoot}/jbi/lib/jbi_framework.jar" enabled="true" is-failure-fatal="false" name="JBIFramework" object-type="system-all">
      <description>"JBI Framework LifecycleModule"</description>
      <property name="com.sun.jbi.home" value="${com.sun.aas.installRoot}/jbi"/>
    </lifecycle-module>
    <lifecycle-module class-name="com.sun.xml.ws.transport.tcp.server.glassfish.WSTCPLifeCycleModule" classpath="${com.sun.aas.installRoot}/lib/webservices-rt.jar" enabled="true" is-failure-fatal="false" name="WSTCPConnectorLCModule" object-type="system-all"/>
    <web-module availability-enabled="false" context-root="web" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/web" name="web" object-type="user"/>
    <web-module availability-enabled="false" context-root="/webprojekt" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/webprojekt" name="webprojekt" object-type="user"/>
    <web-module availability-enabled="false" context-root="/backend" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/backend" name="backend" object-type="user"/>
    <web-module availability-enabled="false" context-root="xport" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/xport" name="xport" object-type="user"/>
    <web-module availability-enabled="false" context-root="mailarclink" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/mailarclink" name="mailarclink" object-type="user"/>
    <web-module availability-enabled="false" context-root="notifyservice" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/notifyservice" name="notifyservice" object-type="user"/>
  </applications>
  <resources>
    <jdbc-resource enabled="true" jndi-name="jdbc/__TimerPool" object-type="system-admin" pool-name="__TimerPool"/>
    <jdbc-resource enabled="true" jndi-name="jdbc/__CallFlowPool" object-type="system-all" pool-name="__CallFlowPool"/>
    <jdbc-resource enabled="true" jndi-name="jdbc/__default" object-type="user" pool-name="DerbyPool"/>
    <jdbc-resource enabled="true" jndi-name="jdbc/XXXXXXX" object-type="user" pool-name="XXXXXXX">
      <description>XXXXXXX</description>
    </jdbc-resource>
    <jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="__CallFlowPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
      <property name="databaseName" value="${com.sun.aas.instanceRoot}/lib/databases/sun-callflow"/>
      <property name="connectionAttributes" value=";create=true"/>
    </jdbc-connection-pool>
    <jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="__TimerPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
      <property name="databaseName" value="${com.sun.aas.instanceRoot}/lib/databases/ejbtimer"/>
    </jdbc-connection-pool>
    <jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="DerbyPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
      <property name="PortNumber" value="1527"/>
      <property name="Password" value="APP"/>
      <property name="User" value="APP"/>
      <property name="serverName" value="localhost"/>
      <property name="DatabaseName" value="sun-appserv-samples"/>
      <property name="connectionAttributes" value=";create=true"/>
    </jdbc-connection-pool>
    <jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.sap.dbtech.jdbcext.XADataSourceSapDB" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="MaxDbPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.XADataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
      <property name="user" value="XXXXXXX"/>
      <property name="url" value="jdbc:XXXXXXX"/>
      <property name="password" value="XXXXXXX"/>
    </jdbc-connection-pool>
  </resources>
  <configs>
    <config dynamic-reconfiguration-enabled="true" name="server-config">
      <http-service>
        <access-log format="%client.name% %auth-user-name% %datetime% %request% %status% %response.length%" rotation-enabled="true" rotation-interval-in-minutes="15" rotation-policy="time" rotation-suffix="yyyy-MM-dd"/>
        <http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="8080" security-enabled="false" server-name="" xpowered-by="true">
          <property name="proxiedProtocols" value="ws/tcp"/>
        </http-listener>
        <http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="8181" security-enabled="true" server-name="" xpowered-by="true">
          <ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
        </http-listener>
        <http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="__asadmin" enabled="true" family="inet" id="admin-listener" port="4848" security-enabled="false" server-name="" xpowered-by="true"/>
        <http-listener acceptor-threads="15" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-backend" port="9898" security-enabled="false" server-name="" xpowered-by="true"/>
        <virtual-server hosts="${com.sun.aas.hostName}" http-listeners="http-listener-2,http-listener-1,http-listener-backend" id="server" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
          <property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>
          <property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
          <property name="sso-enabled" value="false"/>
        </virtual-server>
        <virtual-server hosts="${com.sun.aas.hostName}" http-listeners="admin-listener" id="__asadmin" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
          <property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>
          <property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
          <property name="sso-enabled" value="false"/>
        </virtual-server>
        <request-processing header-buffer-length-in-bytes="8192" initial-thread-count="5" request-timeout-in-seconds="30" thread-count="15" thread-increment="1"/>
        <keep-alive max-connections="250" thread-count="1" timeout-in-seconds="30"/>
        <connection-pool max-pending-count="4096" queue-size-in-bytes="4096" receive-buffer-size-in-bytes="4096" send-buffer-size-in-bytes="8192"/>
        <http-protocol default-response-type="AttributeDeprecated" default-type="text/html; charset=iso-8859-1" dns-lookup-enabled="false" forced-response-type="AttributeDeprecated" forced-type="text/html; charset=iso-8859-1" ssl-enabled="true" version="HTTP/1.1"/>
        <http-file-cache file-caching-enabled="false" file-transmission-enabled="false" globally-enabled="false" hash-init-size="0" max-age-in-seconds="30" max-files-count="1024" medium-file-size-limit-in-bytes="537600" medium-file-space-in-bytes="10485760" small-file-size-limit-in-bytes="2048" small-file-space-in-bytes="1048576"/>
        <property name="accessLoggingEnabled" value="false"/>
      </http-service>
      <iiop-service client-authentication-required="false">
        <orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1"/>
        <iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="3700" security-enabled="false"/>
        <iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="3820" security-enabled="true">
          <ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
        </iiop-listener>
        <iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="3920" security-enabled="true">
          <ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
        </iiop-listener>
      </iiop-service>
      <admin-service system-jmx-connector-name="system" type="das-and-server">
        <!-- The JSR 160 "system-jmx-connector" -->
        <jmx-connector accept-all="false" address="0.0.0.0" auth-realm-name="admin-realm" enabled="true" name="system" port="8686" protocol="rmi_jrmp" security-enabled="false">
          <ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
        </jmx-connector>
        <!-- The JSR 160 "system-jmx-connector" -->
        <das-config admin-session-timeout-in-minutes="60" autodeploy-dir="${com.sun.aas.instanceRoot}/autodeploy" autodeploy-enabled="true" autodeploy-jsp-precompilation-enabled="false" autodeploy-polling-interval-in-seconds="2" autodeploy-verifier-enabled="false" deploy-xml-validation="full" dynamic-reload-enabled="true" dynamic-reload-poll-interval-in-seconds="2"/>
      </admin-service>
      <web-container>
        <session-config>
          <session-manager>
            <manager-properties/>
            <store-properties/>
          </session-manager>
          <session-properties/>
        </session-config>
      </web-container>
      <ejb-container cache-idle-timeout-in-seconds="600" cache-resize-quantity="32" commit-option="B" max-cache-size="512" max-pool-size="32" pool-idle-timeout-in-seconds="600" pool-resize-quantity="8" removal-timeout-in-seconds="5400" session-store="${com.sun.aas.instanceRoot}/session-store" steady-pool-size="0" victim-selection-policy="nru">
        <ejb-timer-service max-redeliveries="1" minimum-delivery-interval-in-millis="7000" redelivery-interval-internal-in-millis="5000"/>
      </ejb-container>
      <mdb-container idle-timeout-in-seconds="600" max-pool-size="32" pool-resize-quantity="8" steady-pool-size="0"/>
      <jms-service addresslist-behavior="random" addresslist-iterations="3" default-jms-host="default_JMS_host" init-timeout-in-seconds="60" reconnect-attempts="3" reconnect-enabled="true" reconnect-interval-in-seconds="5" type="EMBEDDED">
        <jms-host admin-password="admin" admin-user-name="admin" host="pvdocsrv.planconnect.net" name="default_JMS_host" port="7676"/>
      </jms-service>
      <log-service alarms="false" file="${com.sun.aas.instanceRoot}/logs/server.log" log-rotation-limit-in-bytes="2000000" log-rotation-timelimit-in-minutes="0" log-to-console="false" retain-error-statistics-for-hours="5" use-system-logging="false">
        <module-log-levels admin="INFO" classloader="INFO" cmp="INFO" cmp-container="INFO" configuration="INFO" connector="INFO" corba="INFO" deployment="INFO" ejb-container="INFO" group-management-service="INFO" javamail="INFO" jaxr="INFO" jaxrpc="INFO" jdo="INFO" jms="INFO" jta="INFO" jts="INFO" management-event="INFO" mdb-container="INFO" naming="INFO" node-agent="INFO" resource-adapter="INFO" root="INFO" saaj="INFO" security="INFO" self-management="INFO" server="INFO" synchronization="INFO" util="INFO" verifier="INFO" web-container="INFO"/>
      </log-service>
      <security-service activate-default-principal-to-role-mapping="false" anonymous-role="AttributeDeprecated" audit-enabled="false" audit-modules="default" default-realm="file" jacc="default">
        <!-- All administrative users use this realm by default. -->
        <auth-realm classname="com.sun.enterprise.security.auth.realm.file.FileRealm" name="admin-realm">
          <property name="file" value="${com.sun.aas.instanceRoot}/config/admin-keyfile"/>
          <property name="jaas-context" value="fileRealm"/>
        </auth-realm>
        <!-- All administrative users use this realm by default. -->
        <auth-realm classname="com.sun.enterprise.security.auth.realm.file.FileRealm" name="file">
          <property name="file" value="${com.sun.aas.instanceRoot}/config/keyfile"/>
          <property name="jaas-context" value="fileRealm"/>
        </auth-realm>
        <auth-realm classname="com.sun.enterprise.security.auth.realm.certificate.CertificateRealm" name="certificate">
    </auth-realm>
        <jacc-provider name="default" policy-configuration-factory-provider="com.sun.enterprise.security.provider.PolicyConfigurationFactoryImpl" policy-provider="com.sun.enterprise.security.provider.PolicyWrapper">
          <property name="repository" value="${com.sun.aas.instanceRoot}/generated/policy"/>
        </jacc-provider>
        <audit-module classname="com.sun.enterprise.security.Audit" name="default">
          <property name="auditOn" value="false"/>
        </audit-module>
        <message-security-config auth-layer="SOAP">
          <!-- turned off by default -->
          <provider-config class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule" provider-id="XWS_ClientProvider" provider-type="client">
            <request-policy auth-source="content"/>
            <response-policy auth-source="content"/>
            <property name="encryption.key.alias" value="s1as"/>
            <property name="signature.key.alias" value="s1as"/>
            <property name="dynamic.username.password" value="false"/>
            <property name="debug" value="false"/>
          </provider-config>
          <provider-config class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule" provider-id="ClientProvider" provider-type="client">
            <request-policy auth-source="content"/>
            <response-policy auth-source="content"/>
            <property name="encryption.key.alias" value="s1as"/>
            <property name="signature.key.alias" value="s1as"/>
            <property name="dynamic.username.password" value="false"/>
            <property name="debug" value="false"/>
            <property name="security.config" value="${com.sun.aas.instanceRoot}/config/wss-server-config-1.0.xml"/>
          </provider-config>
          <provider-config class-name="com.sun.xml.wss.provider.ServerSecurityAuthModule" provider-id="XWS_ServerProvider" provider-type="server">
            <request-policy auth-source="content"/>
            <response-policy auth-source="content"/>
            <property name="encryption.key.alias" value="s1as"/>
            <property name="signature.key.alias" value="s1as"/>
            <property name="debug" value="false"/>
          </provider-config>
          <provider-config class-name="com.sun.xml.wss.provider.ServerSecurityAuthModule" provider-id="ServerProvider" provider-type="server">
            <request-policy auth-source="content"/>
            <response-policy auth-source="content"/>
            <property name="encryption.key.alias" value="s1as"/>
            <property name="signature.key.alias" value="s1as"/>
            <property name="debug" value="false"/>
            <property name="security.config" value="${com.sun.aas.instanceRoot}/config/wss-server-config-1.0.xml"/>
          </provider-config>
        </message-security-config>
      </security-service>
      <transaction-service automatic-recovery="false" heuristic-decision="rollback" keypoint-interval="65536" retry-timeout-in-seconds="600" timeout-in-seconds="0" tx-log-dir="${com.sun.aas.instanceRoot}/logs"/>
      <monitoring-service>
        <module-monitoring-levels connector-connection-pool="OFF" connector-service="OFF" ejb-container="OFF" http-service="LOW" jdbc-connection-pool="OFF" jms-service="OFF" jvm="OFF" orb="OFF" thread-pool="OFF" transaction-service="OFF" web-container="OFF"/>
      </monitoring-service>
      <diagnostic-service capture-app-dd="true" capture-hadb-info="true" capture-install-log="true" capture-system-info="true" compute-checksum="true" max-log-entries="500" min-log-level="INFO" verify-config="true"/>
      <java-config classpath-suffix="" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="">
        <!-- various required jvm-options -->
        <jvm-options>-XX:MaxPermSize=256m</jvm-options>
        <jvm-options>-server</jvm-options>
        <jvm-options>-Djava.endorsed.dirs=${com.sun.aas.installRoot}/lib/endorsed</jvm-options>
        <jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy</jvm-options>
        <jvm-options>-Djava.security.auth.login.config=${com.sun.aas.instanceRoot}/config/login.conf</jvm-options>
        <jvm-options>-Dsun.rmi.dgc.server.gcInterval=3600000</jvm-options>
        <jvm-options>-Dsun.rmi.dgc.client.gcInterval=3600000</jvm-options>
        <jvm-options>-Xmx512m</jvm-options>
        <jvm-options>-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}/config/keystore.jks</jvm-options>
        <jvm-options>-Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}/config/cacerts.jks</jvm-options>
        <jvm-options>-Djava.ext.dirs=${com.sun.aas.javaRoot}/lib/ext${path.separator}${com.sun.aas.javaRoot}/jre/lib/ext${path.separator}${com.sun.aas.instanceRoot}/lib/ext${path.separator}${com.sun.aas.derbyRoot}/lib</jvm-options>
        <jvm-options>-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver</jvm-options>
        <jvm-options>-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder</jvm-options>
        <jvm-options>-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory</jvm-options>
        <jvm-options>-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar</jvm-options>
        <jvm-options>-Dcom.sun.enterprise.taglisteners=jsf-impl.jar</jvm-options>
        <jvm-options>-XX:NewRatio=2</jvm-options>
        <jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>
        <!--
        Use the following jvm-options element to disable the quick startup:
        com.sun.enterprise.server.ss.ASQuickStartup=false
      -->
      </java-config>
      <thread-pools>
        <thread-pool idle-thread-timeout-in-seconds="120" max-thread-pool-size="200" min-thread-pool-size="0" num-work-queues="1" thread-pool-id="thread-pool-1"/>
      </thread-pools>
      <management-rules enabled="true">
  </management-rules>
    </config>
    <!-- config model with name "server-config" ends -->
  </configs>
  <servers>
    <server config-ref="server-config" lb-weight="100" name="server">
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="adminapp" virtual-servers="__asadmin"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="admingui" virtual-servers="__asadmin"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="JBIFramework"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="WSTXServices"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="WSTCPConnectorLCModule"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="__ejb_container_timer_app" virtual-servers="server"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="MEjbApp" virtual-servers="server"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="__JWSappclients" virtual-servers="server"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="web"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="backend"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="webprojekt"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="xport"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="mailarclink"/>
      <application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="notifyservice"/>
      <resource-ref enabled="true" ref="jdbc/__TimerPool"/>
      <resource-ref enabled="true" ref="jdbc/__CallFlowPool"/>
      <resource-ref enabled="true" ref="jdbc/__default"/>
      <resource-ref enabled="true" ref="jdbc/XXXXXXX"/>
    </server>
  </servers>
  <property name="administrative.domain.name" value="domain1"/>
</domain>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

sorry for the delay.

Kristian Rink wrote:

> Salut Jeanfrancois;
>
> and first off, thanks loads for your ongoing support on that... Somehow
> I still have hope to get this one resolved this time. :)
>
>
>
> Jeanfrancois Arcand schrieb:
>> OK you are using mod_proxy. Can you share you config file? I'm just
>> curious to to see if that could be the problem.
>
> The mod_proxy configuration itself is pretty much straightforward, I
> followed several reverse-proxy-setup instructions on that, here:
>
> [--/etc/apache2/mods-enabled/proxy.conf---]
>
> ProxyRequests Off
>
> <Proxy our.external.ip.addr >
>                 Order deny,allow
>                 Deny from all
> </Proxy>
>
> ProxyVia Off
>
> [--/--]
>
>
> The apache2 virtual host in question for this has the following
> proxying-related configuration:
>
>
> [--/etc/apache2/sites-enabled/main--]
>
> ProxyPreserveHost On
> ProxyPass /webprojekt/ http://192.168.1.242:8080/webprojekt/
> ProxyPassReverse /webprojekt/ http://192.168.1.242:8080/webprojekt/
> ProxyPass /web/ http://192.168.1.242:8080/web/
> ProxyPassReverse /web/ http://192.168.1.242:8080/web/
>
> [--/--]
>
> We do have, as a matter of fact, mod_jk enabled on our apache2 to front
> another application which still runs tomcat but there aren't any mod_jk
> / worker / JkMount configurations for any glassfish related resources...
>
>
>
>>> Another thing however is that we're using Spring MVC in this app, but I
>>> so far am unaware that Spring comes pre-packaged with tomcat code - I'll
>>> better check that, just to make sure...
>> Can you share your domain.xml? If you can't send it publicly, just send
>> it to jfarcand at apache dot org and I will take a look.
>
> No problem, got it attached after X'ing out the only thing I so far
> consider somehow sensible in there (our JDBC environment). Thanks a
> bunch in advance for taking care of this...

I've replicated your environment bu wasn't able to reproduce the
problem. But one thing I noticed is the <http-listener
acceptor-threads="5".... let the acceptor-threads value equals to 1.
That property is not well tested and I suspect that could be the issue.
Instead, just increase:

<request-processing ...thread-count="60"/>

Let me know what you get.

Thanks!

-- Jeanfrancois

>
>
> [apache2 responses]
>> OK let me know what those folks thinks :-)
>
> Nothing so far, unfortunately. :( As a matter of fact I have seen the
> same outcome earlier trying to resolve the same problem related to our
> tomcat6 installation and never really got over it up to now... :/
>
>
> Anyway, thanks a bunch for your patience, best regards from
> Dresden/Germany...
> Kristian
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kristian Rink-3]

Salut Jeanfrancois;

and first off thanks a bunch for your message.

Jeanfrancois Arcand schrieb:
> sorry for the delay.

No problem at all - too glad seeing you help sorting this thing out. :)

[...]

> I've replicated your environment bu wasn't able to reproduce the
> problem. But one thing I noticed is the <http-listener
> acceptor-threads="5".... let the acceptor-threads value equals to 1.
> That property is not well tested and I suspect that could be the issue.
> Instead, just increase:
>
> <request-processing ...thread-count="60"/>
>
> Let me know what you get.
>

Changed it, seems to some degree indeed have improved things about this
confusing issue, thanks a bunch for pointing me here. :) Sadly however
it's not completely resolved yet, still the ClientAbortException does
pop up once in a while (well, actually 37 times this very morning
between 7:45 and 8:45 ...). Only similarity to be found is that all
users affected by this thing seem to use MSIE (5.0 .. 7.something). I
will see whether I can do some more debugging on our firewall/proxy
machines to maybe get better track of this problem...

Anyway thanks a load for your help on that, much appreciated. :)
Cheers, have a good new week...
Kristian


--
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu@... * icq: 48874445 * fon: ++49 176 2447 2771 "One
dreaming alone, it will be only a dream; many dreaming together is the
beginning of a new reality." (Hundertwasser)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kristian Rink-3]

Kristian Rink schrieb:

> [...]
>> I've replicated your environment bu wasn't able to reproduce the
>> problem. But one thing I noticed is the <http-listener
>> acceptor-threads="5".... let the acceptor-threads value equals to 1.
>> That property is not well tested and I suspect that could be the issue.
>> Instead, just increase:
>>
>> <request-processing ...thread-count="60"/>
>>
>> Let me know what you get.
>>
>
> Changed it, seems to some degree indeed have improved things about this
> confusing issue, thanks a bunch for pointing me here. :) Sadly however
> it's not completely resolved yet, still the ClientAbortException does
> pop up once in a while (well, actually 37 times this very morning
> between 7:45 and 8:45 ...).

Adding to that, after having it running for a while and talking to some
customers: In some situations, it seems, the very moment this exception
is being thrown on our site, the customer does see something like
"website not found or not available" in their browser... Strange things
goin' on there... :(

Cheers,
Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeanfrancois Arcand-2]

Salut,

Kristian Rink wrote:

> Kristian Rink schrieb:
>> [...]
>>> I've replicated your environment bu wasn't able to reproduce the
>>> problem. But one thing I noticed is the <http-listener
>>> acceptor-threads="5".... let the acceptor-threads value equals to 1.
>>> That property is not well tested and I suspect that could be the issue.
>>> Instead, just increase:
>>>
>>> <request-processing ...thread-count="60"/>
>>>
>>> Let me know what you get.
>>>
>> Changed it, seems to some degree indeed have improved things about this
>> confusing issue, thanks a bunch for pointing me here. :) Sadly however
>> it's not completely resolved yet, still the ClientAbortException does
>> pop up once in a while (well, actually 37 times this very morning
>> between 7:45 and 8:45 ...).
>
> Adding to that, after having it running for a while and talking to some
> customers: In some situations, it seems, the very moment this exception
> is being thrown on our site, the customer does see something like
> "website not found or not available" in their browser... Strange things
> goin' on there... :(

The error pa