Messages in ISH queue

we are seeing messages queuing up in ISH mesage queue .
what is the best way to handle this situation ?
should i reduce the multiplexing factor ?
any experiences ?

Reducing the multiplexing factor is the best way to deal with a situation
where messages are queueing up in the ISH or WSH message queue.
<roopesh dubey> wrote in message news:[email protected]..
we are seeing messages queuing up in ISH mesage queue .
what is the best way to handle this situation ?
should i reduce the multiplexing factor ?
any experiences ?

Similar Messages

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

How to set up the maximum number of messages on a queue programmatically

Hi,
I am using IMQ 3.5 to implement a message layer for one of my projects. I created a "Job Status Queue", which receives job status report from a java application every minute. But I just want to keep the most current status report instead of all the job running history. How can I restrict the maximum number of messages to 1 programmatically?
Any suggestion or help will be appreciated.
Xiaoyun Tang

You can't limit the destination size programmatically, but you can do it administratively and associate a behavior to occur when the limit is reached. In your case it sounds like you want a queue, 1 message deep, and to discard the oldest message when the queue is full. When you create the physical queue on the broker you can specify these attributes (you can also update them on an existing queue). For example:
imqcmd create dst -t q -n StatusQ -o maxNumMsgs=1 -o limitBehavior=REMOVE_OLDESTFor more information see Chapter 6 of the Message Queue Administration Guide. In particular the "Managing Destinations" section:
http://docs.sun.com/app/docs/coll/MessageQueue_35_SP1
Joe

How do i find the number of messages in a queue

Sorry if this is too trivial, but i haven't been able to figure out how to determine the number of messages in a queue. business case being that i can only have 3 messages in the send queue, so i need to stop sending if there are 3 outstanding messages still in the send queue.
Can someone point the way?
Thanks,
Nilesh

Hi,
To get the depth using JMS you must create a QueueBrowse and browse the entire queue. Its generally horribly inefficient if you want to do it with any regularity.
In Hermes I have had to write plugins that open separate connections to providers using their non-JMS APIs or JMX and get that kind of information that way.
Look at the getDepth() method in this JBoss plugin for an example that uses JMX:
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/jbossmq/JBossMQAdmin.java?view=markup
And here is one for WebSphereMQ that uses one of its many APIs..
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/mq/MQSeriesAdmin.java?view=markup
Colin.
http://hermesjms.com

Error while trying to pick message from weblogic queue

Hi,
We are getting the following error while trying to connect to pick up a message from weblogic queue.
We are suing oracle soa suite 10.1.3.1 and weblogic 8.1
the bad part is that, this error is not documented anywhere and couldn't get much help on this.
Would appreciate any suggestions / pointers on this.
Let me know if any further information is required.
invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: file:/E:/product/10.1.3.1/OracleAS_4/bpel/domains/default/tmp/.bpel_OTOCBPELProcess_1.0_78fcf080ec2bd7495aebfb5373e76116.tmp/readmsg.wsdl [ Consume_Message_ptt::Consume_Message(opaque) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
---------------------------------------------------

Hi!
I am facing a similar issue, does someone have an idea ?
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="detail"><detail>null</detail>
</part><part name="summary"><summary>file:/opt/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_TestReceiveMessage_BPEL_1.0_e00fd88d454889b871183d0d92dc9f7d.tmp/plReceiveMessage.wsdl [ Consume_Message_ptt::Consume_Message(TestPushMessage_BPELProcessRequest) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
Please examine the log file to determine the problem.
</summary>
</part></remoteFault>
Thanks,
romain.

Error while sending the messages to JMS Queue

Hi ,
I am trying to pick the file from JMS Queue and send the response xml as outbound message to JMS Queue again using XAI Sender
I Created XAI Sender, Outbound Message Type(DM-RCVRESP) and configured these two with External System.
I am able to pick the file from JMS Queue but unable to send the message through XAI Sender (Real-time)
Plz find below the error trace getting.
[Wed Jun 15 16:12:09 IST 2011] Error while processing sender "UPLOADSTG" : Unable to update response in staging table: Row id not given.
com.splwg.mpl.sending.SameThreadSendingManager$ProcessException
     at com.splwg.mpl.sending.SameThreadSendingManager.processDestination(SameThreadSendingManager.java:341)
     at com.splwg.mpl.sending.SameThreadSendingManager.sendResponse(SameThreadSendingManager.java:293)
     at com.splwg.mpl.sending.SameThreadSendingManager.doSend(SameThreadSendingManager.java:249)
     at com.splwg.mpl.server.async.ExecSendRequestProcessor.ProcessRequest(ExecSendRequestProcessor.java:61)
     at com.splwg.mpl.server.async.RequestProcessingThreadAdapter.run(RequestProcessingThreadAdapter.java:46)
     at com.splwg.mpl.server.PooledThread.run(PooledThread.java:91)
     at java.lang.Thread.run(Thread.java:662)
Please guide me in this regard..
Thanks,
sukumar

What have you configured for the response tab for the sender? Are you using the MPL or the MDB?
Take a look at:
MPL Best Practices (Doc Id 1308165.1)
Oracle WebLogic JMS Integration (Doc Id: 1308181.1)

TS3147 Since my last update for Mac OS X Lion 10.7.5 I have been unable to print to either my HP or Lexmark printers! Everything is connected but I get an "idle" message in the queue. I have "Reset printer system" and re-added these printers. No luck. H

Since my last update for Mac OS X Lion 10.7.5 I have been unable to print to either my HP or Lexmark printers! Everything is connected but I get an "idle" message in the queue. I have "Reset printer system" and re-added these printers. No luck. Help?

Hello,
It isn't the fw in Network you want o use or look at, that's for something completely different.
My first suspect is the Power Adapter on the LaCie has gone.
At the Apple Icon at top left>About this Mac, then click on More Info, then click on Hardware>Firewire, what is listed there?
Reset the Firewire bus
If your Firewire or USB isn't recognizing any device. A solution which has worked for some whose hard drive became invisible in 10.4 was simply to follow these four steps to reset the Firewire/USB bus:
1. Shut the machine down.
2. UNPLUG the power lead to the computer and any firewire/USB drive or devices.
3. leave it for 10 minutes.
4. Connect back up and reboot.
http://www.macmaps.com/firewirebug2.html

Mails/Alerts-triggered for messages stuck in queues and failed in moni

Hi,
I have two doubts.
1) Messages are getting stuck in smq2 of my ECC and PI system. I have to manually push them. Is there any mechanism in which we can get alerts/mails when messages get stuck in queues.
I have already gone through the blog /people/santhosh.kumarv/blog/2009/05/19/sap-xipi-alerts-for-queue-errors and I have implemented it in ECC system. But no mails were generated.
2)Is there any method in which I can get alerts/mails when a message fails in sxmb_moni of ECC system?
Thanks and regards,
Siji

