[svn:bz-trunk] 16092: Bug: N/A

Revision: 16092
Revision: 16092
Author:   [email protected]
Date:     2010-05-13 06:31:33 -0700 (Thu, 13 May 2010)
Log Message:
Bug: N/A
QA: Yes
Doc: Yes
Checkintests: Pass
Details: Added some public APIs to FlexClient to make Servlet and NIO based session attribute sync a little more manageable. More specifically added getSessionAttribute, getSessionAttributeNames, setSessionAttribute, and removeSessionAttribute public APIs along with the private methods that support them.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

Similar Messages

  • [svn:bz-trunk] 15217: Bug: BLZ-508 - If server receives message for an unknown destination it shouldn ' t include the destination name in the error message sent back to the client .

    Revision: 15217
    Revision: 15217
    Author:   [email protected]
    Date:     2010-04-05 03:43:36 -0700 (Mon, 05 Apr 2010)
    Log Message:
    Bug: BLZ-508 - If server receives message for an unknown destination it shouldn't include the destination name in the error message sent back to the client.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: Changed the error message to not include destination id. I'm also checking in a few minor fixes I had locally.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-508
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/errors.properties
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
        blazeds/trunk/modules/core/src/flex/messaging/cluster/JGroupsCluster.java

    Thanx Mete, yeah i did...
    but i solved it some other way... not entirely sure this was
    it though as i was doing a lot of things at once...
    it was fds.swc... possibly it was out of date or missing.

  • [svn:bz-trunk] 17010: Bug: Watson #2652870 - use a property file to drive the custom configuration tokens as opposed to setting it in the command line

    Revision: 17010
    Revision: 17010
    Author:   [email protected]
    Date:     2010-07-22 02:52:41 -0700 (Thu, 22 Jul 2010)
    Log Message:
    Bug: Watson #2652870 - use a property file to drive the custom configuration tokens as opposed to setting it in the command line
    QA: Yes
    Doc: Yes - in custom tokens section, talk about the new token.file option
    Checkintests: Pass
    Details: Changed TokenReplacer to look for a token.file JVM option. If it's specified (eg. -Dtoken.file=/User/matamel/Desktop/token.properties), then TokenReplacer looks for a properties file where token name and values are specified. This allows someone to specify a file for custom tokens. Custom tokens can still be specified as straight JVM option and in case where a token is defined both as a JVM option and in a token properties file, JVM option takes precedence.
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/config/TokenReplacer.java

    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-trunk] 15163: Bug: BLZ-507 - JGroups 2.9. 0 GA not compatible with BlazeDS/LCDS

    Revision: 15163
    Revision: 15163
    Author:   [email protected]
    Date:     2010-03-31 06:31:12 -0700 (Wed, 31 Mar 2010)
    Log Message:
    Bug: BLZ-507 - JGroups 2.9.0 GA not compatible with BlazeDS/LCDS
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: Tweaked the clustering code to work with JGroups 2.9.0 while maintaining backwards compatibility with earlier versions of JGroups.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-507
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/cluster/ClusterNode.java
        blazeds/trunk/modules/core/src/flex/messaging/cluster/JGroupsCluster.java

  • [svn:bz-trunk] 16395: Bug: #2621264 [Regression] Small messages not working with NIO-HTTP endpoints in LCSD/trunk.

    Revision: 16395
    Revision: 16395
    Author:   [email protected]
    Date:     2010-06-02 05:00:56 -0700 (Wed, 02 Jun 2010)
    Log Message:
    Bug: #2621264 Small messages not working with NIO-HTTP endpoints in LCSD/trunk.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: This is the BlazeDS side of the fix. This wasn't a regression, it probably never worked correctly. So, in the scenario where there's a Producer and a Consumer, and Producer sends a message for the Consumer, there are 2 messages from the server. The ACK message for Producer's send, and the actual message Consumer receives. I found that the ACK message was in small form, but the actual message was not in streaming messages. This was because we never really tried to convert streamed messages into small messages before.
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/StreamingAMFEndpoint.java
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/StreamingHTTPEndpoint.java

  • [svn:bz-trunk] 18926: bug fix BLZ-570 Double linked list with lot of objects result in BlazeDS Error deserializing error  : StackOverflowError

    Revision: 18926
    Revision: 18926
    Author:   [email protected]
    Date:     2010-12-01 14:07:19 -0800 (Wed, 01 Dec 2010)
    Log Message:
    bug fix BLZ-570 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
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/errors.properties
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.java
        blazeds/trunk/modules/core/src/flex/messaging/io/SerializationContext.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf0Input.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/AmfIO.java

  • [svn:bz-trunk] 8910: Bug: LCDS-936 - Should have better error message in servlet log if server in services-config .xml is configured to use wrong class.

    Revision: 8910
    Author:   [email protected]
    Date:     2009-07-29 14:22:26 -0700 (Wed, 29 Jul 2009)
    Log Message:
    Bug: LCDS-936 - Should have better error message in servlet log if server in services-config.xml is configured to use wrong class.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/LCDS-936
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java

    After many hard working days.i finally found the error cause,i needed to make weblogic datasource also ADF doesnt work on internet explorer browser,it works on safary.hope it helps somebody

  • [svn:bz-trunk] 21394: bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX .

    Revision: 21394
    Revision: 21394
    Author:   [email protected]
    Date:     2011-06-16 12:34:13 -0700 (Thu, 16 Jun 2011)
    Log Message:
    bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX.
    get the sessions id before we invalidate the duplicate session.
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

    For our profect I think this issue was caused as follows:
    Believing that remoting was full asynchronous we fired a 2 or 3 remote calls to the server at the same time ( within the same function ) - usually when the users goes to a new section of the app.
    This seemed to trigger the duplicate http session error since according to http://blogs.adobe.com/lin/2011/05/duplication-session-error.html  two remote calls arriving before a session is created will cause 2 sessions to be created.
    Our current solution ( too early to say it works ) is to daisy chain the multiple calls together .
    Also there seemed to be an issue where mobile apps that never quit ( thanks Apple! )  caused the error when activated after a few hours.
    I guess the session expires on the server and the error above occurs on activation.
    So the mobile apps now ping the server with a remote call when activated after sleeping for more than one hour.
    All duplicate http errors are silently caught and reported.
    Fingers crossed we won't get any more!

  • [svn:bz-trunk] 13746: Bug: LCDS-952

    Revision: 13746
    Revision: 13746
    Author:   [email protected]
    Date:     2010-01-25 07:44:49 -0800 (Mon, 25 Jan 2010)
    Log Message:
    Bug: LCDS-952
    QA: Yes - please make sure that:
    -This change didn't cause any regressions. Last time, it caused some issues but we don't seem to remember what they were.
    -Make sure the max limit is being enforced and the JVM option to change it actually works.
    Doc: Yes, might want to document about default max string length of 25MB and the JVM option to change it.
    Checkintests: Pass
    Details: Limited maximum incoming string length to 25MB by default. Also provided a JVM option called max-string-bytes that one can use to change this limit (using -Dmax-string-bytes=1000 for example).
    Ticket Links:
        http://bugs.adobe.com/jira/browse/LCDS-952
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/errors.properties
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf0Input.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java

  • [svn:bz-trunk] 8731: Bug: BLZ-251 - Destination.stop() and Service.stop() don't seem to do anything

    Revision: 8731
    Author:   [email protected]
    Date:     2009-07-22 07:08:20 -0700 (Wed, 22 Jul 2009)
    Log Message:
    Bug: BLZ-251 - Destination.stop() and Service.stop() don't seem to do anything
    QA: Yes
    Doc: No
    Details: Reintroduced the change 7370 that fixed this problem but broke the LCDS Edge server; there will be another check-in in the LCDS branch to make sure this fix doesn't break the Edge server again.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-251
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java

    Hi Ingrid
    Thanks a lot for the response.
    That parameter is right now set to "0".
    But on reading the documentation for that parameter, it says you should change it only if SAP recommends you to do so.
    We checked in our other systems as well and all that is set to "0" as well.
    Will that be Ok to change the parameter to a different value?
    If yes, what is the value to be used?
    Thanks a lot

  • [svn:bz-trunk] 10570: Bug: BLZ-428 - pinging endpoint Returns a HTTP: Status 200 in ie8

    Revision: 10570
    Author:   [email protected]
    Date:     2009-09-24 07:53:33 -0700 (Thu, 24 Sep 2009)
    Log Message:
    Bug: BLZ-428 - pinging endpoint Returns a HTTP: Status 200 in ie8
    QA: Yes - please make sure IE8 works with AMF.
    Doc: No
    Details: AMF does not work all the time in IE8 due to some IE8 and/or Flash Player bug. Setting the Content-Type in HTTP responses to text seem to resolve the issue. We're adding a temporary solution to change the Content-Type when IE8 is being used. This is not on by default though, user has to opt-in with this configuration option in channel definiton:
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-428
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

  • [svn:bz-trunk] 21111: Bug: BLZ-578 - [Coverity] potential race condition for class flex.messaging.MessageBroker

    Revision: 21111
    Revision: 21111
    Author:   [email protected]
    Date:     2011-04-21 06:12:37 -0700 (Thu, 21 Apr 2011)
    Log Message:
    Bug: BLZ-578 - potential race condition for class flex.messaging.MessageBroker
    QA: Yes
    Doc: No
    Details: The bug was fixed by change 19598 already, but also adding a minor fix to not call setSystemSettings in initThreadLocal method becuase there are no thread local variables in MessageBroker anymore.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-578
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java

  • [svn:bz-trunk] 21494: bug fix BLZ-581 Possible deadlock situation when sending message

    Revision: 21494
    Revision: 21494
    Author:   [email protected]
    Date:     2011-06-29 11:25:54 -0700 (Wed, 29 Jun 2011)
    Log Message:
    bug fix BLZ-581 Possible deadlock situation when sending message
    change the scope of lock EndpointPushNotifier.pushNeeded to be minimal (retrieving the messages from the message buffer), that way, we can avoid the connection write failure to occupy the lock forever.
    Checkintests pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-581
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java

    Adobe has donated BlazeDS to the Apache Flex community, and the source code is hosted on the Apache Flex website in a GIT repository.
    http://flex.apache.org/dev-sourcecode.html

  • [svn:bz-trunk] 21209: bug fix BLZ-581 Possible deadlock situation when sending message

    Revision: 21209
    Revision: 21209
    Author:   [email protected]
    Date:     2011-05-04 18:26:18 -0700 (Wed, 04 May 2011)
    Log Message:
    bug fix BLZ-581 Possible deadlock situation when sending message
    change the scope of lock EndpointPushNotifier.pushNeeded to be minimal (retrieving the messages from the message buffer), that way, we can avoid the connection write failure to occupy the lock forever.
    Checkintests pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-581
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java

    Adobe has donated BlazeDS to the Apache Flex community, and the source code is hosted on the Apache Flex website in a GIT repository.
    http://flex.apache.org/dev-sourcecode.html

  • [svn:bz-trunk] 13685: Bug: Some checkintests on Mac are failing.

    Revision: 13685
    Revision: 13685
    Author:   [email protected]
    Date:     2010-01-21 05:19:59 -0800 (Thu, 21 Jan 2010)
    Log Message:
    Bug: Some checkintests on Mac are failing.
    QA: Yes
    Doc: No
    Details: Changed the port of bad-http channel in ConfigurationBasedTestCase, so checkintests work more consistently on Mac, on Mac port 88 is used by some process, thanks to John for figuring this out. With this change, checkintests on Mac are more consistent but there are 2 tests that are still intermittently failing.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/flexunit/src/mx/messaging/tests/ChannelSetTes t.as
        blazeds/trunk/qa/apps/qa-regress/testsuites/flexunit/src/mx/messaging/tests/Configuration BasedTestCase.as
        blazeds/trunk/qa/apps/qa-regress/testsuites/flexunit/src/mx/messaging/tests/ConsumerWithS erverTest.as

    I removed the src/ directory and ran makepkg and it succeeded. Pacman -U kernel.pkg.tar.gz also worked. Now all that's left is rebooting and trying.
    Thanks everyone.
    OK, I guess it's not over yet. I rebooted in the new kernel, but it says it can't find /dev/sda3 (which is my / partition).
    This is my grub entry:
    title Arch Linux Gigamo
    root (hd0,2)
    kernel /boot/vmlinuz26 root=/dev/sda3 ro
    initrd /boot/kernel26-gigamo.img
    Okay well, I didnt realise there was a vmlinux26-gigamo as well. Will see if that fixes it.
    Last edited by Gigamo (2008-03-12 16:53:22)

Maybe you are looking for