Dequeue a delayed message

How do I dequeue a delayed message (in wait state) with specific correlation ID?
Does JMS API provide this call or I have to go to Oracle Java API?
thanks,
- David

david,
generally when u fire Deequeue command it will deeq. all the messages which r new. i do remember @ wait state but i don't think there is Force action API is there or atleast i m not aware .
Mandar

Similar Messages

  • Dequeue with delay

    Folks,
    One more question about dequeue with delay. I read in the AQ docs, that if a message is dequeued by specifying message ID, it is dequeued irrespective of whether or not it has a delay set on it.
    This is the code that I use to dequeue
    receiver = session.createReceiver("queueName", "JMSCorrelationID='ID:<msg-id-col-in-db>");
    message = (TextMessage) receiver.receiveNoWait();
    However, this returns null. What am I doing wrong here? I'd really appreciate any help.
    Thanks,
    Darshan

    It works now with this workaround from Oracle Team
    We do have a temporary workaround is to disable the new 11.2 dequeue functionality via
    connect / as sysdba
    alter system set event='10852 trace name context forever, level 16384'
    scope=spfile;
    shutdown immediate;
    startup;

  • How can I Dequeue a Single Message

    Is it possible to use BPEL to dequeue just a SINGLE message from an MQ - as an activity in a process flow?
    It seems that the "Receive" activity drains a queue, and is meant to be used at the beginning of a BPEL process (to kick off a new instance). I'm just trying to dequeue a single message from a specified queue, and access its payload.
    Please let me know if this is possible.
    Thanks very much.

    Consider a scenario where there exists an MQ that contains messages that represent a unit of work. This MQ is populated with messages from an external C++ process that generates these units of work.
    I would like to create a BPEL service that can be invoked by a user as a web service. As a part of that process, I would like to dequeue one message (one unit of work from this MQ), to assign to the user. Portions of this message would be mapped to XML elements in the service response.
    As a whole, the BPEL process is responsible for performing several other activities (logging work assignment in the database for future reporting, sending email confirmations to the requesting user, etc.). I really appreciate what BPEL offers in terms of the overall orchestration of this process - but I'm wondering if this inability to dequeue a single message is a limitation of the adapters that are offered, or a misunderstanding on my part.
    I'm sure I could achieve the same result by embedding some Java code in the process, that would connect to this MQ and dequeue a single message - but would prefer to use an adapter (if possible).
    Thanks for the help!

  • Delayed messages problem!

    Hello there, i'm from malaysian , and i'm a iPhone user, i has some issue with my skype, where i always get a delay messages. Sometimes, take a two days to get messages from my friends, or group! Idk what problem, has any idea to solving this issue ?

    I'm having the same/smilar issue. not sure why. usually ihave to type , or somethign to force it to update. usually i get an alert but it won't show up in my list until i do as stated.

  • Dequeue a text message

    Hello everyone,
    DB version : 11.2.0.1.0
    I'm able to add a text message on an AQ queue, but I'm not able to dequeue it from java.
    When I run the dequeue method, it waits ... it doesn't get any message in, even if new messages are being put on the queue.
    What am I missing ?
    Creation of the AQ queue:
    EXEC DBMS_AQADM.STOP_QUEUE('textmessage_queue');
    EXEC DBMS_AQADM.DROP_QUEUE('textmessage_queue');
    EXEC DBMS_AQADM.DROP_QUEUE_TABLE('queue_textmessage_table');
    EXEC DBMS_AQADM.CREATE_QUEUE_TABLE (queue_table => 'queue_textmessage_table', queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers => false);
    EXEC DBMS_AQADM.CREATE_QUEUE (queue_name => 'textmessage_queue', queue_table => 'queue_textmessage_table');
    EXEC DBMS_AQADM.START_QUEUE (queue_name => 'textmessage_queue');The createJMSClient(); used by the enqueue and dequeue methods
        private JMSTopic createJMSClient() {
            JMSTopic aq = new JMSTopic();
            try {
                TopicConnectionFactory topicConnectionFactory = null;
                // Get topic connection factory
                Properties info = new Properties();
                info.put(userName, userPassword);
                topicConnectionFactory = AQjmsFactory.getTopicConnectionFactory(connectString, info);
                // Creates an AQ topic connection and session
                aq.connection = topicConnectionFactory.createTopicConnection(userName, userPassword);
                // If a session is transacted, message acknowledgment is handled automatically
                //   by commit and recovery is handled automatically by rollback
                aq.session = aq.connection.createTopicSession(true, // Session is transacted
                            Session.CLIENT_ACKNOWLEDGE); // Acknowledges by commit and rollback
                System.out.println("Successfully created AQ session");
            } catch (Exception ex) {
                System.err.println("AQApplication.createJMS(): " + ex.getMessage());
                System.err.println("user = " + userName + ", password = " + userPassword + ", destination = " +
                                   connectString);
                ex.printStackTrace();
            return aq;
        }Java code to enqueue a text message
            JMSTopic client = myMessage.createJMSClient();
            AQjmsSession aqjmssession = (AQjmsSession) client.session;
            AQjmsDestination destination = (AQjmsDestination)aqjmssession.getQueue(myMessage.DB_AQ_ADMIN_NAME, "textmessage_queue");
            TextMessage createTextMessage = aqjmssession.createTextMessage("This is my first text message");
            MessageProducer producer = aqjmssession.createProducer(destination);
            producer.send(createTextMessage);
            aqjmssession.commit();Java code to dequeue a text message
            JMSTopic client = myMessage.createJMSClient();
            AQjmsSession aqjmssession = (AQjmsSession)client.session;
            AQjmsDestination destination =
                (AQjmsDestination)aqjmssession.getQueue(myMessage.DB_AQ_ADMIN_NAME, "textmessage_queue");
            MessageConsumer consumer = client.session.createConsumer(destination);
            System.out.println("Waiting for a message ...");
            Message message = consumer.receive();
            System.out.println("Message received !!");

    You have to start the connection (aq.connection) to receive the message. This is not required for enqueue, but required for dequeue.

  • Enqueue and Dequeue of BLOB messages

    Hi all,
    Does anyone have any experience with enqueue and dequeue of BLOB messages? I have PDF files that I would like to send via aq. I can enqueue them, but not dequeue them. When I attempt to deque, I get the following error:
    ORA-25236: buffer too small for user data
    Here is my enqueue code:
    set serveroutput on size 1000000
    set timing on
    /* Enqueue to msg_queue: */
    DECLARE
       Enqueue_options     DBMS_AQ.enqueue_options_t;
       Message_properties  DBMS_AQ.message_properties_t;
       Message_handle      RAW(16);
       Message             blob;
         TmpMsg              blob := empty_blob;
         cnt                 number;
    BEGIN
       DBMS_AQ.ENQUEUE(queue_name => 'JOOSTENBERGVLAKTE',
       Enqueue_options            => enqueue_options,
       Message_properties         => message_properties,
       Payload                    => tmpmsg,
       Msgid                      => message_handle);
         select t.user_data into message from test_queue t where t.msgid = message_handle;
         select blob_content into tmpmsg from tbl;
         cnt := length(message) + 1;
         dbms_lob.erase(message, cnt);
         dbms_lob.trim(message, 0);
         dbms_lob.append(message, tmpmsg);
         dbms_output.put_line('Erased ' || cnt || ' characters');
         dbms_output.put_line('Message length ' || length(message));
       COMMIT;
    END;
    /And here is my deque code:
    set serveroutput on 1000000;
    declare
         l_options         dbms_aq.dequeue_options_t;
         l_properties      dbms_aq.message_properties_t;
         l_hnd             RAW(16);
         l_msg             blob := empty_blob;
    begin
         dbms_aq.dequeue(
              queue_name => 'JOOSTENBERGVLAKTE',
              dequeue_options => l_options,
              message_properties => l_properties,
              payload => l_msg,
              msgid => l_hnd
         commit;
    exception
         when others then
              rollback;
              raise;
    end;
    /

    Hi,
    I think you have the order of enqueueing and filling your blob in the wrong order. I understand why you do it, because inserting a blob in the table you could do that in this way. But I think that you should fill and close your blob before enqueueing it.
    Try something like:
    l_attachment blob;-- := :p_attachment;
    begin
    dbms_lob.createtemporary(l_attachment, false);
    dbms_lob.write( lob_loc => l_attachment
    , amount => length(:p_attachment)
    , offset => 1
    , buffer => utl_raw.cast_to_raw(:p_attachment));
    Another small remark is that I see you doing a commit right after the enqueue-dequeue. In your enqueu example it seems to make sense because you try to fill the blob afterwards. But you could also use the enqueue-dequeue option "visibility" and set that on dbms_aq.immediate. Then you don't have to do a commit. This is handy for enqueueing messages with out affecting your transaction.
    Regards,
    Martien

  • Stopping delayed messages from going out

    I previous versions of GroupWise including current version 8, a user
    couldn't retract a delayed message even though it was sitting in the
    GWIA\GWHOLD directory. Has it been fixed that users can retract a
    delayed message that is queue in GWIA? As per TID 3800546
    http://www.novell.com/support/viewCo...800546&sliceId
    =1
    none of my clients are ready for the jump just yet to this version, but
    this has been an issue for one that is likely to make the jump in the
    summer which should be after the gamma testing period is over. I might
    then be able to entice him to go sooner
    Andy Konecny
    KonecnyConsulting.ca in Toronto
    Andy's Profile: http://forums.novell.com/member.php?userid=75037

    On 12/21/2011 9:17 AM, Andy Konecny wrote:
    > I previous versions of GroupWise including current version 8, a user
    > couldn't retract a delayed message even though it was sitting in the
    > GWIA\GWHOLD directory. Has it been fixed that users can retract a
    > delayed message that is queue in GWIA? As per TID 3800546
    > http://www.novell.com/support/viewCo...800546&sliceId
    > =1
    >
    > none of my clients are ready for the jump just yet to this version, but
    > this has been an issue for one that is likely to make the jump in the
    > summer which should be after the gamma testing period is over. I might
    > then be able to entice him to go sooner
    >
    >
    > Andy Konecny
    > KonecnyConsulting.ca in Toronto
    > -----------------------------------------------------------------------
    > Andy's Profile: http://forums.novell.com/member.php?userid=75037
    >
    >
    Nope. Once something hits GWIA, it's no longer under GW control. I don't
    see that changing.

  • Dequeue Condition for Message Payload

    Hi experts ,
    My requirement is that :I have 2 Composites in my Application which are going to listen same Aqueue but I want
    SubComposite1 to dequeue only message where "LocalName" is "Create" .
    SubComposite2 to dequeue only message where "LocalName" is "Update" .
    Example of message :
    <msg_out:FusionXFamilyEvent xmlns:msg_out="http://xmlns.oracle.com/apps/common/acr/events">
    <msg_out:Namespace>/entity/events/edl/OrganizationEO</msg_out:Namespace>
    <msg_out:LocalName>Create</msg_out:LocalName>
    <msg_out:Payload>
    </msg_out:Payload>
    </msg_out:FusionXFamilyEvent>
    In DequeueAdapter (AqAdapter),I have added this condition ,but its not working .
    <activation-spec className="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec">
    <property name="DequeueCondition" value="LocalName='Create'"/>
    <property name="Consumer" value="Sample"/>
    <property name="QueueName" value="ACR_XFAMILY_EVENT_Q"/>
    </activation-spec>
    please help me in this solution

    Hello,
    As you have discovered by default both dequeueing via a condition and dequeue via a correlation identifier have never honoured the sort order of the queue table.
    You can get it to honour the sort order by setting the following event at the session or system level or in the spfile/pfile as follows
    alter session set events '10866 trace name context forever, level 1';
    or
    alter system set events '10866 trace name context forever, level 1';
    or
    alter system set event='10866 trace name context forever, level 1' scope=spfile;
    Once this is set and a dequeue condition is being used an extra order by based on the sort columns of the queue table will be added to the sql which is executed internally.
    So this could have an impact on the dequeue performance when using a deq_condition or dequeueing via correlation id but ultimately you will have the ordering you require.
    Thanks
    Peter

  • Re enable dequeueing for expired messages in AQ

    Dear all,
    I need to reprocess expired messages in an advanced queue.
    Is there a script that allows either to retry dequeuing or to re insert/enqueue again the messages?
    The creation script of the queue follows:
    BEGIN
      SYS.DBMS_AQADM.CREATE_QUEUE
        QUEUE_NAME          =>   'CC.PMTS'
       ,QUEUE_TABLE         =>   'CC.PMTS_DATA'
       ,QUEUE_TYPE          =>   SYS.DBMS_AQADM.NORMAL_QUEUE
       ,MAX_RETRIES         =>   0
       ,RETRY_DELAY         =>   0
       ,RETENTION_TIME      =>   0
       ,COMMENT             =>   'Comment'
    END;
    Thanks

    There is another forurm for AQ queries: https://forums.oracle.com/community/developer/english/oracle_database/advanced_queueing

  • Delay message processing until after a given datetime?

    Using Service Broker, is it possible to delay a given message from being processed until some future date/time has gone by?
    scott

    Depends on what you want to achieve, but maybe you can use a conversation timer? BEGIN CONVERSATION TIMER sets up a timeout that produces a message on the local queue in the given time frame.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Delayed messages

    I recently bought the blackberry z10. I am not able to receive my emails and watsapp messages in real time. They only get delivered after some time say two hours. The email account is set to receive push message. My network carrier is Vodafone India. Also my phone and app are updated to latest versions. Kindly . thanking you

    Have you seen any improvement?
    Actually, we have not. However, it appears that this is a problem with 1 user sending to 1 domain. If i am reading this right, this issue appears to be from the sending domain? Here is a snippet from the delayed email message:
    Generating server: our.exchange.server
    Receiving server: sending.to.domain (public ip)
    user on sending to domain
    Remote Server at sending.to.domain (public ip) returned '400 4.4.7 Message delayed'
    3/3/2014 8:26:54 PM - Remote Server at sending.to.domain (public ip) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10061, Win32 error code: 10061." Attempted failover to alternate
    host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was sending to domain public ip:25'

  • No "Short delay" message = slow workflow

    Prior to this round of changes, we got the now-familar "Your message has been posted {...} short delay" confirmation when we submitted a post. It allowed us to edit the message immediately if desired, which it displayed in 'preview' form.
    To the extent there must be a short (or not so short) delay before the message is visible in the forum's list, this was a good feature: not only did it allow immediate editing, it also allowed us to jump to any point in the path to the topic using the path links (like Apple.com > Support > Discussions > Using Apple Discussions > Feedback about Discussions) if we wanted to, instead of being forced to wait out the delay while doing nothing, & then being returned to the topic, whether that is where we wanted to go next or not.
    It also avoided the uncertainty over if it was accepted before an all too frequent interruption of service/server not found/"We are sorry" error occurred, which appears to be a common reason for duplicate posts.
    As it stands now, it appears there will always be a delay before the post is visible, & not infrequently that discussions.apple.com will go offline before the delay is complete.
    For all these reasons, I hope that the "short delay" confirmation feature is restored.

    You'll have to get used to creating Ram Previews and using AE's interface in the right way. You should really go through the getting started materials on the home page and take a look at the FAQ. AE is a layer based pixel calculating beast that will do a lot more to a movie at 60 frames per second than Photoshop will do on to a still image. After Effects is essentially Photoshop for movies with a lot more options.
    If you want to smoothly drag through the timeline and playback multiple cuts with simple transitions and two or three layers then use Premiere Pro. If you need to use 20 layers and 60 effects to create a stunning composite or motion graphics effect then you're stuck with rendering at just about any price point.

  • Unity 4.2(1.0) delayed messages

    We have customer who are having issues of delayed delivery of voicemails.. sometimes days...
    The problem is that Unity holds some voicemails for days before releasing them. Some users saying that after return from holiday, they clear down all voicemails and then the following day they get some from a few days ago.
    I have restarted the server and MTA service but this issue seems to return after few days.
    Any idea what could be the issue or is there a bug in this version?
    Help would be much appreciated.
    Thanks

    this is the text for the Cisco Unity 4.2(1) Engineering Special 173 (I also reported the broken link that you saw earlier):
    Release Notes for 4.2(1) Engineering Special 173
    System Requirements
    Overview
    Engineering Special Installation Instructions
    Post Installation Steps
    New Options and Features
    Uninstall Instructions
    Resolved Defects
    System Requirements
    This Engineering Special (patch) requires Cisco Unity 4.2(1) and needs to be installed on both Primary and Secondary Cisco Unity failover servers in the case of a failover configuration.
    Overview
    A complete list of defects addressed by this Engineering Special can be found in the section titled Resolved Defects. This Engineering Special is a roll-up of the following Engineering Specials and service patches:
    ES172, ES171, ES170, ES169, ES168, ES167, ES166, ES165, ES164, ES163, ES162, ES161, ES160, ES159, ES158, ES157, ES155, ES153, ES152, ES150, ES149, ES148, ES147, ES146, ES145, ES144, ES143, ES142, ES140, ES139, ES137, ES135, ES134, ES133, ES132, ES131, ES130, ES129, ES127, ES126, ES125, ES123, ES122, ES121, ES120, ES119, ES118, ES117, ES116, ES115, ES114, ES113, ES112, ES111, ES110, ES109, ES108, ES107, ES106, ES105, ES104, ES103, ES102, ES101, ES100, ES99, ES98, ES97, ES96, ES95, ES94, ES93, ES92, ES91, ES89, ES88, ES87, ES86, ES85, ES84, ES83, ES82, ES81, ES80, ES79, ES78, ES77, ES76, ES75, ES73, ES72, ES71, ES70, ES69, ES68, ES67, ES66, ES64, ES63, ES62, ES61, ES59, ES58, ES57, ES56, ES55, ES54, ES53, ES52, ES51, ES50, ES49, ES48, ES47, ES46, ES44, ES43, ES42, ES41, ES40, ES39, ES38, ES37, ES36, ES35, ES34, ES33, ES32, ES31, ES30, ES28, ES27, ES26, ES25, ES24, ES23, ES22, ES20, ES19, ES18, ES17, ES16, ES15, ES14, ES13, ES12, ES11, ES10, ES9, ES8, ES6, ES5, ES4, ES3, ES2, ES1
    Engineering Special Installation Instructions
    Logon to the Cisco Unity server console either directly (physical console) or via VNC (do not use Terminal Services / Remote Desktop)
    Double click the executable install file CU4.2(1)_ES173.exe
    Step through the installation wizard clicking 'Next' as appropriate
    Once the installation has completed select the option to reboot the Cisco Unity server
    Post Installation Steps
    1) This patch must be installed after applying this Engineering Special, available here for download: Other non-Cisco Unity Patch 70.
    This patch installs new prompts to provide a warning when the Reply-All recipient list either contains a PDL or is above a threshold.
    2) These steps must be applied after applying this Engineering Special:
    a. Stop Tomcat service.
    b. Delete only the files in
    \CommServer\cscoserv\Tomcat\work\Standalone\localhost\ciscopca directory.
    c. Restart Tomcat service.
    3) Customers using the Blackberry feature with Cisco Unity must apply this patch on the Blackberry server after applying this Engineering Special, available here for download: Other non-Cisco Unity Patch 76.
    4) Customers with systems based in Australia shall be affected by the Daylight Saving Time changes introduced by the Australian Gov't across several of their territories. The changes cause systems to report incorrect time stamps and to resolve them patches from Microsoft and Sun Microsystems must be applied after applying this engineering special:
    Sun Microsystems patch:
    a. Download the TZUpdater 1.2.2 or later from here: TZ Updater to the Cisco Unity system.
    b. Stop the Tomcat service.
    c. Unzip the contents to the same folder, file extracted tzupdater.jar
    d. Open a CMD window and change directories to where tzupdater.jar is located
    e. Enter "%JAVA_HOME%\jre\bin\java -jar tzupdater.jar -u -v -bc" and press enter. The output should be similar to this:
    - java.home: E:\CommServer\cscoserv\Java2SDK\jre
    - java.vendor: Sun Microsystems Inc.
    - java.version: 1.4.2_13
    - JRE time zone data version: tzdata2006g
    - Embedded time zone data version: tzdata2007h
    - Extracting files... done.
    - Making changes for JDK 1.1 compatibility... done.
    - Renaming directories... done.
    - Validating the new time zone data... done.
    - Time zone data update is complete.
    Windows Patch
    Apply the relevant Windows patch (Windows 2003 SP1/SP2 or Windows 2000 SP4) to the following machines:
    a. Each Cisco Unity Server
    b. Each Cisco Unity Bridge
    c. All servers hosting Microsoft Exchange or Lotus Domino housing a mailbox of a Cisco Unity subscriber
    d. The Cisco Unity partner mail server
    e. Each Exchange server with the Internet Voice Connector installed
    f. Each domain controller in an Active Directory (AD) domain with a Cisco Unity server
    g. Each global catalog server within the AD forest where Cisco Unity is present
    The Windows 2003 SP1/SP2 patch may be obtained directly from Microsoft under Knowledge Base article 955839. The Windows 2000 SP4 patch, KB article 942763, is only available to customers with a Microsoft Extended Hotfix Service Agreement for Windows 2000.
    Defect: CSCsm32946, CSCtc11035
    4) Customer sites where Cisco Unity integrated with multiple PIMG devices is failing to start after Microsoft hotfix MS08-037 - KB 953230 was applied must do the following after applying this Engineering Special:
    a) Open and close the Manage Integrations (UTIM) utility.
    b) Reboot the Cisco Unity server for the changes to take affect.
    Defect: CSCsv54175
    New Options and Features
    The following sections detail how to enable new options and features that are supported by this ES. Prior to following these steps, you must first install the ES as per the above Engineering Special Installation Instructions section
    1) Customers wishing to change the number of Microsoft Exchange mailstores Cisco Unity supports, shall need to modify the registry key found here:
    [\HKLM\Software\Active Voice\AvWm\1.00]
    Registry Key Name: Max Stores
    Registry Key Type: DWORD
    Registry Key Default Value: 250
    Other Settings:
    After changing the number of mailstores to support, stop Cisco Unity and the CuMdbStoreMonitor service and then re-start Cisco Unity.
    Defect: CSCsu03848
    2) Customer's wishing to enable the enhanced Cross-server login functionality shall need to upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Networking - Allow Transfer Override on Cross-server Transfer Handoff and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsd69934
    3) Customer's wishing to enable the enhanced functionality for transfers to alternate contact numbers shall need to upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Conversation - ACN Follows Current Transfer Rule and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsi02306
    4) Customers wishing to enable the functionality to prevent accidentally reply-all to PDLs shall need to upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Conversation - Reply-to-All Warning and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsi01131
    5) Customer's experiencing issues with cross-server transfers to VPIM, Bridge or AMIS subscribers under the conditions listed below should consider enabling this functionality:
    - Cisco Unity A and Cisco Unity B are two servers in the same directory and dialing domain.
    - Cisco Unity A has a VPIM (or Bridge or AMIS) Delivery Location configured for remote location X.
    - Cisco Unity A has a VPIM (or Bridge or AMIS) Subscriber (SubExt) associated with the Delivery Location.
    - Cisco Unity B, on the SA Dialing Domain page, "Cross-server transfer: Pass control to the called subscriber's Cisco Unity server" is enabled.
    In these conditions, if a caller calls Cisco Unity B and enters the id of SubExt, Cisco Unity B will prompt "One moment please", then immediately "You cannot be transferred now" and the caller will be returned to the previous conversation state.
    Upgrade to the latest version of the Advanced Setting Tools.
    Launch the Advanced Setting Tool and look for Networking - Cross-server Transfer Behavior for External Subscribers and follow the instructions in the description for a full understanding on how this works feature can be enabled/disabled.
    Defect: CSCsh56194
    6) Customers wishing to set the pre-pended and post-pended digits to any extension that a caller may dial while listening to the greeting for a Call Handler or Subscriber shall need to upgrade to the latest version of the Bulk Edit Utility.
    Launch the Bulk Edit Utility and perform topic search in the Help file for instructions on how to set the pre-pend and post-pend digits for Callhandlers and Subscribers.
    Defect: CSCse16249
    Uninstall Instructions
    On the Cisco Unity server console browse to the X:\CommServer\EngineeringSpecialBackup\ folder
    Search for the folder called CU4.2(1)_ES173
    Double click the Restore.bat file and follow the instructions
    Once the un-install completes reboot the Cisco Unity server
    Resolved Defects
    All defects listed below are included in this ES
    Fixes introduced in CU4.2(1)_ES173
    CSCsf27378
    CSCsf27378 - Media Master fails to load with "not found" errors in PCA
    CSCtc24189
    CSCtc24189 - HTTP TRAP - CPCA TRaP record does not work
    CSCsv30015
    CSCsv30015 - Unity failing to connect to SQL causing Unity to stop working as expected
    CSCsx94938
    CSCsx94938 - Recording New Greetings causes a file lock condition
    CSCta71728
    CSCta71728 - Issue with ActiveX controls shipped with Unity PCA
    CSCsz17586
    CSCsz17586 - Unity Inbox timestamp incorrect for some time zones
    CSCtc11035
    CSCtc11035 - DST change for Western Australia
    Fixes introduced in CU4.2(1)_ES172
    CSCsz19418
    CSCsz19418 - modify exclusion pattern so . (period) is allowed
    CSCsi74619
    CSCsi74619 - Conv - Empty-body TTS message can cause AV
    CSCsy10773
    CSCsy10773 - Intermittent License Corruption on double-byte Unity systems
    Fixes introduced in CU4.2(1)_ES171
    CSCsq76448
    CSCsq76448 - primary active but ports unregistered after reboot when sec. offline
    CSCsx67429
    CSCsx67429 - modify exclusion pattern so _ (underscore) is allowed with Exchange
    CSCsx95506
    CSCsx95506 - Remove feedback link from CPCA and SA
    Fixes introduced in CU4.2(1)_ES170
    CSCsx20874
    CSCsx20874 - Double-free in Event Log class can cause heap corruption, crash
    Fixes introduced in CU4.2(1)_ES169
    CSCsx20874
    CSCsx20874 - Double-free in Event Log class can cause heap corruption, crash
    Fixes introduced in CU4.2(1)_ES168
    Fixes introduced in CU4.2(1)_ES167
    CSCsv54175
    CSCsv54175 - Unity has IP Port conflicts with DNS after MS08-037 installed.
    CSCsw73149
    CSCsw73149 - Unity not starting Unexpected result in CAvLic::QueryS. Unspecified error
    Fixes introduced in CU4.2(1)_ES166
    CSCsv37908
    CSCsv37908 - If Interview Handler Question Skipped, Unity States Message Has No Audio
    CSCsv10048
    CSCsv10048 - DOM: Unity does not keep BusinessTelephoneNumber in sync
    CSCsv93549
    CSCsv93549 - Failover: FCW can fail if run after certain ESs applied
    Fixes introduced in CU4.2(1)_ES165
    CSCsm80598
    CSCsm80598 - TdsProxy fails due to corrupted Performance Counter Registry
    CSCso96540
    CSCso96540 - Unity should write eventlog warning when MAPI stalls
    CSCsd89417
    CSCsd89417 - SA does not create a MWI device correctly in SQL
    CSCsw19755
    CSCsw19755 - Port MWI improvements, fixes, diags to 4.2 from 5.0 and 7.0
    CSCsj35854
    CSCsj35854 - AvWm - Request to port MAPI function diags
    CSCsl48610
    CSCsl48610 - Unity sends port 0 in SDP information
    CSCsw25257
    CSCsw25257 - Unity AD sync - offer setting to disable sync'ing Scope DL's
    Fixes introduced in CU4.2(1)_ES164
    CSCsh04473
    CSCsh04473 - SA: Administrative Access report is empty
    Fixes introduced in CU4.2(1)_ES163
    CSCsv24693
    CSCsv24693 - Missing stored procedures after running scripts in UnitydbEx
    Fixes introduced in CU4.2(1)_ES162
    CSCsr86345
    CSCsr86345 - SA>Primary Location page is vulnerable to Cross Site Scripting
    Fixes introduced in CU4.2(1)_ES161
    CSCsr86971
    CSCsr86971 - Anonymous Auth Logon page counts against the session count
    CSCsr86943
    CSCsr86943 - Authentication bypass w/ anonymous auth
    Fixes introduced in CU4.2(1)_ES160
    CSCsr91797
    CSCsr91797 - AvLic diagnostics don't show Unity location being processed
    Fixes introduced in CU4.2(1)_ES159
    CSCsq80836
    CSCsq80836 - AvDSAD: Syncing of ScopeDls causes performance problems.
    Fixes introduced in CU4.2(1)_ES158
    CSCsm46139
    CSCsm46139 - CUOM voicemail test fails to deliver msg to inbox
    CSCso28123
    CSCso28123 - Unity repeats option to record message
    Fixes introduced in CU4.2(1)_ES157
    CSCse87865
    CSCse87865 - Change greeting to CUBI subscriber will change all others to default
    Fixes introduced in CU4.2(1)_ES155
    CSCso69772
    CSCso69772 - When sending message, if hang up after continuing, is not delivered
    Fixes introduced in CU4.2(1)_ES153
    CSCsm27607
    CSCsm27607 - JPN: Message Locator cannot search messages
    CSCsm09325
    CSCsm09325 - Unnecessary Drafts folder in unexpected language is created in Outlook
    CSCsd26042
    CSCsd26042 - Realspeak engine buffer overflow results in email TTS failure
    Fixes introduced in CU4.2(1)_ES152
    CSCsm90314
    CSCsm90314 - Dom: message notification re-sent on MWI Resync
    Fixes introduced in CU4.2(1)_ES150
    CSCsm97318
    CSCsm97318 - ReportDb_log.ldf or TempLog.ldf fill disk, may cause failsafe
    Fixes introduced in CU4.2(1)_ES149
    CSCsm82003
    CSCsm82003 - Streamsweeper logic deletes DB reference when it shouldn't
    Fixes introduced in CU4.2(1)_ES148
    CSCsi22389
    CSCsi22389 - Virtual Bytes / Fragmentation in AvCsMgr
    Fixes introduced in CU4.2(1)_ES147
    CSCsm17318
    CSCsm17318 - Unity can't set Continue adding names after each addressee from Web SA
    Fixes introduced in CU4.2(1)_ES146
    CSCsm32946
    CSCsm32946 - DST Australia Unity: Update for Unity
    Fixes introduced in CU4.2(1)_ES145
    CSCsg90913
    CSCsg90913 - Inconsistent subject line on subscriber to subscriber message
    CSCsk56884
    CSCsk56884 - Subscriber sign in should respect system first & inter digit dtmf delays
    Fixes introduced in CU4.2(1)_ES144
    CSCsm10385
    CSCsm10385 - MWI Refresh/resync turns MWI Off for New Urgent Domino Msg
    Fixes introduced in CU4.2(1)_ES143
    Fixes introduced in CU4.2(1)_ES142
    CSCsl79289
    CSCsl79289 - MWI lengthy after Exchange Cluster Failover
    Fixes introduced in CU4.2(1)_ES140
    CSCsl59482
    CSCsl59482 - VMO reports errors when form is published by not locally installed
    Fixes introduced in CU4.2(1)_ES139
    CSCsk79469
    CSCsk79469 - DST: Venezuela
    Fixes introduced in CU4.2(1)_ES137
    CSCsl56254
    CSCsl56254 - GC total resync should sync typically most important objects first
    Fixes introduced in CU4.2(1)_ES135
    CSCdx12345
    CSCdx12345
    Fixes introduced in CU4.2(1)_ES134
    Fixes introduced in CU4.2(1)_ES133
    CSCsh9258
    CSCsh9258
    CSCsf2633
    CSCsf2633
    CSCse7788
    CSCse7788
    CSCsg0314
    CSCsg0314
    Fixes introduced in CU4.2(1)_ES132
    CSCsl10496
    CSCsl10496 - Conversation Exception can cause Unity to ring-no-answer (RNA)
    CSCsk88930
    CSCsk88930 - Duplicate Alias can cause system to become unresponsive
    Fixes introduced in CU4.2(1)_ES131
    CSCsh61500
    CSCsh61500 - Can't forward Domino msgs without an intro via TUI with streamlined conv
    Fixes introduced in CU4.2(1)_ES130
    Fixes introduced in CU4.2(1)_ES129
    CSCsi43057
    CSCsi43057 - Heap Corruption in Miu during ASR cleanup
    CSCsk67827
    CSCsk67827 - MWI's may fail for PIMG integrations greater than the first integration.
    Fixes introduced in CU4.2(1)_ES127
    CSCsd16651
    CSCsd16651 - When invalid password entered at known extension, do not prompt for ID
    Fixes introduced in CU4.2(1)_ES126
    CSCsk08880
    CSCsk08880 - SA: SA use causes memory spikes/leak in AvCsMgr process
    Fixes introduced in CU4.2(1)_ES125
    CSCsk08880
    CSCsk08880 - SA: SA use causes memory spikes/leak in AvCsMgr process
    Fixes introduced in CU4.2(1)_ES123
    CSCsj76543
    CSCsj76543 - No audio if SIP call not cleared correctly, UDP port re-used
    Fixes introduced in CU4.2(1)_ES122
    CSCsd93217
    CSCsd93217 - Cross box login SIP not functioning
    Fixes introduced in CU4.2(1)_ES121
    CSCsj53656
    CSCsj53656 - New Call Routing Rules Should be disabled by default
    CSCsh15836
    CSCsh15836 - Unity 4.1.1 multiple admin adding call routing rules get mixed
    CSCsc8690
    CSCsc8690
    CSCsi1374
    CSCsi1374
    CSCsg4933
    CSCsg4933
    Fixes introduced in CU4.2(1)_ES120
    CSCsc51996
    CSCsc51996 - DInterop-Interop subs on member servers not deleted from Global sub tbl
    CSCsf10680
    CSCsf10680 - DOM: deleted Domino users are not removed from GlobalSubscriber table
    Fixes introduced in CU4.2(1)_ES119
    CSCsj80282
    CSCsj80282 - User name with Apostrophe will generate error
    Fixes introduced in CU4.2(1)_ES118
    CSCsj81527
    CSCsj81527 - Unity Inbox: time stamp adjustment not valid for DST change in 2007 NZ
    CSCsh35828
    CSCsh35828 - Unity Inbox: time stamp adjustment not valid for DST change in 2007
    Fixes introduced in CU4.2(1)_ES117
    CSCse77587
    CSCse77587 - TMP files in Unity Message Store account's temp folder fill drive
    Fixes introduced in CU4.2(1)_ES116
    Fixes introduced in CU4.2(1)_ES115
    Fixes introduced in CU4.2(1)_ES114
    Fixes introduced in CU4.2(1)_ES113
    Fixes introduced in CU4.2(1)_ES112
    CSCsj57251
    CSCsj57251 - Errors during Play Speed Adj with g.711 to g.729a conversion
    Fixes introduced in CU4.2(1)_ES111
    CSCsi73888
    CSCsi73888 - PCA Unity4.2.1- UK language reverse day with month in Alternate Greeting
    Fixes introduced in CU4.2(1)_ES110
    CSCsd39975
    CSCsd39975 - PCA cannot read or write to database when JDBC connections are refused
    Fixes introduced in CU4.2(1)_ES109
    CSCsi76164
    CSCsi76164 - DOM: Msg sent to a sub even if deleted from reply to all recipient list
    Fixes introduced in CU4.2(1)_ES108
    CSCsj16707
    CSCsj16707 - Crossbox showing event log warnings on caller disconnect
    CSCsj03459
    CSCsj03459 - Streamlined Conversations are inconsistent
    Fixes introduced in CU4.2(1)_ES107
    CSCsg76524
    CSCsg76524 - BusinessLogicManagerSvr.dll violates DLLMain rules and causes deadlock
    Fixes introduced in CU4.2(1)_ES106
    Fixes introduced in CU4.2(1)_ES105
    Fixes introduced in CU4.2(1)_ES104
    CSCsi95296
    CSCsi95296 - Optional Conversion Help (Zero for Help) is not functioning
    Fixes introduced in CU4.2(1)_ES103
    CSCsi88008
    CSCsi88008 - AvConcCVMENU006.wav causes call to terminate prematurely
    Fixes introduced in CU4.2(1)_ES102
    Fixes introduced in CU4.2(1)_ES101
    CSCsi98311
    CSCsi98311 - PIMG: Notifier should disable port when PIMG unavailable
    Fixes introduced in CU4.2(1)_ES100
    Fixes introduced in CU4.2(1)_ES99
    CSCsi77374
    CSCsi77374 - Unity Mobile Messaging Cannot Handle Spaces
    Fixes introduced in CU4.2(1)_ES98
    CSCsd46384
    CSCsd46384 - NodeMgr gives error in Eventlog: DeleteFile() fails with 80070020
    Fixes introduced in CU4.2(1)_ES97
    CSCsi85034
    CSCsi85034 - Extension remapping fails for calling # with SIP Fwd'd calls
    Fixes introduced in CU4.2(1)_ES96
    Fixes introduced in CU4.2(1)_ES95
    CSCsi64012
    CSCsi64012 - FCW fails to verify SQL is installed with WS03 3SP2
    Fixes introduced in CU4.2(1)_ES94
    CSCsi86913
    CSCsi86913 - Crossbox: No configurable timeout for digits received during transfer
    Fixes introduced in CU4.2(1)_ES93
    CSCsi82851
    CSCsi82851 - Crossbox: transfer fails with Handoff Response = ##
    Fixes introduced in CU4.2(1)_ES92
    Fixes introduced in CU4.2(1)_ES91
    CSCsh94992
    CSCsh94992 - Domino NDN causes Unity crash
    Fixes introduced in CU4.2(1)_ES89
    CSCsi69607
    CSCsi69607 - MIU fails to initialize TTS on Win2003 SP2.
    Fixes introduced in CU4.2(1)_ES88
    CSCsd76986
    CSCsd76986 - Unity MTA Counter Do not Increment in Performance Monitor
    Fixes introduced in CU4.2(1)_ES87
    Fixes introduced in CU4.2(1)_ES86
    CSCsg49334
    CSCsg49334 - License Pooling does not work between Unity 4x and 5x versions.
    Fixes introduced in CU4.2(1)_ES85
    CSCsi56850
    CSCsi56850 - Crash in AvCsMgr while loading Event Log
    Fixes introduced in CU4.2(1)_ES84
    CSCsg64120
    CSCsg64120 - Unity MWI resync performance needs improvement
    Fixes introduced in CU4.2(1)_ES83
    Fixes introduced in CU4.2(1)_ES82
    CSCsd75873
    CSCsd75873 - Miu exception under load referencing MiuCall without lock
    CSCsd75912
    CSCsd75912 - AvWav errors during 144 port load
    CSCsi16038
    CSCsi16038 - Heap Corruption in UnitySipStack.dll
    CSCsi19521
    CSCsi19521 - Unity 4.2ES - Allow 144 ports
    Fixes introduced in CU4.2(1)_ES81
    CSCsi13742
    CSCsi13742 - Exception with variant holding a date
    Fixes introduced in CU4.2(1)_ES80
    CSCsi16038
    CSCsi16038 - Heap Corruption in UnitySipStack.dll
    Fixes introduced in CU4.2(1)_ES79
    CSCsi02306
    CSCsi02306 - ACN should follow the active transfer rule
    CSCsi01131
    CSCsi01131 - Unity should prevent occurrences of accidental reply-all to PDLs
    CSCsi01116
    CSCsi01116 - sub restricted from sending to PDLs can still reply-all to PDLs
    CSCsf14610
    CSCsf14610 - Reply-To-All to a large number of recipients can cause delays..
    CSCsg52066
    CSCsg52066 - Subscriber not able to toggle between Standard and Alternate greeting
    Fixes introduced in CU4.2(1)_ES78
    CSCsh35894
    CSCsh35894 - MWI doesn't work for VPT added Unity subscribers
    Fixes introduced in CU4.2(1)_ES77
    CSCsi04112

  • Delay messages being placed on a queue.

    Hello,
              I am using WL6.0 on the latest service pack. I have an applet that
              connections directly to a queue. I have an MDB consuming the message.
              There are times typically the first or second message sent from the applet
              when it will take 5 - 10 seconds to get consumed. Otherwise, the messages
              are instantaneously received. Any suggestions would be greatly appreciated.
              John
              

    Hi John,
              Well, 8.1 has a setting that changes the rmi load-balancing behavior
              on a cluster-wide basis. It causes rmi to favor using remote
              objects that are located on servers that the client is already
              connected to (aka server-affinity). If you are using applets,
              8.1 is particularly attractive for another reason: it contains
              a fully capable JMS client in 700K (without JMS it is 300K).
              The beta for 8.1 is coming out soon -- I think before the
              end of the year.
              OK, I'm assuming that 8.1 won't be soon enough to help. See
              if you can narrow down the problem. Measure what
              happens with a single non-clustered server where the applet
              host, jms server host, and connection factory host are all the same.
              Measure this configuration as well as your current configuration
              to see where the actual delays are - obtaining the initial
              context, obtaining the connection factory, or obtaining
              the connection from the connection factory.
              Furthermore, I suggest:
              targeting the connection factory at ONLY the server that
              hosts the destination (for applets this makes
              good sense - there is no need for JMS to create
              connection concentrators when applet hosts are
              already acting as concentrators, and this prevents
              connections from making useless extra network hops).
              seeing if you can change the applet application to attempt
              its initial connection earlier
              posting your question to the
              weblogic.developer.interest.performance newsgroup
              Tom
              John Favre wrote:
              > Thank you for your response that makes a little sense. What would you
              > suggest to resolve this issue?
              >
              > Thank you
              >
              > "Tom Barnes" <[email protected]> wrote in message
              > news:[email protected]...
              >
              >>I suspect the delay is due to rmi, and not jms specifically.
              >>Establishing an initial context takes some amount of time.
              >>
              >>It may help to ensure that the applet host, queue, and connection
              >>factory are all on the same server.
              >>
              >>Here is what happens when
              >>jmsConnectionFactory.createQueueConnection() is called from
              >>a client outside of the cluster (such as an applet):
              >>
              >> RMI picks a random server from among all of the
              >> hosts in the cluster that the connection factory
              >> is targeted at.
              >>
              >> RMI attempts to contact server that hosts the
              >> CF directly
              >>
              >> if above fails (for instance because the applet sandbox
              >> restricts connections to the applet's host), then
              >> RMI will retry contacting the CF server by
              >> routing traffic through the client's already
              >> established context host (in this case
              >> the applet's host server)
              >>
              >>Tom
              >>
              >>John Favre wrote:
              >>
              >>>Hello,
              >>>
              >>>I am using WL6.0 on the latest service pack. I have an applet that
              >>>connections directly to a queue. I have an MDB consuming the message.
              >>>There are times typically the first or second message sent from the
              >>
              > applet
              >
              >>>when it will take 5 - 10 seconds to get consumed. Otherwise, the
              >>
              > messages
              >
              >>>are instantaneously received. Any suggestions would be greatly
              >>
              > appreciated.
              >
              >>>John
              >>>
              >>>
              >>
              >
              >
              

  • Exchange logging of delayed messages

    We are having the known issue of delayed outbound messages (last error: 400 4.4.7 message delayed), whereas the suggested ways to fix it are to edit the host file on cas/ht servers or to turn on external DNS and then add smtp addresses as needed. 
    Of course we can telnet to these same addreses and successfully send messages, so it makes it look like our DNS is broken, but our DNS appears to be working fine.  We are trying to investigate this further to confirm the DNS is indeed working as it should
    so I checked to make sure logging was turned on in the cas/ht servers and the outbound connector is set to verbose logging.  I have also looked at some of the tools in the EMC toolbox to trace problem child messages.  Out of all of this, including
    looking at logs, all I can see is the message goes out and/or it didn't get delivered, depending on what tool or log I am looking at.  I don't see anything else to indicate why it is having a problem with the message, thereby delaying it.  I don't
    want to edit the host file as that is a hokey to manage this, and not the best option, and I was told by my supervisors that before we turn on external DNS we really need to find out why this is happening (and I really don't want to have to add smtp addresses
    and domains as additonal housekeeping, this really shouldn't be necessary).  Does anyone have any ideas as to what I can do with the logging or tools to fill in the gaps?  As I said, all I get is that it failed to deliver, and well, I knew that going
    in.  Thanks for any suggestions.  : )

    We are having the known issue of delayed outbound messages (last error: 400 4.4.7 message delayed), whereas the suggested ways to fix it are to edit the host file on cas/ht servers or to turn on external DNS and then add smtp addresses as needed. 
    Of course we can telnet to these same addreses and successfully send messages, so it makes it look like our DNS is broken, but our DNS appears to be working fine.  We are trying to investigate this further to confirm the DNS is indeed working as it should
    so I checked to make sure logging was turned on in the cas/ht servers and the outbound connector is set to verbose logging.  I have also looked at some of the tools in the EMC toolbox to trace problem child messages.  Out of all of this, including
    looking at logs, all I can see is the message goes out and/or it didn't get delivered, depending on what tool or log I am looking at.  I don't see anything else to indicate why it is having a problem with the message, thereby delaying it.  I don't
    want to edit the host file as that is a hokey to manage this, and not the best option, and I was told by my supervisors that before we turn on external DNS we really need to find out why this is happening (and I really don't want to have to add smtp addresses
    and domains as additonal housekeeping, this really shouldn't be necessary).  Does anyone have any ideas as to what I can do with the logging or tools to fill in the gaps?  As I said, all I get is that it failed to deliver, and well, I knew that going
    in.  Thanks for any suggestions.  : )
    SMTP Protocol logging is the place to start:
    http://technet.microsoft.com/en-us/library/bb124531(v=exchg.141).aspx
    I don't see why anyone would suggest configuring a host file in this instance.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Maybe you are looking for