Hi Sanjeev,
I made a report with the following code in it and executed it. So I think that should work even if the job for it is not scheduled. There were messages stuck in queue. But no alert was generated. I had also created alert category in ECC.
Thanks and regards,
Siji

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

Messages Stuck in Queue in PI

Hi,
For a few inbound interfaces for which PI is the middleware, we have found that the messages are stuck in queue in PI. We have also found that the messages are stuck in the queue in PI because one message which has an RFC error (It does a RFC lookup from PI into R/3).
Is there any way in which we can trigger the RFC lookup manually for the failed message in the queue in PI?
If this is not the right forum, please let me know the correct forum.
Thanks in advance.
Mick

Hi,
We can prevent this problem through standard SAP program RSQIWKEX. This program need to execute background. Whenever any message stuck in queue automatically this problem will restart error message automatically. If you want to delete error message from queue (due to this error message remaining messages are in hold stage. for remaining message execution we need to delete error message from queue) we need to change one function in this probem.
Existing function TRFC_QIN_RESET_LUW , this function only can restart error message.
Need to add function TRFC_QIN_DELETE_LUW , this function delete error message from queue.
For this program execution we need to mentioned queue name(mandatory), find message stucking queue name and give same name to program in variant.
I hope now clear

Messages stuck in queue AFWRecv of Adapter Framework

Hello,
Messages stuck in queue AFWRecv of Adapter Framework in our production system(trace in RWB: "to be delivered")
in URL http://xxxxxxx:50000/MessagingSystem/monitor/systemStatus.jsp we can see:
Queue Info
Queue Name isStarted QueueSize ThreadCount (working) MaxThreads
AFWCall true 0 0 (0) 20
AFWRecv true 954 10 (10) 10
AFWRqst true 0 0 (0) 20
AFWSend true 0 0 (0) 10
We have tried to resend the first message but that´the result:
Time Stamp Status Description
2010-10-09 11:24:06 Success The message was successfully received by the messaging system. Profile: XI URL: http://xxxxxxxxx:8100/MessagingSystem/receive/AFW/XI
2010-10-09 11:24:06 Success Using connection AFW. Trying to put the message into the receive queue.
2010-10-09 11:24:06 Success Message successfully put into the queue.
2010-10-11 00:01:46 Success Recovering from loss of connection to database; message loaded into queue by recover job: System Job (Failover Recovery)
2010-10-11 02:48:16 Success System Startup: Message successfully loaded into queue: AFWRecv.
2010-10-13 11:03:19 Success Admin action: Trying to redeliver message.
2010-10-13 11:03:46 Success Admin action: Trying to redeliver message.
Since then it stucks there...
Any help would be apreciated....

Hi,
Go to the runtime workbench --> Message Monitoring --> Click on the 'Configure Table Columns' > Check Sequence ID, Serialization Context & Sequential Number options.> and then click 'Apply'.
Then in the 'Serialization Context' column you will get the queue ID for the stcuk message.
Take that value and click on the 'Show additional Criteria' option on the top and put this value in the 'Serialization context' parameter. Also,select the start/end date as 'This year' --> start.
You will get all the messages stuck in that particular queue for this yoear, try to rectify them, so that your message will be processed.
-Supriya.

Messages in deliver queue

