[svn:bz-trunk] 14546: Bug: LCDS-1477 - Deadlocks detected by Coverity.

Revision: 14546
Revision: 14546
Author:   [email protected]
Date:     2010-03-03 05:52:54 -0800 (Wed, 03 Mar 2010)
Log Message:
Bug: LCDS-1477 - Deadlocks detected by Coverity.
QA: Yes
Doc: No
Checkintess: Pass
Detailed: Changed outboundQueues to ConcurrentHashMap so we can avoid sync blocks around it. This should get rid of most of the Coverity deadlock issues reported in the bug.
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-1477
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

Similar Messages

  • [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] 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:fx-trunk] 14719: Bug: LCDS-1522 - RTE running reliable messaging test over NIO HTTP endpoint caused by checkin 272187 .

    Revision: 14719
    Revision: 14719
    Author:   [email protected]
    Date:     2010-03-12 02:20:41 -0800 (Fri, 12 Mar 2010)
    Log Message:
    Bug: LCDS-1522 - RTE running reliable messaging test over NIO HTTP endpoint caused by checkin 272187.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: Checkin 272187 fixed small messages to work on NIO HTTP endpoints but this exposed a bug in HTTPChannel. HTTPChannel is not supposed to support small messaging feature but there was one place where small messages feature were still being enabled which caused the bug.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/LCDS-1522
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/channels/HTTPChannel.as

  • [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] 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:fx-trunk] 21141: Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors .

    Revision: 21141
    Revision: 21141
    Author:   [email protected]
    Date:     2011-04-26 06:40:39 -0700 (Tue, 26 Apr 2011)
    Log Message:
    Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: When a logout was followed by an immediate login, sometimes the server would throw duplicate session detected errors. This was because when logout happened, a fire-and-forget disconnect message was sent to the server that established a new session, and if the subsequent login happened before disconnect ACK returned from the server, that would establish another session and hence the error. The fix is to insert a slight delay between disconnect and ResultEvent dispatching. This way, disconnect has a chance to return before a login is performed.
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

    You've got an  incompatible Logitech driver and java was incompletely uninstalled.
    You may have a problem with the Wacom driver.
    I don't know if fixing those things will help.
    There also a few window server errors, but I don't know if they are causal.
    If you can note the time of the hangs, that might help narrow it down in the logs.

  • [svn:bz-trunk] 18873: Bug fix Watson 2724938 [Coverity] potential deadlock in flex.messaging.client.FlexClient

    Revision: 18873
    Revision: 18873
    Author:   [email protected]
    Date:     2010-11-30 12:22:15 -0800 (Tue, 30 Nov 2010)
    Log Message:
    Bug fix Watson 2724938 potential deadlock in flex.messaging.client.FlexClient
            Maintain the pattern of using the FlexClient.lock and ensure that order of locks should always start with the FlexClient.lock.  This is critical to prevent deadlock cases,
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

  • [svn:bz-trunk] 19119: bug fix BLZ-598  [Coverity] potential deadlock in FlexClient

    Revision: 19119
    Revision: 19119
    Author:   [email protected]
    Date:     2010-12-07 13:55:34 -0800 (Tue, 07 Dec 2010)
    Log Message:
    bug fix BLZ-598  potential deadlock in FlexClient
    adding the synchronization in the time out routine to acquir the FlexClient instance level lock first.
    Checkintests pass
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-598
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.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] 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] 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] 8964: Fix LCDS-953 - Add a last ditch catch block to the service() function to avoid any possibility or leaking exception info.

    Revision: 8964
    Author:   [email protected]
    Date:     2009-07-31 12:07:09 -0700 (Fri, 31 Jul 2009)
    Log Message:
    Fix LCDS-953 - Add a last ditch catch block to the service() function to avoid any possibility or leaking exception info.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/LCDS-953
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.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-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.

Maybe you are looking for

  • Will actionListener work in 1.4?

    I have the following code written in 1.2.2. It works fine. But when I tried this in 1.4.1, it is not working. This is where the user enter the userid and password and push the "Login" button. class SISHandler implements ActionListener public void act

  • IPhoto Calender - pictures

    I'm having trouble figuring out how to drag pictures from iPhoto albums into Calender and cannot find anyting on the Apple site that explains how to do that. Can anyone help? Thanks, Walter

  • User exit used

    Hi, what is the user exit used and what is the requirement. Thi s was a ninterview question . What would be the best answer

  • Sony update engine could not be installed

    Recently i bought a xperia z1 and because of some issues wanted to repair the software through pc companion as the update service is no longer available.But i can not repair my phone cause every time a error message is popping up by saying update eng

  • Windows 8.1 safe mode password doesn't work

    Using HP Pavilion 23 all in one model 23-b037c, 2012 windows 8.1. During testing for internet connectivity was instructed to initiate msconfig and reboot in Safe Mode. After rebooting the sign in security screen asked for my password.  I entered my p