[BlazeDS]Error serialization exceeds the max collection object nest level of '15'.

I am getting the following error when I try to import large data from server to client. I am not able to find where I can change the settings to handle more data.
[BlazeDS]Error serialization exceeds the max collection object nest level of '15'.
flex.messaging.io.SerializationException: Error serialization exceeds the max collection object nest level of '15'.
        at flex.messaging.io.amf.AmfIO.increaseNestCollectionLevel(AmfIO.java:142)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:753)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:439)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:453)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:439)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:453)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)

Similar Messages

[svn:bz-4.0.0_fixes] 20451: backporting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20451
Revision: 20451
Author:   [email protected]
Date:     2011-02-24 08:33:31 -0800 (Thu, 24 Feb 2011)
Log Message:
backporting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/common/src/flex/messaging/errors.properties
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

[svn:bz-3.x] 20443: back porting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20443
Revision: 20443
Author:   [email protected]
Date:     2011-02-23 21:19:22 -0800 (Wed, 23 Feb 2011)
Log Message:
back porting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/3.x/modules/common/src/java/flex/messaging/errors.properties
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/AmfIO.java

Flooded with error: Table RequestUsage_PartitionX has 442892288 bytes that has exceeded the max bytes 442857142

Hi all,
Since last week my 2013 farm (3 WFE, 3 App server, SQL 2012) application event log flooded with error every 5 minutes.
Table RequestUsage_PartitionX has 442892288 bytes that has exceeded the max bytes 442857142.
I have google the error and only found Steve Mann's blog discussing about this. Yet there is no additional information in terms of how to fix it. Just wondering if anybody has seen this and know how to fix it?
Appreciate any suggestion and thanks in advance.
Sally

Hi Sally,
Thank you for your posting!
For your error, it is coming from the Usage Infrastructure. The root cause is that your SharePoint Server usage data is exceeding the daily partition size for the logging DataBase.
For more detailed information, you can refer to the blog:
Blind spots in Usage file and Web Analytics Reports
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support

[svn:bz-trunk] 20609: Change the default max object nest level from 1024 to 512.

Revision: 20609
Revision: 20609
Author:   [email protected]
Date:     2011-03-04 10:23:41 -0800 (Fri, 04 Mar 2011)
Log Message:
Change the default max object nest level from 1024 to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Update documentation for the max object nest level setting to reflect the new default.
Add documentation for the new max collection nest level setting.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/trunk/resources/config/services-config.xml

You should be able to get some more precise information from your Xorg logs, but I would bet it is related to the evdev driver. Some of the options in your xorg.conf no longer work with the latest version. For now you should be able to either map your mouse directly to the appropriate /dev/event* entry or change to the standard mouse driver, both of those methods should be in the wiki.
You are supposed to be able to use the evdev driver without the input section of your xorg.conf by using dbus/hal autodetection, but AFAIK at the moment the xorg-server package still isn't compiled with hal support, so you would have to patch and rebuild the package.

Layer 0 exceeds the max layer

When I try formatting a dvd I get the message: Layer 0 exceeds the max layer size allowed please choose a suitable marker location that will support this condition.
I brought in a 2 hour and 45 minute vcr video and added chapter markers. Does this simply mean the size is too big or what is it looking for?
Thank You

