[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

Similar Messages

[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.

[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] 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.

[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] 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

[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.

[svn:bz-4.0.0_fixes] 20586: backporting nest object level fix and nest collection level fix from blazeds trunk to 4 .0.0.fixes branch

Revision: 20586
Revision: 20586
Author:   [email protected]
Date:     2011-03-03 13:44:51 -0800 (Thu, 03 Mar 2011)
Log Message:
backporting nest object level fix and nest collection level fix from blazeds trunk to 4.0.0.fixes branch
checkintests pass
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/Amf0Output.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/Amf3Output.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

Revision: 20586
Revision: 20586
Author:   [email protected]
Date:     2011-03-03 13:44:51 -0800 (Thu, 03 Mar 2011)
Log Message:
backporting nest object level fix and nest collection level fix from blazeds trunk to 4.0.0.fixes branch
checkintests pass
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/Amf0Output.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/Amf3Output.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

I need to change the default network name on my iMac

I recently changed routers and my iMac keeps trying to join the "default" net work as it did in the past. That is no longer working and I need to have the default changed to the name of the new network. It keeps trying for some time (meanwhile I am not connected to the internet) and eventually the computer finds the name of the new network that works and after a long wait it works.

Open System Preferences > Network > Wi-Fi (or AirPort) > Advanced, and remove your old network from the list of preferred networks. Your computer won't try to connect to the network anymore, and it will only connect to your new router

Need to cancel an auto renewal subscription but don't have the device. can i do it fron itunes.

need to cancel an auto renewal subscription but don't have the device. can i cancel from itunes?

Yes, see that topic of:
iTunes Store: Purchasing and managing auto-renewing subscriptions

[svn] 1543: Bug: BLZ-152-lcds custom Date serialization issue - need to add java.io. Externalizable as the first type tested in AMF writeObject() functions

Revision: 1543
Author: [email protected]
Date: 2008-05-02 15:32:59 -0700 (Fri, 02 May 2008)
Log Message:
Bug: BLZ-152-lcds custom Date serialization issue - need to add java.io.Externalizable as the first type tested in AMF writeObject() functions
QA: Yes - please check that the fix is working with AMF3 and AMFX and you can turn on/off the fix with the config option.
Doc: No
Checkintests: Pass
Details: The problem in this case was that MyDate.as was serialized to MyDate.java on the server but on the way back, MyDate.java was serialized back to Date.as. As the bug suggests, added an Externalizable check in AMF writeObject functions. However, I didn't do this for AMF0Output as AMF0 does not support Externalizable. To be on the safe side, I also added legacy-externalizable option which is false by default but when it's true, it restores the current behavior.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-152
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.ja va
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/amf/Amf3Output.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/amfx/AmfxOutput.java
blazeds/branches/3.0.x/resources/config/services-config.xml

[svn:bz-4.0.0_fixes] 22242: bug fix for watson 251328, backporting to 3. 1 branch from trunk

Revision: 22242
Revision: 22242
Author:   [email protected]
Date:     2011-08-26 07:41:45 -0700 (Fri, 26 Aug 2011)
Log Message:
bug fix for watson 251328, backporting to 3.1 branch from trunk
adding a getFlexClient(String id, boolean createIfNecessary) would be useful and the current getFlexClient(String id) can simply call getFlexClient(id, true).
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/client/FlexClientManager.jav a

awd_uk...
Using two pieces of software, a webpage and this walk-thru I was able to successfully put my old text messages onto the new iOS 5.0.
Can be found here >> https://discussions.apple.com/thread/3375277?start=90&tstart=0
Look for benhefron's post. It's magic.
Thanks again....
*SHiNK*

[svn:bz-4.0.0_fixes] 22605: backporting bug fix for 2956421 lexClient to expose EndpointQueue

Revision: 22605
Revision: 22605
Author:   [email protected]
Date:     2011-09-16 08:14:47 -0700 (Fri, 16 Sep 2011)
Log Message:
backporting bug fix for 2956421 lexClient to expose EndpointQueue
exposing a new API FlexClient.getEndpointQueue(String endpointQueueId)
checkintest not run
tests: YES
@watson: 2956421
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/client/FlexClient.java

[svn:bz-4.0.0_fixes] 16633: Merge fix from trunk

Revision: 16633
Revision: 16633
Author:   [email protected]
Date:     2010-06-23 07:55:57 -0700 (Wed, 23 Jun 2010)
Log Message:
Merge fix from trunk
Bugs: Watson #2632745 - Edge server to lcds server connection leak.
QA: Yes
Doc: No
Checkintests: Pass
Details: This is the BlazeDS part of the fix, there will be an LCDS part as well.
This wasn't an Edge Server bug per say, the real bug goes as follows:
-Take a messaging sample that uses RTMP.
-Connect and subscribe the Consumer to the destination.
-Get Message Generator stream messages to the destination.
-Close the browser window.
-At this point, you?\226?\128?\153d expect the FlexClient to time out (after 5 seconds if no FlexClient timeout is defined, or as specified by FlexClient timeout) which should time out the RTMPFlexSession. However, FlexClient does not time out because Message Generator is wrongly keeping the FlexClient alive as it?\226?\128?\153s pushing messages to it.
The bug is scattered across FlexClient.java class but mainly in FlexClient#push method. This method calls FlexClient#updateLastUse at the beginning of the method but what it should do is to delay FlexClient#updateLastUse until the message is actually written to the network (which won?\226?\128?\153t be the case when the browser window is closed, hence FlexClient will time out as expected).
This has an important side-effect for the Edge Server. When RTMP is in use, and there?\226?\128?\153s a stream of messages from Message Generator to a Flex client, when the browser window is closed, the connection between the Flex client and the Edge Server is cleaned up correctly, but the connection between the Edge Server and the backing App Server on behalf of the FlexClient stays open due to FlexClient not timing out, until the message streaming stops.
The fix is to not call FlexClient#updateLastUse right away in FlexClient#push, and delay it when we actually know that the message is written to the client.
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/client/FlexClient.java

[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.

Similar Messages

Maybe you are looking for