[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

Similar Messages

  • [svn:bz-trunk] 21151: bug fix watson 2769398 [Coverity] potential dead lock in flex.messaging.services.MessageService

    Revision: 21151
    Revision: 21151
    Author:   [email protected]
    Date:     2011-04-26 12:14:04 -0700 (Tue, 26 Apr 2011)
    Log Message:
    bug fix watson 2769398 potential dead lock in flex.messaging.services.MessageService
    override the AbstractService.stop in MessageService to obtain subscribeLock when stopping
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/services/MessageService.java

  • [svn:bz-trunk] 21043: bug fix watson 2769398 [Coverity] potential dead lock in flex.messaging.service

    Revision: 21043
    Revision: 21043
    Author:   [email protected]
    Date:     2011-04-07 12:41:36 -0700 (Thu, 07 Apr 2011)
    Log Message:
    bug fix watson 2769398 potential dead lock in flex.messaging.service
    fix the order of locking of MessageService.subscribeLock, FlexClient.objectLock, requires that routing message to client roution obtain the subscribeLock first
    checkin test pass done
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/services/MessageService.java

  • [svn:bz-trunk] 18839: bug fix BLZ-575 Potential race condition in flex. management.runtime.messaging.endpoints.EndpointControl

    Revision: 18839
    Revision: 18839
    Author:   [email protected]
    Date:     2010-11-29 12:26:32 -0800 (Mon, 29 Nov 2010)
    Log Message:
    bug fix BLZ-575 Potential race condition in flex.management.runtime.messaging.endpoints.EndpointControl
    Change a few counters to Atomic numbers
    Probably solve some PMD bugs too (was complaining about new Integer() and new Long() API)
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-575
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/management/runtime/messaging/endpoints/EndpointContro l.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] 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] 20505: Bug: Watson #2818669 - AbstractAmfInput uses System. getProperty in Constructor leading to AccessControlException when using in Applet

    Revision: 20505
    Revision: 20505
    Author:   [email protected]
    Date:     2011-03-01 07:31:55 -0800 (Tue, 01 Mar 2011)
    Log Message:
    Bug: Watson #2818669 - AbstractAmfInput uses System.getProperty in Constructor leading to AccessControlException when using in Applet
    QA: Yes
    Doc: No
    Checkintests: Didn't run - the change was to wrap the System.getProperty in a try/catch that would have caused the SecurityException, so no real functionality change that could affect the check-in tests.
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.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] 17133: this time finally (and hopefully) adding all the flex-messaging-opt tomcat/jrun/oracle/weblogic/ websphere servers maven pom files in the right svn folder.

    Revision: 17133
    Revision: 17133
    Author:   [email protected]
    Date:     2010-07-30 02:01:44 -0700 (Fri, 30 Jul 2010)
    Log Message:
    this time finally (and hopefully) adding all the flex-messaging-opt tomcat/jrun/oracle/weblogic/websphere servers maven pom files in the right svn folder.
    Added Paths:
        blazeds/trunk/modules/opt/poms/oracle/
        blazeds/trunk/modules/opt/poms/oracle/pom.xml
        blazeds/trunk/modules/opt/poms/tomcat4/
        blazeds/trunk/modules/opt/poms/tomcat4/pom.xml
        blazeds/trunk/modules/opt/poms/tomcat6/
        blazeds/trunk/modules/opt/poms/tomcat6/pom.xml
        blazeds/trunk/modules/opt/poms/weblogic/
        blazeds/trunk/modules/opt/poms/weblogic/pom.xml
        blazeds/trunk/modules/opt/poms/websphere/
        blazeds/trunk/modules/opt/poms/websphere/pom.xml

  • [svn:bz-trunk] 18858: bug fix watson 2724936

    Revision: 18858
    Revision: 18858
    Author:   [email protected]
    Date:     2010-11-30 08:35:41 -0800 (Tue, 30 Nov 2010)
    Log Message:
    bug fix watson 2724936
    potential dead lock in flex.messaging.services.MessageService
    Fixing the order of acquiring locks to break the cycle of deadlock.
    Adding messageClient shutdowning check too
    Checkintests passed
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/MessageClient.java
        blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.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] 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] 20981: bug fix BLZ-426 fixing the response cookie logic to skip request cookies

    Revision: 20981
    Revision: 20981
    Author:   [email protected]
    Date:     2011-03-28 14:28:45 -0700 (Mon, 28 Mar 2011)
    Log Message:
    bug fix BLZ-426 fixing the response cookie logic to skip request cookies
    checkintests pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-426
    Modified Paths:
        blazeds/trunk/modules/proxy/src/flex/messaging/services/http/proxy/ProxyContext.java
        blazeds/trunk/modules/proxy/src/flex/messaging/services/http/proxy/RequestFilter.java
        blazeds/trunk/modules/proxy/src/flex/messaging/services/http/proxy/ResponseFilter.java

  • [svn:bz-trunk] 17982: Bug: BLZ-564 - Some classes in flex-messaging-core. jar define main methods for debugging purposes.

    Revision: 17982
    Revision: 17982
    Author:   [email protected]
    Date:     2010-10-01 00:39:15 -0700 (Fri, 01 Oct 2010)
    Log Message:
    Bug: BLZ-564 - Some classes in flex-messaging-core.jar define main methods for debugging purposes. This creates an unintended entry point and the main methods should be removed.
    QA: No - just removed main methods
    Doc: No
    Checkintests: No - just removed main methods
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-564
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/services/messaging/selector/NumericValue.ja va
        blazeds/trunk/modules/core/src/flex/messaging/util/Base64.java
        blazeds/trunk/modules/core/src/flex/messaging/util/Hex.java
    Added Paths:
        blazeds/trunk/modules/core/test/src/flex/messaging/util/Basae64Test.java

Maybe you are looking for

  • Video - Play In iTunes Then Won't Sync

    I've just noticed that if I play a video in iTunes it will then no longer sync with the iPod. iTunes says its not a compatible format. I've just tested playing a video on the iPod (OK) then playing on Mac iTunes (OK) then resyncing. The video no long

  • Itunes wont download on new pc

    just bought a new pc. tried to download iTunes, it said it was downloaded but it isn't anywhere on my pc. tried it again and the same thing happened. how do u download iTunes?????

  • F110-payment has been carried out

    Hi , After making the payment, status is showing as payment has been carried out........what may be the reasons for this. Regards, Dharani

  • Troubles importing and linking media in CS5.5

    I am using CS5.5 and having trouble importing media. Importing .mpg or .VOB files (~30mins length, 1GB size) and both cause Prem to hang and not respond. I can leave it for half an hour and still no progress. However, when using a different computer,

  • Error 200302 in DAQ-mx global virtual channels when reading 0Hz

    Hello, I am attempting to calculate flowrate via frequency (by counting the pulses for a given time). The frequency read seems fine when the operation is running. However, when there is no flow (only tested by reading the channel with the operation o