[
https://issues.apache.org/jira/browse/AXIS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186810#comment-13186810
]
Nagaraj commented on AXIS-2863:
-------------------------------
Hi Nethanel,
I have asked the xml file size to check whether axis supports Large file
requests or not.I'm suspecting that the axis behavior could be changed if it
gets large xml files for parsing.But need to confirm this.
We are also using OC4J app server with with 4 oc4j processes for an oc4j
instance.The ibm jdk version is 1.4 only.
Our JVM Arguments are Xmx2048m(Min 512MB and max 2GB)
I have done profiling for single user and checked the memory utilizations and
didn't find any issues at the time.
I haven't done profiling for more than one users which you have done it.So,im
not sure about the memory utilizations.
I have the following questions for you
1.At what user load you did the profiling?( I can understand clearly if you
send the user load details.If possible you can send snapshot also)
2.How frequent your JVM is getting restarted?
3.At the time of out of memory,what is the biggest object size u found in
theleak suspect? and do you see any heap fragmentation problem in the memory?
4.What is the load balancing method you are handling?(round robin or someother?)
5.Is it clustered env or single hosts?
6.Suppose the free heap memory is getting reduced and allocated memory is
increasing, Have you ever noticed at any point of time the free memory bounced
back?(for Ex: initiall free memory is 400MB and allocated is 100MB,after some
GC's the allocated memory is getting released or it is increasing until out of
memory)
> Circular Reference in Deserialization and XMLReader
> ---------------------------------------------------
>
> Key: AXIS-2863
> URL: https://issues.apache.org/jira/browse/AXIS-2863
> Project: Axis
> Issue Type: Bug
> Components: Serialization/Deserialization
> Affects Versions: 1.4
> Environment: IBM AIX JRE 1.4.2
> Reporter: Nagaraj
> Priority: Critical
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I got out of memory error and when i analysed heap dump, i was getting
> infinite active references of deserialization and xmlreader.When expand
> Deserialization context,XMLReader reference is there and when expand
> XMLReader,Deserialization reference is there.It seems to be circular
> reference.The sample output of heap dump is given below.
>
> | Shallow Heap | Retained Heap | Percentage
> org.apache.axis.encoding.DeserializationContext @ 0x505dbbc8 | 88 |
> 988,356,416 | 60.92%
> |- oracle.xml.parser.v2.XMLReader @ 0x505dc5f8 | 128 | 988,272,872 | 60.92%
> | |- org.apache.axis.encoding.DeserializationContext @ 0x504ce7d8 | 88 |
> 988,263,992 | 60.92%
> | | |- oracle.xml.parser.v2.XMLReader @ 0x505385b0 | 128 | 988,190,680 |
> 60.91%
> | | | |- org.apache.axis.encoding.DeserializationContext @ 0x89592c00 | 88 |
> 988,181,800 | 60.91%
> | | | | |- oracle.xml.parser.v2.XMLReader @ 0x89592e00 | 128 | 988,067,936 |
> 60.91%
> | | | | | |- org.apache.axis.encoding.DeserializationContext @ 0x50799858 |
> 88 | 988,059,056 | 60.91%
> | | | | | | |- oracle.xml.parser.v2.XMLReader @ 0x5079d0e8 | 128 |
> 987,975,512 | 60.90%
> | | | | | | | |- org.apache.axis.encoding.DeserializationContext @ 0x505e23d8
> | 88 | 987,966,632 | 60.90%
> | | | | | | | | |- oracle.xml.parser.v2.XMLReader @ 0x505e1c08 | 128 |
> 987,892,528 | 60.90%
> Please provide some solution for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
