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

Nagaraj commented on AXIS-2863:
-------------------------------

Hi Nethanel,
 It seems that this circular reference is there as soon as Axis is getting into 
action. 
Do you think this circular reference creation is the design of Apache Axis?

What about your service call? whether synchronous or asynchronous?
If asynchronous call then you may store all the objects in to callbacktarget 
right?


Sometimes i get the object request for allocation between 24MB to 65MB.Such a 
big request comes to the server for allocation.We can see good amount of free 
memory whenever we check the GC logs when out of memory occurs.The problem will 
be the heap fragmentation because it wont have contiguous memory to allocate 
the request.

So can we conclude like that
 the two big objects are accumulating memory always whenever request comes to 
server and not been cleared properly ?
Have you created any sample service for testing purpose and tried the same to 
call thru apache axis engine? if yes then did u see the behavior of axis? 
whether creating circular reference or not?

Andreas,
Could you please reply?
                
> 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

Reply via email to