Hello everybody:
Is there any way to get the list of the messages that are in que deliver queue for a domain?
With hoststatus I can know the number of active recipients, but it would be useful sometimes to get the MIDs of the messages to process them individually with showmessage or removemessage.
If there's no way by now I think it would be a good improvement in future versions.
Thank you:
Salvador

Try using the "showrecipients" command.
> showrecipients
Please select how you would like to show messages:
1. By recipient host.
2. By Envelope From address.
3. All.
> help showrecipients
showrecipients host hostname
showrecipients [options] sender email
showrecipients all
Show messages from the queue.
options:
--match-case
Cause matching of the username portion of the email address to match in
a case-sensitive fashion. By default, it is case-insensitive.
Hello everybody:
Is there any way to get the list of the messages that are in que deliver queue for a domain?
With hoststatus I can know the number of active recipients, but it would be useful sometimes to get the MIDs of the messages to process them individually with showmessage or removemessage.
If there's no way by now I think it would be a good improvement in future versions.
Thank you:
Salvador

Messages in Distributed Queue remain on one JMSServer in Cluster

Hi,
          the situation is as follows:
          We're having Distributed Queues on a two-Node server setup. A queue therefore exists two times, once on each JMSServer on each node.
          Forward-Delay has been set on the DistibutedQueue to value 1 second (we tested with values 0 and 10, too).
          External Java client (both cluster nodes in the provider_url for initialcontext) connects to the DistributedQueue and sends messages. In the weblogic console you can see these messages on the physical queue on the JMSServer, let's call it QueueA on NodeA.
          An external java process to consume messages (again both clusters nodes in the jndi-connection-string) is started to consume messages. Because of round-robin it sometimes get's connections to QueueB (part of same DistributedQueue as QueueA, but on the other node in the cluster).
          When connected to QueueB on NodeB no single message is received. You can even see in the weblogic console that QueueA on NodeA has zero consumers and 50 messages, QueueB on NodeB has zero messages but one consumer.
          When we restart the consumer java process and it randomly get's connected to QueueA on NodeA it consumes fine, as it should.
          Should'nt Forward-Delay do exactly this? Transport messages from QueueA on NodeA with zero consumers to QueueB on NodeB which actually has consumers?
          Any help would be appreciated.
          Axel van Lil

Hi,
          thanks for your answer. We opened a support case today for this issue... I don't know. Cluster seems to run fine, no warnings, no exceptions.
          The next step of this issue is the following (just to give an idea of our upcoming problems :-)
          External Java process listens on QueueA on NodeA (QueueA is part of a Distributed Queue). Currently receives all the messages located on that queue. We kill NodeA on that machine to simulate failover.
          The external process failovers immediately to NodeB (which is good! proven by netstat and debugger) but just doesn't receive messages even though there are messages in that queue! It seems that the new consumer is just being forgotten by the BEA server.
          I don't know... somehow our configuration is quirked... or the BEA implementation doesn't work at all...
          Rgds,
          Axel

Messages in Buffered queue not beeing applied

Hi All,
Im running a streams environment. The receiving server crashed and was restarted. The apply process was restarted and the buffer was flooded with messages. Flow control initiatied on the sending database. The apply process doesn't show errors, but there are 5001 messages in the queue that arn't beeing applied. I' ve tried restarting the apply process and increased the number of parallel apply processes. Purging the queue doesn't seem like a good idea since the I will loose data. What can I do?
btw The messages in de queue seem to be in defered state. I dont know if this is of any importance...
Another thing that struck me as odd was the following:
Coordinator Low Watermark: 11063412548
Reader Oldest SCN: 11063412382
I would assume the Oldest SCN would be equal or higher that the Coordinator low watermark because messages are first beeing read, then coordinated then applied right?
and while I' m at it: it is no longer possible to disable the queue from Grid Control. If I try to, what happens is, that the status becomes disabled (red downward arrow) but the state remains:"DEQUEUEING MESSAGES"
kind regards,
Erik
Edited by: erikros on Apr 28, 2010 2:47 PM
Edited by: erikros on Apr 28, 2010 3:05 PM
Edited by: erikros on Apr 28, 2010 3:08 PM

Query 1
APPLY_NAME : P_APP1
Latency in Seconds : 29139
Message Creation : 2010-04-27 14:48
Apply Time : 2010-04-27 22:54
APPLIED_MESSAGE_NUMBER : 11063412548
Query 2
CAPTURE_NAME : P_CAP1
STATE : PAUSED FOR FLOW CONTROL
CAPTURE_TIME : 2010-04-29 07:41
CAPTURE_MESSAGE_NUMBER : 11063460122
CAPTURE_MESSAGE_CREATE_TIME : 2010-04-27 14:55
ENQUEUE_TIME : 2010-04-29 07:41
ENQUEUE_MESSAGE_NUMBER : 11063460122
ENQUEUE_MESSAGE_CREATE_TIME : 2010-04-27 14:55
AVAILABLE_MESSAGE_NUMBER : 11076534248
The second query had some fields in it that weren't supported by my version of Oracle 10.2. I replaced them with some others....
Edited by: erikros on Apr 29, 2010 8:24 AM

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

Messages in ISH queue

Similar Messages

Maybe you are looking for