You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jens Rottgardt (JIRA)" <ax...@ws.apache.org> on 2007/09/26 15:46:50 UTC
[jira] Created: (AXIS-2698) SAX2EventRecorder causes Out of memory
during Deserialization
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2698) SAX2EventRecorder causes Out of
memory during Deserialization
Posted by "Michael Olson (JIRA)" <ax...@ws.apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2698) SAX2EventRecorder causes Out of
memory during Deserialization
Posted by "Sharath (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736676#action_12736676 ]
Sharath commented on AXIS-2698:
-------------------------------
I have a critical issue with deserializing Java Array with 3000+ length
Does any one have fix for this issue or is it being worked out.
> 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.
[jira] Commented: (AXIS-2698) SAX2EventRecorder causes Out of
memory during Deserialization
Posted by "Bjorn Townsend (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530793 ]
Bjorn Townsend commented on AXIS-2698:
--------------------------------------
Have you considered trying the latest version of Axis, verison 1.4? Many memory leaks have been fixed since 1.2.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS-2698) SAX2EventRecorder causes Out of
memory during Deserialization
Posted by "Jens Rottgardt (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531493 ]
Jens Rottgardt commented on AXIS-2698:
--------------------------------------
Hello,
I have followed Bjorn's advice and updated AIXS from 1.2.1 to 1.4 but the problem still exists. The out of memory occures exactly at the same line.
java.lang.OutOfMemoryError
at org.apache.axis.message.SAX2EventRecorder$objArrayVector.add(SAX2EventRecorder.java(Compiled Code))
at org.apache.axis.message.SAX2EventRecorder.endElement(SAX2EventRecorder.java(Inlined Compiled Code))
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java(Compiled Code))
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java(Compiled Code))
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java(Compiled Code))
at org.apache.axis.Message.getSOAPEnvelope(Message.java(Inlined Compiled Code))
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java(Compiled Code))
at org.apache.axis.client.AxisClient.invoke(AxisClient.java(Compiled Code))
at org.apache.axis.client.Call.invokeEngine(Call.java(Compiled Code))
at org.apache.axis.client.Call.invoke(Call.java(Compiled Code))
at org.apache.axis.client.Call.invoke(Call.java(Compiled Code))
at org.apache.axis.client.Call.invoke(Call.java(Compiled Code))
at org.apache.axis.client.Call.invoke(Call.java(Compiled Code))
at com.vwag.fh.common.fsp.AbstractConnector.genericGetAllData(AbstractConnector.java(Inlined Compiled Code))
at com.vwag.fh.common.fsp.HDTServiceImpl.getAllHDTData(HDTServiceImpl.java(Inlined Compiled Code))
at fh.sysmon.adapter.service.fsp.implementation.HDTConnectorDelegator.getAvailableItemMap(HDTConnectorDelegator.java(Compiled Code))
at fh.sysmon.adapter.service.fsp.implementation.HDTConnectorDelegator.getAvailableMbeans(HDTConnectorDelegator.java(Compiled Code))
at fh.sysmon.adapter.service.fsp.implementation.FSPResourceInfoBulkUpdateJob.updateContent(FSPResourceInfoBulkUpdateJob.java(Compiled Code))
at fh.sysmon.adapter.service.fsp.implementation.FSPResourceInfoBulkUpdateJob.execute(FSPResourceInfoBulkUpdateJob.java(Compiled Code))
at fh.sysmon.common.scheduler.DummyScheduler.alarm(DummyScheduler.java(Compiled Code))
at fh.evo.common.timer.Alarm.run(Alarm.java(Compiled Code))
at java.lang.Thread.run(Thread.java:570)
... Jens
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org