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

Michael Olson commented on AXIS-2698:
-------------------------------------

I am using Axis 1.4, and I consistently get this error.  It is not a matter of 
whether or not the error occurs, only when.  Also, it does not take 3 or 4 days 
for me; if I leave my threads running at 1 request per second, they have all 
died before 24 hours has elapsed.  I would agree with whoever marked this bug 
as critical.  This makes the deserialization function incredibly fragile and 
undependable for long term processing.  Is there any chance of getting this 
assigned to someone?

> SAX2EventRecorder causes Out of memory during Deserialization
> -------------------------------------------------------------
>
>                 Key: AXIS-2698
>                 URL: https://issues.apache.org/jira/browse/AXIS-2698
>             Project: Axis
>          Issue Type: Bug
>          Components: Serialization/Deserialization
>    Affects Versions: 1.2
>         Environment: IBM AIX 5.2.,  Client: java 1.4.2 Server: PERL, SOAPLite
>            Reporter: Jens Rottgardt
>            Priority: Critical
>
> After undetermined time (3 or 4 days) the java client crashes with an out of 
> memeory exception. Analyzing the head dump showes that during the 
> deserialization the SAX2EventRecorder$objArrayVector.add  produces a huge 
> amount of MessageElemets. The returned message is a 3times nested array 
> containg in the inner arry just a strings [ [ [ key~value, ..., key~value ] ] 
> ]. Here a snippit of the array
> [
>           [
>             [
>               'range.type~INTEGER',
>               'range.mode~LASTCHANGE',
>               'attribute.state~error',
>               'lower-limit.value~2',
>               'lower-limit.isIncluded~FALSE',
>               'type.id~fhkh00',
>               'attribute.id~timestamp.last-change-physical',
>               'fhkh00.host~lwfis24',
>               'fhkh00.id~DVD337SF',
>               'fhkh00.instance~A11F2411'
>             ],
>             [
>               'range.type~INTEGER',
>               'range.mode~LASTCHANGE',
>               'attribute.state~error',
>               'upper-limit.value~0',
>               'upper-limit.isIncluded~FALSE',
>               'type.id~fhkh00',
>               'attribute.id~timestamp.last-change-physical',
>               'fhkh00.host~lwfis24',
>               'fhkh00.id~DVD337SF',
>               'fhkh00.instance~A11F2411'
>             ],
>             [
>               'range.type~INTEGER',
>               'range.mode~LASTCHANGE',
>               'attribute.state~ok',
>               'lower-limit.value~0',
>               'lower-limit.isIncluded~TRUE',
>               'upper-limit.value~2',
>               'upper-limit.isIncluded~TRUE',
>               'type.id~fhkh00',
>               'attribute.id~timestamp.last-change-physical',
>               'fhkh00.host~lwfis24',
>               'fhkh00.id~DVD337SF',
>               'fhkh00.instance~A11F2411'
>             ]
>           ]
>       ]
>        
>    

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to