Message waiting in queue

Hi guys,
I’m trying to connecting XI (integration server) to R/3 (Application sys) using ABAP proxy.
When the message enters in XBTO2___0002 (inbound queue) it can’t leave there!!!
Queue status is: a yellow triangle “Message waiting in queue”.
I don’t have any error messages, only this status…I don’t know what happens!
Anybody could help me?
Thanks in advance,
Ricardo.

Hi Ricardo,
Try registering queues again...it worked for me for the same problem.
sxmb_Adm->mange queues->register queues..
Regards
Anand
Message was edited by: Anand Torgal

Similar Messages

  • Client Proxy - Message waiting in queue

    Hi all,
    I have a client proxy in R3 that sends information to XI. I see in XSMB_MONI a green flag, but in the field "status queue" appears a yellow triangle with the message "Message waiting in queue".
    In Runtime Workbench I don't see any message.
    Any help? I have to activate the queue?
    Regards,

    Hi,
    Have u registered the queue in R3? If not....
    1.Go to SXMB_ADM(R/3)
    2. Go to Manage Queues and then
    3. Register All Queues.
    <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically Failed Messages</a>
    Regards
    San

  • Message waiting in queueu0085

    Hi all,
    During message process some messages stop in some queues with the message “time limit exceeded” and obstruct other messages to be processed. I need to delete the first queue entry to process the remaining messages. I don’t want delete the block entry because one message is lost…
    I would like to know how I can fix this issue preventing an elimination of messages.
    Thanks in advance,
    Ricardo.

    Hi,
    Go through these links:
    Message waiting in queue
    Messages in BPM with Status Waiting
    Message Queue in XI is stuck
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Hope these will be of help.
    Regards,
    Divija.

  • Messages waiting indefinetely in queue -- how to purge

    Hi All,
    I have around 900 messages in the outbound queue waiting in the past 2 days .
    Is there any way to purge sceduled messages in the Queue (SMQ1,SMQ2)?
    My messages are indefinetely growing in the message queue without processing. I understand I need to configure a background job for that.
    Which transaction code should i use to schedule Backgound job for Messages ( not BPM) ?
    Is there any way I can purge these messages from the queue before they get processed by XI?
    if yes please let me know the way.
    Because of this a scenario I run today is scheduled in the queue after 3 days and my receiver is unable to get the message.
    Regards,
    Meher

    Hi All,
    Thanks All for helping me.
    Initiated a search for all the messages waiting on all the Queues.
    Status of all the messages shows : <b>To Be Delivered</b>
    Messages were processed successfully till some date. we have a system down after that.
    From then on messages are not being processed.
    Am I missing in the job configuration for the Queues.
    Queue status is displayed as Ready ( no errors)
    Regards,
    Meher
    This is not a production environment.

  • Streams AQ: waiting for messages in the queue

    Hi,
    For some reason, I've to run the owb mapping manually. First I try to run it in this way:
    declare
    n_result number;
    begin
    n_result:=dwrr104.wb_rt_api_exec.run_task('LOC_ZONE2_DW','PLSQL','MAP_RMS_CUSTOMER');
    dbms_output.put_line('result :='||n_result);
    end;
    This script just kept running endlessly. I noticed The wait event in database for this session was: "Streams AQ: waiting for messages in the queue"
    However, if I run the 'main' function of this mapping directly like this:
    declare
    -- Non-scalar parameters require additional processing
    p_env dw.wb_rt_mapaudit.wb_rt_name_values;
    begin
    -- Call the function
    :result := dw.map_rms_web_ptrackcode.main(p_env => p_env);
    end;
    it can work without any problem.
    Any ideas?
    Jeffrey

    Hi Jeffrey,
    need to change them?Yes, you need to increase value for AQ_TM_PROCESSES parameter (set it to at least 1).
    It is a requirements for target database (database where runtime services is run):
    Look at OWB installation guide (it is for OWB 10gR1 but for later OWB versions requirements is the same):
    http://download.oracle.com/docs/cd/E10926_01/doc/owb.101/b12150/appaprepdb.htm#i1008228
    Regards,
    Oleg

  • Messages in inbound queue in status-RUNNING and it is too slow

    Hi Experts,
    We have a issue there are tons of messages in inbound queue in status-RUNNING and it is too slow!, hence there are more messages getting in the queue every minute.
    This is Production enviorment.
    We have priority queues
    QIN is waiting status.
    De-register will not work due to loss of messages fear
    Please advice
    thanks and regards,
    krushi

    Hi,
    If the queues are hanging due to peak load at sometimes
    you can schedule following reports to restart them automatically
    (dont have to lock and unlock manually)
    RSQIWKEX - Inbound Queues
    RSQOWKEX- Outbound Queues
    Also you can save the first entry of the queue if its causing problems to process later- smq3
    thanks
    francis

  • OC4J 9.0.4: Problem receiving message from JMS queue

    I've created an application which puts XML files in a JMS queue and try to get it out again. The enqueing (sending) is no problem, but when I dequeue from the same queue I receive nothing and if I don't specify a wait time the programs hangs.
    If I create a QueueBrowser I can see there are messages in the queue.
    Can someone tell me what I do wrong?
    Here is the code of my dequeue action:
    public String dequeue(int qName) throws RbsSysException
            final String method = "dequeue(int qName)";
            _log.debug(method);
            QueueConnection queueConnection = null;
            try
                queueConnection = _queueConnectionFactory.createQueueConnection();
                QueueSession queueSession = queueConnection.createQueueSession(false,
                        Session.AUTO_ACKNOWLEDGE);
                QueueReceiver queueRcv = queueSession.createReceiver(getQueue(qName));
                _log.debug("queue = "+ queueRcv.getQueue().getQueueName());
                // Due to bug 3376983 in OC4J We cannot use TextMessage if it exceeds
                // 64 kb. Therefore use ObjectMessage.
                Message msg = queueRcv.receiveNoWait();
                _log.debug("msg = " + msg);
                ObjectMessage objMsg = (ObjectMessage)msg;
                //ObjectMessage objMsg = (ObjectMessage) queueRcv.receiveNoWait();
                _log.debug("objMsg = " + objMsg);
                if (objMsg != null)
                    return (String) objMsg.getObject();
                else
                    return null;
            catch (JMSException je)
                throw new RbsSysException(je);
            finally
                if (queueConnection != null)
                    try
                        queueConnection.close();
                    catch (Exception any)
                        _log.error("Error while closing QueueConnection: ", any);
        }

    Did you implement javax.jms.MessageListener and the method onMessage(Message)?
    If you use onMessage() as wel as receive (or receiveNoWait() or receive(long)), the onMessage() can be called, while the main thread is blocking on a synchronous receive, so make sure you use only one of the two methods: onMessage() or receive.
    Receive() blocks your thread until a message is published. So your program 'hangs' by design. Usually this is used when your program is waiting for a particular message. Otherwise use onMessage().
    ReceiveNoWait() checks if something is in the queue at that very moment, so if nothing is there (yet), the main thread continues.
    Hope this helps,
    Lonneke

  • ** Message being processed - Queue status green colour

    Hi Friends,
    Many messages in our SXMB_MONI  shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
    Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
    Kind Regards,
    Jeg P.

    HI,
    QUEUE STATUS RUNNING BASICALLY MEANS THT
    The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
    HOPE THIS WILL SOLVE THE PROBLEM
    PLZ REWARDS POINTS
    VIKAS

  • A bug in message pattern's queue implementation?

    Here is how to reproduce the problem.
    Have 2 Java program ready.
    A is to create a queue and publish 3 messages to the queue.
    B is to subscribe to the same queue and try to get all messages from the queue (put the getMessage inside a while(true) loop) then wait for new message.
    Step 1. Run A, which put 3 messages into queue.
    Step 2. Run B, which get 3 messages out of the queue then waiting on the getMessage() blocking call.
    Step 3. Kill program B without unsubscribe() call.
    Step 4. Run A, which put 3 messages into the queue again.
    Step 5. Run B, this time it only get 2 messages. The 1st message A put in on Step 4 got lost.
    Actually, if you run Step 2 multiple times before step 3, you will lost more message. It seems each time when there is a subscription created without a unsubscribe(), it will get one message lost.
    I know the propery way is to call unsubscribe(), but the JVM could be killed thus won't have time to do cleanup.

    Using message pattern 2.3, command pattern 2.3 and common 1.3
    Coherence version is 3.4.2.
    BTW, if the unit test program you mentioned is the MessageTests.java included in the src zip file, you won't be able to test this issue.
    All unit test inside the MessageTests.java are comsuming exactly number of messages been published then do unscribe() call.
    In order to reproduce this issue, you'd need to put your consumer JVM in a blocking getMessage() state (i.e. call getMessage() while there is no message in queue)
    then kill the JVM. The unit test codes in MessageTests.java never enter blocking wait state when call getMessage().
    Example code -
    For the one putting message
    MessagingSession messagingSession = DefaultMessagingSession.getInstance();
    Identifier topicIdentifier = messagingSession.createQueue("test-queue");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY1");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY2");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY3");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY1");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY2");
    messagingSession.publishMessage(topicIdentifier, "Hello WorldY3");
    For the one getting message
    MessagingSession messagingSession = DefaultMessagingSession.getInstance();
    Identifier topicIdentifier = messagingSession.createQueue("test-queue");
    Subscriber subscriber = messagingSession.subscribe("test-queue");
    while (true) {
    String message = (String)subscriber.getMessage();
    System.out.println(message);
    }

  • Message sitting in Queues for 30 minutes before MDB picks them up

    We're seeing a situation where we place messages on a queue and a small percentage of them will sit on the queue for 30 minutes before being picked up by the MDB to process. Anyone see this before?
              Here is the background. We're running 3 distributed queues on a cluster of 4 Weblogic 8.1 sp3 servers. The 30 minute issue happens on all 3 queues on all 4 servers. Currently we do not see a pattern. It can happen at a busy hour and in the middle of the night with nothing going on. During a busy timeframe, we can get up to 50 msg that hangup over a few minutes; less than 5 minutes.
              Our Service is an enterprise email service where various clients send email request to us via EJB. The EJB puts an entry into the database and puts a request msg into the queue. The MDB pulls it off the queue sends it to an email subsystem and updates the database.
              We added log msgs in both the EJB and MDB to track messages and narrowed it down to the requests just sitting in the JMS queue. We DO NOT set a delivery time via setJMSDeliveryTime().
              As mentioned is happens anytime during the day (busy or idle), may go for days without occuring, on any of the 3 JMS queues, on any of the 4 cluster servers, and for any of the clients. It's consistantly 30 minutes. This occurs on a small number of requests, but is enough to concern our business owner.
              Any thoughts on possible problems or any thoughts on monitoring or tracking down the issue is greatly appreciated.
              Thanks. Later...
              - Wayne

    One possibility is that the messages have already been pushed to an MDB instance in the JMS asynchronous consumer pipeline, but the MDB instance has stalled during message processing - which delays processing of the following messages. The waiting messages count as "pending" in the JMS statistics.
              You can reduce the number of messages in a JMS asynchronous consumer's pipeline via the "MessagesMaximum" connection factory setting (default is 10). First: create a custom connection factory with transactions enabled (to support transactional MDBs), and ack-mode set to "previous" (to support pub/sub MDBs), and MessagesMaximum set to its lowest possible value. Second: specify this connection factory's JNDI name in the MDB's weblogic descriptor.
              Tom, BEA

  • Pending Messages waiting for Client Acknowledgement

              Hi,
              I have tried to search the Internet for an answer to this question but failed.
              Any clue???
              I have setup a queue on BEA WLS 7.4. I have four consumers which connect concurrently
              to dequeue messages. Each of the consumers serve as a proxy to other clients
              waiting for the messages.
              The proxy application (consumer) is developed such that it will send the client_acknowledge
              to the Q manager after it finishes processing the received message and sends it
              successfully to the external client.
              I noticed that in some exceptional cases which I cannot reproduce, the proxy application
              would fail to send the message to client and therefore wouldn't send the client_acknowldege.
              Although I tried to catch all possible exceptions, i cannot catch this single
              exception that causes my proxy to continue processing the messages in a proper
              way. The problem is that I end up with some Pending Messages on the queue which
              cannot be available to other consumers and would stay that way till the consumer
              that was attempting to dequeue it is killed.
              Isn't there any way to configure an expiry period for this client_acknowledge
              wait state??? In other words, is it possible to configure a time after which
              the JMS provider would no longer be waiting for the client_acknowledge and sends
              the pending message back to the Q in a state that makes it available to other
              consumers.
              

    Sorry. Once a message has been received in "CLIENT_ACKNOWLEDGE" mode, it
              remains pending and unavailable to other consumers until either the consumer
              is closed, acknowledge is called, or the client disconnects.
              Have you tried using a transacted session? In that case, the transaction
              will time out eventually, which will roll back the transaction and make the
              message visible again. You can control the length of this timeout using the
              "TransactionTimeout" parameter on the JMS connection factory.
              greg
              "Muhannad" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi,
              > I have tried to search the Internet for an answer to this question but
              failed.
              > Any clue???
              >
              > I have setup a queue on BEA WLS 7.4. I have four consumers which connect
              concurrently
              > to dequeue messages. Each of the consumers serve as a proxy to other
              clients
              > waiting for the messages.
              >
              > The proxy application (consumer) is developed such that it will send the
              client_acknowledge
              > to the Q manager after it finishes processing the received message and
              sends it
              > successfully to the external client.
              >
              > I noticed that in some exceptional cases which I cannot reproduce, the
              proxy application
              > would fail to send the message to client and therefore wouldn't send the
              client_acknowldege.
              > Although I tried to catch all possible exceptions, i cannot catch this
              single
              > exception that causes my proxy to continue processing the messages in a
              proper
              > way. The problem is that I end up with some Pending Messages on the queue
              which
              > cannot be available to other consumers and would stay that way till the
              consumer
              > that was attempting to dequeue it is killed.
              >
              > Isn't there any way to configure an expiry period for this
              client_acknowledge
              > wait state??? In other words, is it possible to configure a time after
              which
              > the JMS provider would no longer be waiting for the client_acknowledge and
              sends
              > the pending message back to the Q in a state that makes it available to
              other
              > consumers.
              

  • Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit

    My core.log file keeps showing these errors everytime I start to stream. My streams are not viewable on PC's and only viewable on iOS devices.
    Is there something wrong with the libf4f.dll file? I'm using FMS 4.5 on Windows 2003 Server.
    2011-12-28    15:44:09    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    15:44:09    4020    (e)2611423    Failed to record bbc2011-BBC73 (Unknown Error).    -
    2011-12-28    16:02:00    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    16:02:00    4020    (e)2611423    Failed to record bbc2011-BBC71 (Unknown Error).    -
    2011-12-28    16:57:12    4020    (e)2611363    Server detected a backward timestamp from 5006873 to 0 in file: C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2011
    2011-12-28    17:18:21    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    17:18:21    4020    (e)2611423    Failed to record bbc2011-BBC83 (Unknown Error).    -
    2011-12-28    17:36:12    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    17:36:12    4020    (e)2611423    Failed to record bbc2011-BBC81 (Unknown Error).    -
    2011-12-28    18:38:09    4020    (e)2611363    Server detected a backward timestamp from 5420086 to 0 in file: C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2011-BBC82    -
    2011-12-28    19:12:44    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    19:12:44    4020    (e)2611423    Failed to record bbc2011-BBC92 (Unknown Error).    -
    2011-12-28    19:23:38    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    19:23:38    4020    (e)2611423    Failed to record bbc2011-BBC91 (Unknown Error).    -
    2011-12-28    20:41:50    4020    (e)2611363    Server detected a backward timestamp from 6390123 to 0 in file: C:\FMSHOME\applications\livepkgr\streams\_definst_\bbc2011-BBC93    -
    2011-12-28    21:12:05    4020    (e)2611178    Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    -
    2011-12-28    21:12:05    4020    (e)2611423    Failed to record bbc2011-BBC102 (Unknown Error).    -
    2011-12-28    22:49:23    4020    (i)2581247    Core (4020) disconnected from edge.    -
    2011-12-28    22:49:23    4020    (i)2581233    Core (4020) disconnecting from admin: 200.    -
    Thanks,
    Dave

    There is a concept of Absolute Time Code which enables the encoders to publish the livestream based on absolute system time rather than starting the messages from timestamp 0 everytime you append to a recording.
    I suspect you encoder is starting everytime from 0 timestamp but since the server already has recording till some time - say x, for the server these are backward timestamps and hence the continous warnings.
    Also to safeguard FMS against such conditions and cause memory crashes, we only allow messages with backward timestamps to accumulate in the process queue upto a limit and then the recording is stopped. Thats why you are observing the errors - 
    "Error from libf4f.dll: Total number of messages waiting to be recorded has exceeded the limit.    - 
    2011-12-28    19:23:38    4020    (e)2611423    Failed to record bbc2011-BBC91 (Unknown Error).    -"
    Try to check your encoder settings for stream synchronization or ATC settings and enable them.

  • Removing superseded messages from the queue

    Does JSMQ provide any way for a producer to remove a message from the queue which it queued some time ago but which it no longer wishes to send?
    I am investigating the use of JSMQ in a military battlemap application connecting nodes over low bandwidth/unreliable connections. The reason we want to be able to remove messages is as follows: Say a producer sends a low priority message to the queue regarding a unit's position. Later on the same producer sends an update regarding the same unit to the queue. If the first message is still present in the queue (ie has not been sent yet) then we want the producer to be able to remove it as it is now superseded by the new message and we don't want to waste bandwidth sending the old message first.
    I know we can set an expiry time on messages, but this doesn't really solve our problem. We want the original message to stay in the queue indefinately (until it is read by the consumer) unless it is superseded by a new message in which case we want to remove it.
    Thanks
    Roger

    Hi Roger,
    JMS does not support the removal of messages from a queue
    as you described. I can't think of a way to not deliver the old
    message once it was already sent.
    Alternatives I can think of:
    - Adjust the interval at which the consumer reads the messages
    off the queue and/or the number of messages that are read;
    so that the consumer will see the old and new messages
    and can decide which one to use. This does not address the
    bandwidth issue but allows the consumer to behave smarter.
    - Similar to above, but on the producer side. The producer waits
    for some interval before sending a message, in case an
    updated position of a unit arrives at the producer. This might not
    be good if a consumer needs to know the location of a unit as
    soon as it is available.
    - Use a topic instead of a queue. When using queues, old
    messages (containing old positions) sent to a queue are kept
    until the consumer reads it. With topics, if no consumers are
    around, the message is tossed. However, if you really need old
    messages to lie around (e.g. need to know last position of
    unit), this won't suit your needs.
    Sorry I don't have a straight answer for you, hope this helps
    somewhat.
    -i
    http://wwws.sun.com/software/products/message_queue/index.html

  • My iphone 3GS no longer syncs with iTunes. The phone is recognised, backs up but then I get an error message: "Waiting for changes to be applied". BUT unlike other people, it doesn't stay stuck on it, instead the process closes down immediately

    Hi all,
    Apologies: I've just joined the community and didn't quite figure how to write a msg! Hope it works...
    Anyway,
    I read many posts on this annoying error message (Waiting for changes to be applied) in the last 2/3 days, but they all refer to the sync staying stuck on it.
    Mine doesn't.
    I read the message, then it quickly shuts down the sync and the iTunes progress bar only shows the apple...
    As suggested by many, I removed voice msgs, turned off/on, tried to sync in individual stages (calendar only...) but nothing works.
    I am up to date on iTunes (11.1.1.11) and have IOS 6.1.3 on my phone, to sync on a Win8 pc (all worked fine until recently).
    I have had this phone for several years and it has never done this.
    It worked absolutely fine, until I loaded the latest version of iTunes it seems...
    Any suggestions?
    Many thanks

    ALSO, on the iPod under Settings>General>iTunes Sync, you may need to back out of the "iTunes Wi-fi Sync," and reopen it to get it to update.
    (I use iTunes 11.1.5.5)

  • Unable to receive notifications of new messages arriving on queue

    I was wondering whether any AQ experts out there could help me....
    I have an Oracle AQ queue and a .net service which listens and dequeues messages from the queue. The .net service is written (using ODP.net) to execute a poll of the queue upon startup (in order to process anything on the queue initially), and thereafter to hook into the relevant ODP.net event (happens to be OracleAQQueue.MessageAvailable) such that anything that subsequently arrives on the queue gets dequeued.
    Now, before you tell me to head off to the odp.net forum, I will add very quickly that we have this code in both DEV and TEST environments and it works fine. The queue happens to be a multiple-consumer queue, so the service subscribes as a particular consumer and everything hangs together. My problem is that we promoted all this code to LIVE a couple of days ago and although we are able to dequeue messages no problem we are no longer receiving MessageAvailable notifications.
    Now, I come from a .net background and am 100% sure that the .net code on our Live servers is the same as the code on our Test servers, save for the connection string. So I believe that the problem is more database- or queue-config-related than software-related.
    I do not have a high degree of Oracle knowledge in this area but what I can say is that when we start our .NET service, it is happily able to do the initial poll of the queue and to dequeue any messages. So this says to me that, fundamentally, we're not far off. i.e. it isn't anything really dumb like the queue doesn't exist in the live environment! It is purely that the MessageAvailable event never fires.
    I guess my question is fairly open, then. Given what I have said, can anyone think of reasons why this could happen?
    Things I have already thought of include:
    - different versions of ODP drivers. Not so, I supervised their installation myself on each environment.
    - firewall on the Live database blocking comms? I mean, presumably there is some tcp/udp comms going on underneath the MessageAvailable subscription. I don't believe this to be the case but if anyone knows where I can find out in more details how this works I'd be grateful, if only because it would allow me to ask more specific questions of the DBAs/Server admins
    - my initial hunch was that it was something with the consumer not being set up fully (the .net code uses the consumer name to register both to dequeue messages and to subscribe to MessageAvailable notifications). Not I am told that this is not the case and that the consumer has been set up properly, but I'm still a little suspicious.
    Anyway, any help would be gratefully received.
    Pete

    Hi Pete,
    Together we may be able to work this out ... I have a good level of knowledge on the database side of AQ but know nothing about ODPAQ :)
    Have you seen the following documentation section? Could there be some restrictions on the production host on the ports?
    Oracle Data Provider for .NET opens a port to listen for notifications. HA events, load balancing, and database change notification features also share the same port. This port can be configured centrally by setting the database notification port in an application or Web configuration file. The following example code specifies a port number of 1200:
    <configuration>
    <oracle.dataaccess.client>
    <settings>
    <add name="DbNotificationPort" value="1200"/>
    </settings>
    </oracle.dataaccess.client>
    </configuration>
    If the configuration file does not exist or the db notification port is not specified, then ODP.NET uses a valid and random port number. The configuration file may also request for a random port number by specifying a db notification port value of -1.
    The notification listener, which runs in the same application domain as ODP.NET, uses the specified port number to listen to notifications from the database. A notification listener gets created when the application registers with OracleAQQueue.MessageAvailable event. One notification listener can listen to all notification types. Only one notification listener is created for each application domain.
    Thanks
    Paul

Maybe you are looking for

  • Customer in PSG from FI line item

    Hi, we need to get customer in PSG while creating an invoice in F-02, FB01,FB70... For example, the 1st line item: posting key 01, customer XXXXXX, the 2nd line item: posting key 50, revenue account XXXXXX. In the second line item we have PSG where h

  • Not to show the detail records even though the mater records are existing.

    Dear Oracle I would like not to show the detail records even though the mater records are existing. Is there any block preperty I can set? Thanks

  • Drill down on direct database request

    Hi all, I would like to know if its possible to drill down in a table created with a direct database request. I've created the direct request and run it perfectly, but drilling down is not enabled and I, even thought I've looked for it, I couldnt fin

  • JPasswordField in Solaris problem

    Hey all, I have a program that will be running on windows and solaris. This program contains a JPasswordField. On windows, the field is fine, and by that i mean, that there is no way i can copy the contents to another text field and view the contents

  • Ppt for client presentation

    Hi can u plz send poer point presentation sap sd sales process. plz send this mail id [email protected] zapakmail is not working. aditya