DUAL LAYER BREAK POINTS
Basically when burning a DL disc there needs to be something called a "break point" which is effectively a marker at what is considered a "permissable" spot for a break point. The requirements for break points have certain conditions (Layers cannot exceed certain sizes, Layer 0 needs to be larger than Layer 1 etc.) If there is not a marker that meets these conditions, then you will get various error messages.
1.) In a DL disc Layer 0 needs to be larger than Layer 1
2.) A marker needs to be placed as a Layer Break in the project to indicate the layers.
3.) You can start by assuming the marker will be right around the 1/2 point of the disc (give or take)
4.) Find the place which is about 1/2 way and put a few markers in there
5.) Build the DVD to the hard drive then select format. If there is a suitable layer break marker it will be black otherwise it will be gray.
Look [over here|http://dvdstepbystep.com/break.php] has generally the same info and some links for things to look at.
and [this thread|http://discussions.apple.com/message.jspa?messageID=11256039#11256039]

[svn:bz-trunk] 20927: Didn't realize I also needed to modify SerialContext. java in addition to AbstractEndpoint. java to change the default max object nest level.

Revision: 20927
Revision: 20927
Author:   [email protected]
Date:     2011-03-20 11:48:41 -0700 (Sun, 20 Mar 2011)
Log Message:
Didn't realize I also needed to modify SerialContext.java in addition to AbstractEndpoint.java to change the default max object nest level. Change maxObjectNestLevel in SerializationContext.java to 512 to change the default max object nest level from 1024 to 512.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/SerializationContext.java

As the server.xml is big enough, I took the minimum portion of it. Hope u can proceed with it.

<Context path="" docBase="ROOT" debug="0"/>

<Context path="/xyz" docBase="pathTo_xyz" debug="0" crossContext="true"/>
<Context path="/pqr" docBase="pathTo_pqr" debug="0" crossContext="true"/>

<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
You should also provide a WEB-INF folder under pqr or xyz folder.
You should also provide a web.xml file under each WEB-INF folder.
The minimal web.xml is
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/j2ee/dtd/web-app_2_3.dtd">
<web-app>
</web-app>
That's it. Try it out. Hope it is OK.
Hafizur Rahman
SCJP

[svn:bz-4.0.0_fixes] 20928: Needed to change maxObjectNestLevel in SerializationContext. java to 512 to change the default max object nest level from 1024 to 512.

Revision: 20928
Revision: 20928
Author:   [email protected]
Date:     2011-03-21 07:02:01 -0700 (Mon, 21 Mar 2011)
Log Message:
Needed to change maxObjectNestLevel in SerializationContext.java to 512 to change the default max object nest level from 1024 to 512.
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java

Hi Diego,
i have a question.
i know that we need SRM 4.0 installation on WAS and ITS to be installed.
my question to you is....
do we need to install EBP separately if we have already installed SRM 4.0 ( in other words is EBP part of SRM 4.0 installation or is it separate)
and for ITS i am running WAS 6.4 and i know that ITS is an integral part of it so how do we activate ITS for SRM 4.0
Thanks a lot in advance
Harish

Table RequestUsage_Partition14 has 445538304 bytes that has exceeded the max bytes 442857142

Dear All,
Since last 4 weeks my SharePoint 2013 Farm facing Error in Event Ever such as "Table RequestUsage_Partition14 has 445538304 bytes that has exceeded the max bytes 442857142"
Kindly do let me know how we can resolve this issue.
Thanks in Advance.
Pravin Dhulap

Hi All,
I have updated the below script on our test Environment and i am not bale to see this error in Error log.
add-Pssnapin Microsoft.SharePoint.PowerShell
$UsageDefinition = Get-SPUsageDefinition -Identity "Page Requests"
$UsageDefinition.MaxTotalSizeInBytes = 21884901888
$UsageDefinition.Update()
and i have used smae script on PROD server but the i am still receiving same error.
Kindly let me know if there are any settings needs to be done or not??
Kindly provide the solution if anyone of you has it.
Thanks.
Pravin Dhulap

[svn:bz-trunk] 18928: fixing the sample service-config. xml for max-object-nest-level setting

Revision: 18928
Revision: 18928
Author:   [email protected]
Date:     2010-12-01 14:16:56 -0800 (Wed, 01 Dec 2010)
Log Message:
fixing the sample service-config.xml for max-object-nest-level setting
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

you have your driver jar in Tomcat\common\lib?
if so, check your classpath, it could be that.

Error while executing the Job for Objects :null Batch Risk Analysis

Hi All,
We've recently upgraded Virsa to version 5.3_14 . I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles. The job does not complete for some objects and it seems to be sporadic and shows this error: -
Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
I've attached the log for your review.
Thanks in advance for your help.
Linda Lewis
Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
WARNING: Job ID:395 : Failed to run Risk Analysis
java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)
at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job for Object(s) :ABROWN:null
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
INFO: --- BKG User Permission Analysis (System: P20:020) completed --- elapsed time: 4522 ms
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

Hi,
Was a solution found for this error?
Thanks,
Glen

Inactive sessions accumulate exceed the max session

Hi All,
once i checked the v$session, always find lots of inactive session.nearly after two month it will exceed the max session value in the init.ora profile.
I have check the sqlnet.ora profile and the value of expire_time is 10 minuter, while not sure why so many inactive session? and if i need to kill all inactive session?
Best Regards,
Chelsea

INACTIVE users are users not actively running a query, but they are connected to the database.
If SQL expire time is set, you can verify the logfiles, if users get disconnected because of idle connections.
For the remainder I agree with the other post.
Cheers
FJFranken

[svn:bz-3.x] 20876: Change default max object nest level to 512.

Revision: 20876
Revision: 20876
Author:   [email protected]
Date:     2011-03-16 09:02:36 -0700 (Wed, 16 Mar 2011)
Log Message:
Change default max object nest level to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Add documentation for the max object nest level setting.
Add documentation for the max collection nest level setting.
Checkintests: passed
Modified Paths:
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/resources/config/services-config.xml

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn:bz-4.0.0_fixes] 20874: Change default max object nest level to 512.

Revision: 20874
Revision: 20874
Author:   [email protected]
Date:     2011-03-16 06:55:37 -0700 (Wed, 16 Mar 2011)
Log Message:
Change default max object nest level to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Add documentation for the max object nest level setting.
Add documentation for the max collection nest level setting.
Remove max-string-length-bytes setting from the example services-config.xml as this setting doesn't exist.
Checkintests: passed
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/resources/config/services-config.xml

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Error while activating the business content object

Hi guru,
We have installed a new BI system, and hence we need to activate all the business content object as they are available in delivery version.
So as there was an requirement i tryed to activate the business content object ,that is 0mat (MATNR) material number,
but once done with the installation when i try to find the object and display it
that is i select the object 0mat , context menu and say display or change it does not show the complete screen as it appears for a characterstic and gives a error
"_settings for material number conversion not found"_*
so please help me out what is the problem
Thanks

Thanks Subash Balakrishnan for replying,
but let me inform you that i already did that as i need to install this object and now the object is showing with green instead of grey,
Now my problem is that after selecting grouping and collection when i go to infoobject menu under modelling and find out the object 0mat, it shows in green , but as i need to observe the properties of this object like data type , length etc , i select the object 0mat and right click and select display,
then instead of showing me the object properties screen it gives me the error as mentioned above,
so as you say it has to be in active versoin , but i can not view the normal screen which appears after creating any object ,
now i hope my problem is quiet explanatory so please help me.
Thanks

[BlazeDS]Error serialization exceeds the max collection object nest level of '15'.

Similar Messages

Maybe you are looking for