axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nethanel Wizman (Issue Comment Edited) (JIRA)" <axis-...@ws.apache.org>
Subject [jira] [Issue Comment Edited] (AXIS-2863) Circular Reference in Deserialization and XMLReader
Date Wed, 25 Jan 2012 07:19:40 GMT

    [ https://issues.apache.org/jira/browse/AXIS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192907#comment-13192907
] 

Nethanel Wizman edited comment on AXIS-2863 at 1/25/12 7:17 AM:
----------------------------------------------------------------

Hi Nagaraj,

The xml size is quite small, no more than 2KB.

The memory leak happens all the time, whether during load or not. It seems that this circular
reference is there as soon as Axis is getting into action.

Here are my answers for you:
1.	I've done the profiling with a single user running repeated requests to the OC4J instance,
about 4 requests per second. The JProfiler snapshot is too big to attach, I can sen you by
email if you want.
2.	The JVM is getting restarted at different frequencies, depending on the OC4J allocated
memory. With 64MB it's restarted after about 30-60 minutes; with 512MB it occurs after a very
long time: after a 6 weeks, or never at all.
3.	The biggest object size of the leak suspect is 24KB. It's the same value during normal
operation as it's just before the out of memory.
4.	There is no load balancer.
5.	It's a single host environment.
6.	At some point the memory is getting released, but it happens that there are very high peaks
of memory consumption for very short times, in which the out of memory occurs.

Thanks,
Nethanel
                
      was (Author: nel100):
    Hi Nagaraj,

The xml size is quite small, no more than 2KB.

The memory leak happens all the time, whether during load or not. It seems that this circular
reference is there as soon as Axis is getting into action.

Here are my answers for you:
1.	I've done the profiling with a single user running repeated requests to the OC4J instance,
about 4 requests per second. I've attached the JProfiler snapshot.
2.	The JVM is getting restarted at different frequencies, depending on the OC4J allocated
memory. With 64MB it's restarted after about 30-60 minutes; with 512MB it occurs after a very
long time: after a 6 weeks, or never at all.
3.	The biggest object size of the leak suspect is 24KB. It's the same value during normal
operation as it's just before the out of memory.
4.	There is no load balancer.
5.	It's a single host environment.
6.	At some point the memory is getting released, but it happens that there are very high peaks
of memory consumption for very short times, in which the out of memory occurs.

Thanks,
Nethanel
                  
> 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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message