[
https://issues.apache.org/jira/browse/AXIS-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186524#comment-13186524
]
Nethanel Wizman commented on AXIS-2863:
---------------------------------------
Hi Nagaraj and Andreas,
Yes, this problem can be reproduced on my system every time.
I'm using the following axis1 jar: axis-1.4.jar
As for the XML size being sent - I'm not sure because I use axis indirectly.
There is a web service client I use in order to access a web service, and this
client uses axis-1.4.jar in order to communicate with this web service. In this
communication soap messages are being sent back and forth. If it's important I
can try to find out the size of the XML file size.
I'm using OC4J application server version 10.1.2 which works on Java version
1.4.2_04.
The memory heap size is set to 512MB. The problem can be reproduced of course
with smaller heap size – 64MB for instance.
In order to shed some more light on the problem, I can give some more
information:
The problem first happened in a production environment, where an "OutOfMemory"
error occasionally occurred.
I reproduced the problem in my lab by starting the application server and
starting a load application that sends requests repeatedly to that application
server.
Using JProfiler, I could notice that memory consumption is stable at first –
the usual chain-saw pattern that stays within a ~5MB variation from average
(the average is about 10MB).
After about 20 minutes there are huge peaks of memory consumption that go up
sometimes as much as the maximum allowed – 512MB.
After a few repetitions like that the dreaded "OutOfMemory" error occurs…
I can send you the JProfiler snapshot if necessary.
If more information is required please do not hesitate to contact me.
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-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
