You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/03/22 15:31:58 UTC
[jira] Closed: (AXIS-255) Out of Memory Error - tcpmon
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Mon, 22 Mar 2004 6:31 AM
not enough info to recreate the problem. Please reopen bug if you get the problem with latest cvs/1.2alpha.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-255
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-255
Summary: Out of Memory Error - tcpmon
Type: Bug
Status: Closed
Resolution: CANNOT REPRODUCE
Project: Axis
Components:
Basic Architecture
Versions:
beta-3
Assignee:
Reporter: Roy Kimbrell
Created: Wed, 7 Aug 2002 3:37 PM
Updated: Mon, 22 Mar 2004 6:31 AM
Environment: Operating System: Linux
Platform: PC
Description:
An out of memory error occurs at org.apache.catalina.core.ApplicationFilterChain.\
internalDoFilter(ApplicationFilterChain.java:269) under the following conditions:
1. In aimple timing test sending binary data to client, client requests a block
of data by sending a number = 4096*pow(2,x), where x is 0, 1, 2, ..., 11. That
is, the request is 4096, 8192, ..., up to 4194304 The returned byte array is
filled with the digit 0, 1, 2, ..., 'A'. The test program just sends the
request then prints timing, buffer.length, and the first byte of the returned
byte[].
2. The test succeeds up to and including the point of requesting a 64K block.
The test was run by sending the request, printing the report, then stopping.
The test was run again with the next larger request size, then run again with
the next larger size, etc. At 131K it fails with an out of memory report from
the server. (See attached report 1.)
3. An out of memory error also occurs by repeatedly running the test and asking
for a 4096 sized block. The test succeeds when running it in succession for
seven times. At the eighth time, it fails. (See attached report 2 and 2a).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira