[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

Similar Messages

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

    Revision: 19214
    Revision: 19214
    Author:   [email protected]
    Date:     2010-12-09 07:31:35 -0800 (Thu, 09 Dec 2010)
    Log Message:
    BLZ-578 - potential race condition for class flex.messaging.MessageBroker
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: MessageBroker had a thread-local SystemSettings property in addition to regular SystemSettings property. This was due to MessageBroker#getSystemSettings static method that was called only once in the whole code tree. Once I removed the need for this static method, I could get rid of the thread-local SystemSettings property.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-578
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/FlexContext.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageException.java

  • [svn:bz-trunk] 9714: Bug: BLZ-424 - Incorrect user-agent string for Opera 10 in flex.messaging. client.UserAgentSettings

    Revision: 9714
    Author:   [email protected]
    Date:     2009-08-27 14:20:06 -0700 (Thu, 27 Aug 2009)
    Log Message:
    Bug: BLZ-424 - Incorrect user-agent string for Opera 10 in flex.messaging.client.UserAgentSettings
    QA: Yes
    Doc: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-424
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/client/UserAgentSettings.java
        blazeds/trunk/resources/config/services-config.xml

  • [svn:bz-trunk] 19216: Bug: Watson #2769398 - [Coverity] potential dead lock in flex.messaging.services.MessageService

    Revision: 19216
    Revision: 19216
    Author:   [email protected]
    Date:     2010-12-09 08:17:13 -0800 (Thu, 09 Dec 2010)
    Log Message:
    Bug: Watson #2769398 - potential dead lock in flex.messaging.services.MessageService
    QA: Yes
    Doc: No
    Details: allSubscriptions map was usually protected by allSubscriptionsLock but in SubscriptionManager#stop, it was protected by "this" lock instead which was inconsistent and useless in terms of thread safety and also produced the Coverity bug. Now, it's protected by allSubscriptionsLock in SubscriptionManager#stop as well.
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/services/messaging/SubscriptionManager.java

  • [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] 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] 9838: Bug: BLZ-416  - Can bypass checks for which channel and protocol a destination can be called over by using NetConnection instead of BlazeDS messaging .

    Revision: 9838
    Author:   [email protected]
    Date:     2009-08-31 11:27:50 -0700 (Mon, 31 Aug 2009)
    Log Message:
    Bug: BLZ-416  - Can bypass checks for which channel and protocol a destination can be called over by using NetConnection instead of BlazeDS messaging.
    QA: Yes
    Doc: Yes - note the new enforce-endpoint-validation setting.
    Details: Added the following config setting:
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-416
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationConstants.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
        blazeds/trunk/modules/core/src/flex/messaging/config/MessagingConfiguration.java
        blazeds/trunk/modules/core/src/flex/messaging/config/ServerConfigurationParser.java
        blazeds/trunk/modules/core/src/flex/messaging/config/SystemSettings.java

  • [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] 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] 14593: Bug: BLZ-495 - HTTP channel failed to deserialize Externalizable( ArrayCollection ) body in AsyncMessage.

    Revision: 14593
    Revision: 14593
    Author:   [email protected]
    Date:     2010-03-05 00:50:36 -0800 (Fri, 05 Mar 2010)
    Log Message:
    Bug: BLZ-495 - HTTP channel failed to deserialize Externalizable(ArrayCollection ) body in AsyncMessage.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: This regression was caused by change 12844 for BLZ-436. In that change, we assume that an ArrayList is always used temporarily but in ArrayCollection case (which is also an ArrayList), this is not the case, so we had to account for that.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-495
        http://bugs.adobe.com/jira/browse/BLZ-436
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/io/amfx/AmfxInput.java

  • [svn:bz-trunk] 16967: Bug: BLZ-549 - cyclic dependencies between core and remoting projects

    Revision: 16967
    Revision: 16967
    Author:   [email protected]
    Date:     2010-07-19 00:41:00 -0700 (Mon, 19 Jul 2010)
    Log Message:
    Bug: BLZ-549 - cyclic dependencies between core and remoting projects
    QA: Yes
    Doc: No
    Checkintess: Pass
    Details:
    -Removed the unnecessary dependency between core module tests and remoting module. Code module, including its tests, should not depend on any other module other than common module.
    -Remove blazeds-unittests project, instead added a test folder to blazeds-core project.
    -Fixed a minor bug in MessageDestination that I found during JUnit testing.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-549
    Modified Paths:
        blazeds/trunk/development/eclipse/projects/java/blazeds-core/.classpath
        blazeds/trunk/development/eclipse/projects/java/blazeds-core/.project
        blazeds/trunk/modules/core/src/flex/messaging/MessageDestination.java
        blazeds/trunk/modules/core/test/src/flex/messaging/DestinationTest.java
        blazeds/trunk/modules/core/test/src/flex/messaging/MessageBrokerTest.java
        blazeds/trunk/modules/core/test/src/flex/messaging/services/AbstractServiceTest.java
        blazeds/trunk/modules/core/test/src/flex/messaging/services/ServiceAdapterTest.java
    Removed Paths:
        blazeds/trunk/development/eclipse/projects/java/blazeds-unittests/.classpath
        blazeds/trunk/development/eclipse/projects/java/blazeds-unittests/.project

  • [svn:bz-trunk] 17839: Bug: BLZ-552 - AMFX should support Dictionary type

    Revision: 17839
    Revision: 17839
    Author:   [email protected]
    Date:     2010-09-24 08:05:57 -0700 (Fri, 24 Sep 2010)
    Log Message:
    Bug: BLZ-552 - AMFX should support Dictionary type
    QA: Yes
    Doc: Yes - document that the new Dictionary type is supported in AMFX (HTTPChannel) as well.
    Details: Added the new Dictionary type to AMFX. This is the server side of the fix, there'll be a client side (SDK) check-in shortly.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-552
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/io/amfx/AmfxInput.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amfx/AmfxOutput.java
        blazeds/trunk/modules/core/src/flex/messaging/io/amfx/AmfxTypes.java

  • [svn:bz-trunk] 8308: Bug: BLZ-311 - non-RFC 2109 compliant Cookies are ignored due to default HTTPClient CookiePolicy

    Revision: 8308
    Author:   [email protected]
    Date:     2009-06-26 08:26:58 -0700 (Fri, 26 Jun 2009)
    Log Message:
    Bug: BLZ-311 - non-RFC 2109 compliant Cookies are ignored due to default HTTPClient CookiePolicy
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: Added a cookie-policy configuration parameter to control the policy used by the HTTPClient in proxy service.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-311
    Modified Paths:
        blazeds/trunk/modules/proxy/src/flex/messaging/services/http/HTTPConnectionManagerSetting s.java
        blazeds/trunk/modules/proxy/src/flex/messaging/services/http/HTTPProxyAdapter.java
        blazeds/trunk/resources/config/proxy-config.xml

  • [svn:bz-trunk] 15090: Bug: BLZ-506 - Unexpanded {0} in error message from LocalFileResolver related to services .configuration.file

    Revision: 15090
    Revision: 15090
    Author:   [email protected]
    Date:     2010-03-29 01:55:44 -0700 (Mon, 29 Mar 2010)
    Log Message:
    Bug: BLZ-506 - Unexpanded in error message from LocalFileResolver related to services.configuration.file
    QA: No - I already tested.
    Doc: No
    Checkintests: Pass
    Details: Applied customer's patch.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-506
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/config/LocalFileResolver.java
        blazeds/trunk/modules/common/src/flex/messaging/errors.properties

    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] 13477: Bug: BLZ-455 - Document client-load-balancing property in the sample config

    Revision: 13477
    Revision: 13477
    Author:   [email protected]
    Date:     2010-01-13 05:17:10 -0800 (Wed, 13 Jan 2010)
    Log Message:
    Bug: BLZ-455 - Document client-load-balancing property in the sample config
    QA: No
    Doc: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-455
    Modified Paths:
        blazeds/trunk/resources/config/services-config.xml

Maybe you are looking for