Watch all queue message in xi/pi

Hello Experts,
I want to see all queue messages coming to xi and going out of xi. Is there any Tcode to watch queue messages.
I use SMQ1 and SMQ2 to see qRFC queue messages. But i want to see all messages.
Kindly help me in this regard.
Thanks in advance.

Hi tatireddy kiran
if you want to minitor on abap stack (integration engine) then run tcode SXI_MONITOR
fill up the crieteria and there you can search all the message whether its QOS is BE , EO or EOIO
if you want to monitor java stack (adapter engine )
then run tcode SXMB_IFR got to RWB -> message monitoring and there give the filter and you can see the messages and there status
Regards
sandeep

Similar Messages

ALL QUEUE messages are in memory? = OutOfMemoryError

I have very large queue about which contains messages about 1GB in size and above.
Can I configure Sun Java System Message Queue to swap incomming messages to disk if system has already NO FREE MEMORY. I use "-Xmx600m -Xms400m" and when I still sending messages to the queue the system will fail and it shows OutOfMemoryError!
Can somebody help me?

I'm using version 3.5SP1 to specify the correct system version. I'm persisting messages with default settings, so that they may be persistent. I currently using file based backend storage.
Do you mean that:
1. I must use database storage for messages to persist messages?
in reply to:
JSMQ does not currently support a disk only backed destination (where messages only occupy disk space).
2. you say that if number of my stored messages gets over same large number so system fails because it keeps some references to persisted messages?
I have two questions:
-- My system after I was send to it about 200000 persistent messages to one queue is restarting very long time. In log file is shown message "[B1136]: Processing stored transactions" and system is starting many many minutes (20 minutes and it still not started). Do you have any advice about it?
-- May I set property imqConnectionFlowCount to say 1 or 10 messages? Because I sending persistent messages?
I'm currently trying to configure properties file but system is still behaving the same way. Here is my properties file :
imq.instanceconfig.version=300
imq.autocreate.queue=false
imq.autocreate.destination.maxNumMsgs=0
imq.autocreate.destination.maxTotalMsgBytes=0
imq.autocreate.destination.limitBehavior=REMOVE_OLDEST
imq.autocreate.destination.maxBytesPerMsg=100k
Here is my log file: Every thread accepting means sending 10000 ObjectMessages, to see the system speed.
# 1092163502968 Do not modify this line
[10/VIII/2004:20:45:02 CEST] [B1002]: An existing property file for imqbroker was not found, no stored properties will be loaded
[10/VIII/2004:20:45:03 CEST]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Program Files\Sun\MessageQueue3\jre
[10/VIII/2004:20:45:03 CEST] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[10/VIII/2004:20:45:03 CEST] IMQ_HOME=C:\Program Files\Sun\MessageQueue3
[10/VIII/2004:20:45:03 CEST] IMQ_VARHOME=C:\Program Files\Sun\MessageQueue3\var
[10/VIII/2004:20:45:03 CEST] Windows XP 5.1 x86 localhost (1 cpu) JanVit�sek
[10/VIII/2004:20:45:03 CEST] Java Heap Size: max=194432k, current=16256k
[10/VIII/2004:20:45:03 CEST] Arguments:
[10/VIII/2004:20:45:03 CEST] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[10/VIII/2004:20:45:03 CEST] [B1060]: Loading persistent data...
[10/VIII/2004:20:45:03 CEST] Using built-in file-based persistent store: C:\Program Files\Sun\MessageQueue3\var\instances\imqbroker\
[10/VIII/2004:20:45:04 CEST] [B1136]: Processing stored transactions
[10/VIII/2004:20:45:04 CEST] [B1013]: Auto Creation of Queues is Enabled
[10/VIII/2004:20:45:04 CEST] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[10/VIII/2004:20:45:04 CEST] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[10/VIII/2004:20:45:04 CEST] [B1039]: Broker "imqbroker@localhost:7676" ready.
[10/VIII/2004:20:46:08 CEST] [B1065]: Accepting: [email protected]:1043->jms:1040. Count=1
[10/VIII/2004:20:46:08 CEST] [B1132]: Autocreating destination archivace [Queue]
[10/VIII/2004:20:46:33 CEST] [B1066]: Closing: [email protected]:1043->jms:1040. Count=0
[10/VIII/2004:20:46:46 CEST] [B1065]: Accepting: [email protected]:1045->jms:1040. Count=1
[10/VIII/2004:20:47:03 CEST] [B1066]: Closing: [email protected]:1045->jms:1040. Count=0
[10/VIII/2004:20:47:14 CEST] [B1065]: Accepting: [email protected]:1047->jms:1040. Count=1
[10/VIII/2004:20:47:30 CEST] [B1066]: Closing: [email protected]:1047->jms:1040. Count=0
[10/VIII/2004:20:47:52 CEST] [B1065]: Accepting: [email protected]:1049->jms:1040. Count=1
[10/VIII/2004:20:48:10 CEST] [B1066]: Closing: [email protected]:1049->jms:1040. Count=0
[10/VIII/2004:20:48:24 CEST] [B1065]: Accepting: [email protected]:1051->jms:1040. Count=1
[10/VIII/2004:20:48:35 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 116593K, 59% of total memory used
[10/VIII/2004:20:48:43 CEST] [B1066]: Closing: [email protected]:1051->jms:1040. Count=0
[10/VIII/2004:20:56:58 CEST] [B1065]: Accepting: [email protected]:1053->jms:1040. Count=1
[10/VIII/2004:20:57:14 CEST] [B1066]: Closing: [email protected]:1053->jms:1040. Count=0
[10/VIII/2004:20:57:32 CEST] [B1065]: Accepting: [email protected]:1055->jms:1040. Count=1
[10/VIII/2004:20:57:48 CEST] [B1066]: Closing: [email protected]:1055->jms:1040. Count=0
[10/VIII/2004:20:58:08 CEST] [B1065]: Accepting: [email protected]:1057->jms:1040. Count=1
[10/VIII/2004:20:58:26 CEST] [B1066]: Closing: [email protected]:1057->jms:1040. Count=0
[10/VIII/2004:20:58:39 CEST] [B1065]: Accepting: [email protected]:1059->jms:1040. Count=1
[10/VIII/2004:20:59:01 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 129524K, 66% of total memory used
[10/VIII/2004:20:59:01 CEST] [B1066]: Closing: [email protected]:1059->jms:1040. Count=0
[10/VIII/2004:20:59:23 CEST] [B1065]: Accepting: [email protected]:1061->jms:1040. Count=1
[10/VIII/2004:20:59:37 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 135379K, 69% of total memory used
[10/VIII/2004:20:59:44 CEST] [B1089]: In low memory condition, Broker is attempting to free up resources
[10/VIII/2004:20:59:44 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - allocated memory is 140700K, 72% of total memory used
[10/VIII/2004:20:59:46 CEST] [B1066]: Closing: [email protected]:1061->jms:1040. Count=0
[10/VIII/2004:21:05:37 CEST] [B1065]: Accepting: [email protected]:1063->jms:1040. Count=1
[10/VIII/2004:21:05:39 CEST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:1063,jms:1040] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4120]: Can not store message 6-127.0.0.1(a6:f4:b:1c:d1:a0)-1063-1092164737671 on destination archivace [Queue] because capacity of 100000 would be exceeded.
[10/VIII/2004:21:18:36 CEST] [B1065]: Accepting: [email protected]:1065->admin:1041. Count=2
[10/VIII/2004:21:19:23 CEST] [B1066]: Closing: [email protected]:1063->jms:1040. Count=1
[10/VIII/2004:21:19:25 CEST] [B1065]: Accepting: [email protected]:1067->jms:1040. Count=2
[10/VIII/2004:21:22:17 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 95760K, 49% of total memory used
[10/VIII/2004:21:22:41 CEST] [B1066]: Closing: [email protected]:1067->jms:1040. Count=1
[10/VIII/2004:21:23:18 CEST] [B1065]: Accepting: [email protected]:1069->jms:1040. Count=2
[10/VIII/2004:21:23:18 CEST] [B1132]: Autocreating destination mq.metrics.destination_list [Topic]
[10/VIII/2004:21:23:18 CEST] WARNING [B2007]: Creation of destination mq.metrics.destination_list failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4180]: Support for feature [B0048]: Monitoring Destinations is unavailable on destination mq.metrics.destination_list [Topic], please upgrade to the Enterprise Edition to enable this feature
[10/VIII/2004:21:23:19 CEST] [B1066]: Closing: [email protected]:1069->jms:1040. Count=1
[10/VIII/2004:21:24:52 CEST] [B1065]: Accepting: [email protected]:1071->jms:1040. Count=2
[10/VIII/2004:21:25:13 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 128040K, 65% of total memory used
[10/VIII/2004:21:25:19 CEST] [B1066]: Closing: [email protected]:1071->jms:1040. Count=1
[10/VIII/2004:21:26:13 CEST] [B1065]: Accepting: [email protected]:1073->jms:1040. Count=2
[10/VIII/2004:21:26:16 CEST] [B1089]: In low memory condition, Broker is attempting to free up resources
[10/VIII/2004:21:26:16 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - allocated memory is 136518K, 70% of total memory used
[10/VIII/2004:21:26:33 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 123849K, 63% of total memory used
[10/VIII/2004:21:26:45 CEST] [B1089]: In low memory condition, Broker is attempting to free up resources
[10/VIII/2004:21:26:45 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - allocated memory is 137529K, 70% of total memory used
[10/VIII/2004:21:26:49 CEST] [B1066]: Closing: [email protected]:1073->jms:1040. Count=1
[10/VIII/2004:21:30:21 CEST] [B1065]: Accepting: [email protected]:1075->jms:1040. Count=2
[10/VIII/2004:21:30:30 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0023]: ORANGE - allocated memory is 124839K, 64% of total memory used
[10/VIII/2004:21:30:34 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 124839K, 64% of total memory used
[10/VIII/2004:21:30:45 CEST] [B1089]: In low memory condition, Broker is attempting to free up resources
[10/VIII/2004:21:30:45 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - allocated memory is 138535K, 71% of total memory used
[10/VIII/2004:21:30:52 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 148807K, 76% of total memory used
[10/VIII/2004:21:31:04 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 152230K, 78% of total memory used
[10/VIII/2004:21:31:17 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 153114K, 78% of total memory used
[10/VIII/2004:21:31:25 CEST] [B1066]: Closing: [email protected]:1075->jms:1040. Count=1
[10/VIII/2004:21:34:06 CEST] [B1065]: Accepting: [email protected]:1077->jms:1040. Count=2
[10/VIII/2004:21:34:19 CEST] [B1088]: Entering Memory State [B0021]: GREEN from previous state [B0022]: YELLOW - allocated memory is 131047K, 67% of total memory used
[10/VIII/2004:21:34:26 CEST] [B1089]: In low memory condition, Broker is attempting to free up resources
[10/VIII/2004:21:34:26 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - allocated memory is 137901K, 70% of total memory used
[10/VIII/2004:21:34:47 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 151563K, 77% of total memory used
[10/VIII/2004:21:34:59 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 154979K, 79% of total memory used
[10/VIII/2004:21:35:12 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 153312K, 78% of total memory used
[10/VIII/2004:21:35:24 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 149201K, 76% of total memory used
[10/VIII/2004:21:35:33 CEST] [B1066]: Closing: [email protected]:1077->jms:1040. Count=1
[10/VIII/2004:21:37:30 CEST] [B1065]: Accepting: [email protected]:1079->jms:1040. Count=2
[10/VIII/2004:21:38:27 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 154146K, 79% of total memory used
[10/VIII/2004:21:39:05 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 154874K, 79% of total memory used
[10/VIII/2004:21:39:41 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 152984K, 78% of total memory used
[10/VIII/2004:21:39:41 CEST] [B1066]: Closing: [email protected]:1079->jms:1040. Count=1
[10/VIII/2004:21:41:56 CEST] [B1066]: Closing: [email protected]:1065->admin:1041. Count=0
[10/VIII/2004:22:57:17 CEST] [B1065]: Accepting: [email protected]:1081->jms:1040. Count=1
[10/VIII/2004:22:57:47 CEST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0023]: ORANGE - allocated memory is 153223K, 78% of total memory used
[10/VIII/2004:22:58:01 CEST] [B1089]: In low memory condition, Broker is attempting to free up resources
[10/VIII/2004:22:58:01 CEST] [B1088]: Entering Memory State [B0023]: ORANGE from previous state [B0022]: YELLOW - allocated memory is 156624K, 80% of total memory used
[10/VIII/2004:22:58:26 CEST] [B1088]: Entering Memory State [B0023]: ORANGE from previous state [B0024]: RED - allocated memory is 170012K, 87% of total memory used
[10/VIII/2004:22:58:49 CEST] [B1065]: Accepting: [email protected]:1083->admin:1041. Count=2
[10/VIII/2004:22:58:57 CEST] [B1066]: Closing: [email protected]:1081->jms:1040. Count=1
[10/VIII/2004:22:59:36 CEST] [B1125]: Pausing Destination archivace
[10/VIII/2004:22:59:53 CEST] [B1129]: Resuming Destination archivace
[10/VIII/2004:23:00:06 CEST] [B1065]: Accepting: [email protected]:1085->jms:1040. Count=2
[10/VIII/2004:23:00:28 CEST] [B1088]: Entering Memory State [B0023]: ORANGE from previous state [B0024]: RED - allocated memory is 174344K, 89% of total memory used
[10/VIII/2004:23:01:07 CEST] [B1066]: Closing: [email protected]:1083->admin:1041. Count=1
[10/VIII/2004:23:01:07 CEST] [B1088]: Entering Memory State [B0023]: ORANGE from previous state [B0024]: RED - allocated memory is 176741K, 90% of total memory used
[10/VIII/2004:23:01:40 CEST] [B1065]: Accepting: [email protected]:1087->admin:1041. Count=2
[10/VIII/2004:23:01:42 CEST] [B1066]: Closing: [email protected]:1085->jms:1040. Count=1
[10/VIII/2004:23:02:11 CEST] [B1066]: Closing: [email protected]:1087->admin:1041. Count=0
[10/VIII/2004:23:15:14 CEST] [B1047]: Shutting down broker...
[10/VIII/2004:23:15:14 CEST] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
[10/VIII/2004:23:15:14 CEST] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[10/VIII/2004:23:15:14 CEST] [B1077]: Broadcast good-bye to all connections ...
[10/VIII/2004:23:15:14 CEST] [B1078]: Flushing good-bye messages ...
[10/VIII/2004:23:15:29 CEST] [B1063]: Done
[10/VIII/2004:23:15:29 CEST] [B1048]: Shutdown of broker complete.
[10/VIII/2004:23:15:31 CEST]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Program Files\Sun\MessageQueue3\jre
[10/VIII/2004:23:15:31 CEST] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[10/VIII/2004:23:15:31 CEST] IMQ_HOME=C:\Program Files\Sun\MessageQueue3
[10/VIII/2004:23:15:31 CEST] IMQ_VARHOME=C:\Program Files\Sun\MessageQueue3\var
[10/VIII/2004:23:15:31 CEST] Windows XP 5.1 x86 localhost (1 cpu) JanVit�sek
[10/VIII/2004:23:15:31 CEST] Java Heap Size: max=194432k, current=16256k
[10/VIII/2004:23:15:31 CEST] Arguments:
[10/VIII/2004:23:15:31 CEST] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[10/VIII/2004:23:15:31 CEST] [B1060]: Loading persistent data...
[10/VIII/2004:23:15:31 CEST] Using built-in file-based persistent store: C:\Program Files\Sun\MessageQueue3\var\instances\imqbroker\
[10/VIII/2004:23:15:32 CEST] [B1136]: Processing stored transactions

How do you build a web page to display queued messages ?

How do you build a web page to display queued messages in all states?
Thanks,
Reeta
Reeta Joseph Benoy
EDS@XEROX
Database Administration
1350 Jefferson Rd
Rochester, NY 14623

You can build a form to a procedure in oracle portal that explores the queue with the option browse and prints de type message with htp package. I made it in this way and my applicattion works right. The procedure must loop the select count(msgid) from aq$[queuetable_name] times.

I just bought an HD movie on iTunes. Yesterday, I watched all but twenty minutes of it on my Dell laptop. Today, I tried to open it on the same laptop, and it told me my computer can't play HD movies, that I have to view it in SD. What is happening?

I just bought an HD movie on iTunes. Yesterday, I watched all but twenty minutes of it on my Dell laptop. Today, I tried to open it on the same laptop, and it told me my computer can't play HD movies, that I have to view it in SD. The error message said that my computer didn't have the capabilities, but I have several other HD movies that I have always and can still watch without issue. Just this one doesn't work. Why, and do you know how to fix this?

Apparently the display is required to be HDCP compatible to view HD movies in iTunes. My display isn't so this is my problem. I contacted Apple support and they have agreed to credit me for the HD movie and I have now downloaded the SD version.

Advantages of Using Queued Message Handler vs. Standard State Machine

Hello,
What are the advantages of using a Queued Message Handler? Also, why are they more powerful than using Standard State Machines?
Thanks!

They are really just sort of an extension of a state machine. The general idea is that you have one loop doing a specific job. You then use a queue to tell it how/when to do this job. For instance, I might have a log file loop. I will send it commands to open a file, write some data, write some more data, and finally close the file. Each of those commands are coming from the queue. The beauty with this setup is that anybody that can get a reference to that queue can send the command to that loop.
So the QMH is "better" than a state machine mostly because of the decoupling of functions. In a given application, I will have a loop for log file writing, GUI updates, reading of a DAQ, instrumenet communications, server communications, etc. Trying to do all of that in a single loop state machine is a major pain in the rear end. Seperating them out makes life so much easier.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Manage Queues - Messages are in Schedule status after upgrade to ERP2004

Hi,
We upgraded SAP to version ERP2004. ABAP proxy XI messages are in schedule status even though we deregister and register & activated all queues.
When I click on the queues it is in running status.
Does anyone has any idea where should I look?
Thanks in advance!
Mrudula

Hi,
my scenario is file to idoc....
I have set paraemter in SXMB_ADM as below.
Category Parameters CurrentValue DefaultValue
RUNTIME HTTP_TIMEOUT 100000 0
I have gone through as you suggested still when i double click on message in SXMB_MONI...i am getting Runtime Error (TIME_OUT).
Please do help me..
Thanks in advance.
Krish

Configure Monitoring of a MSMQ private queue Messages in Queue counter

Hi
I have a workgroup server that is not part of my local domain.
I have contented the server to my local SCOM 2012 R2 server and it is working fine.
My SCOM server has MSMQ 6.0 & 6.3 MP's installed.
On the remote servers I have some MSMQ 6.0 private queues.
When I am trying to monitor one counter in 1 queue , when the threshold is reached I am getting error message on al the queues.
On the performance counter tab I have :
Object: MSMQ Queue
Counter : Messages In Queue
Instance :[server name'\private$\error
There were 1207 messages in this queue .
I Got about 30 messages and error on all queues.
What did I do wrong ?
Itamar
Itamar

Hi
This is the alert email I got :
Alert: Notification Queue
Source: maasw1\private$\maas.backend.scheduler.timeoutsdispatcher
Path: MAASW1.xxx.com
Last modified by: System
Last modified time: 2/18/2014 2:45:49 PM Alert description: Instance Computer Queues
Object MSMQ Queue
Counter Messages in Queue
Has a value 19
At time 2014-02-18T14:45:35.0000000+02:00
I did not place a monitor on this queue but on 2 other queues.
one with threshold of 500 and on with 1 .
I have made some change in the monitor and will test it now.
Thanks
Itamar
Itamar

Not able to Read All the Message in the Topic

Hi Al,
i am new to JMS. I have implemented publish-subscribe model. Topic as a destination.
I want to read all the message available for particular topic. is there any way to get this?..
like in the Queue, QueueBorrower used to read all available messages in the queue.
Thanks
Raj

It depends on what you mean by "what messages are available on the topic".
if you want to know what messages would be delivered to a new consumer on the topic, then you can simply create a consumer yourself. Each messages on a topic is delivered to all subscribers, so by creating a consumer yourself you won't be interfering with the delivery of messages to other consumers. (That's not possible with queues which is why the queue browser is provided).
If you want to know what messages are "persisted in the topic" then there's not really such a concept. Messages sent to a topic are only persisted in individual durable subscriptions created for individual clients. If there are no durable subscriptions when messages are not persisted. The JMS APi doesn't provide a way to browse the messages saved in an individual durable subscription. It could, but it doesn't.
Nigel

Queue messages stalling

We have an oracle advanced queue which stores messages to be sent via email. A process picks them off and sends them onto our mail service. Something in the chain stalls occasionally, and nothing is dequeued to the exception queue. Everything on the queue has a retry count of 1 when it should try 5 times. The state is also set to 1 for all the messages on the queue. An update of the queue table, resetting the state and retry count to 0 kicks the whole thing back into life again.
Can anyone help me or explain what I am doing wrong?
Thanks
Jennifer

mark42324 wrote:
I want all messages to remain in queue until they are scanned for both spam and virus.Added in Messaging Server 6.3:
"Two new values now have meaning for the various SPAMFILTERx_OPTIONAL MTA options: 3 and 4. A value of 3 causes spamfilter failures to accept the message but queue it to the reprocess chanel for later processing. A value of 4 does the same thing but also logs the spam filter temporary failure to syslog."
So you would add spamfilterX_optional=3 to option.dat where X is the number matching the SpamAssassin filter slot (1,2,3... etc.).
Regards,
Shane.

Equal opportunities for all queues

Hi!
My application receives messages from several queues. I use separate MyListener instance for every queue. I synchronized the onMessage method on static Object, so only one message from all queues is processed in given moment:
MyListener implements MessageListener
static Object object;
onMessage (Message message)
synchronized (object)
//process
Do the "synchronized" and "onMessage" promise equal opportunities for all input queues? Can you give a link to relevant documentation?

According to the JMS specification, a session is a single threaded context that shields applications from worrying about thread safety. So if you create all the queue receivers from the same session, you shouldn't need to synchronize onMessage. To promote equal opportunities, you'll want to synchronize as little as possible - but this is really a JMS implementation issue and you'll probably need to experiment a little to find out if any starvation occurs.
- Bjarne.

Where to store data (queued message handler)

Hello,
i'm developing an image processing application. As a template i'm using the 'queued message handler'. In my app I need to store some images, arrays, and so on in RAM. Now the question is if i should store that data in the message loop's shift register (in a cluster) or somewhere else.
At the moment i have hidden front panel indicators where i store all my data. This isn't good practise, is it?
thanks alot
MN

nollMarvin wrote:
Hello,
i'm developing an image processing application. As a template i'm using the 'queued message handler'. In my app I need to store some images, arrays, and so on in RAM. Now the question is if i should store that data in the message loop's shift register (in a cluster) or somewhere else.
At the moment i have hidden front panel indicators where i store all my data. This isn't good practise, is it?
thanks alot
MN
No that is not good practice.
A Shift register is a much better place to store data in memory it does that without creating copies the OS must interperate for display. (Yeah the displaying of data to a user is a different concept than having data in memory) Ben's famous Action Engine Nugget is always a good read. http://forums.ni.com/t5/LabVIEW/Community-Nugget-4-08-2007-Action-Engines/m-p/503801
And a basic concept to LabVIEW that attending a training session (or asking questions on these forums) will help you master
Jeff

IPad iOS 8.2 still won't allow delete of ALL email messages at once?

iOS 8.2 still won't allow deletion of ALL email messages at once from my iPad? What could be the reason for this? The work-around solutions I see on Internet work erratically for me.
I'm an Android cellphone user so can delete all emails from my phone with a click or two. Is that a patent issue for Apple? There is no way to delete ALL email messages easily?

Had the same problem. There is an undocumented way under another thread and it works, but is clunky and very un-Mac-like.
The Apple thread that I got the undocumented answer from is:
Delete all email in Inbox iOS7
https://discussions.apple.com/thread/5421295?start=15&tstart=0
I've copied the answer below:
From inbox edit
MARK ALL AS READ (for me and several others in the thread it only works, when I marked all as read)
Highlight first email
Hold move button
Try to unhighlight first email (probably won't )
Still holding move button pull down on mails and then try to unhighlight first email again
This time it should
You will notice the inbox seems frozen as move is no longer highlighted and individual emails will not highlight if you touch them
Wait May take a minute or two depending on how many emails are in your inbox but they will move to the right side
Then just touch trash
The YouTube link that demonstrates this is:
http://www.youtube.com/watch?v=fKa-KFjUIGE
Hope this helps!
Cheers!
Anika

JMS Queue Messages not picked up.

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

Delete queued messages

Hi all,
We have IMS 5.2 running Solaris8. I am investigating the smtpout log files, the status attribute for the email shows that it cab be E for enqued, D for Dequed or some other status with error sending to the other smtp destination. Now in the imsimta queue management, if I need to delete only the emails with error status, how can I do this? I mean if I run the "held" sub command then delete it will not delete all the emails with error status, and if I run the "directory channel" then delete then all the emails will be deleted regardless of the status. Is there a solution ?
Many thanks in advance

I would first lengthen the "backoff" stuff, so queued messages don't get retried so often.
You can also reduce the notices timeout, though I would go gently, so you don't return valid mail for servers that may actually be down.

Interface Message acknowledge() method acknowledges this and all previous messages received.

Hi,
          I use a JDBC datastore to hold messages in a queue. When I receive a message
          off the queue, there is a flag that says True or False. If True, I want to
          put the message back onto the queue without acknowledge. If False, I want
          to acknowledge. My session instantiation looks like this:
          qsession = qcon.createQueueSession(false,Session.CLIENT_ACKNOWLEDGE);
          Currently, I receive messages by correlation ID in order to filter messages
          based on the flag. First, I receive all messages with False. Those messages
          I will acknowledge. Then, I receive messages with True. This group of
          messages will not be acknowldeged. Instead, I use qsession.recover. The
          messages are put back on the same queue after forwarding them to another
          process. The process will return success or failure. If failure, the
          process will call again, and I'll resend the group of messages I just
          recovered.
          What I would like to have happen is to do this procedure in one loop, not
          two. Instead, I would rather get all messages, and check if True or False.
          If True, I would want to skip acknowledgement. If False, I would want to
          acknowledge. The problem is, the JMS Message.acknowledge method will
          acknowledge all the messages it received before.
          In BEA WebLogic, is there an ability to acknowledge a particular message,
          rather than all previous messages? If it is not possible, is the reason
          because the acknowledge underneath is actually like a database commit? Is
          there any other way to process these two types of messages given that I may
          need to keep one type around in case resending is necessary?
          Regards,
          Scott Lynch


          Scott Lynch wrote:
          > Hi,
          >
          > I use a JDBC datastore to hold messages in a queue. When I receive a message
          > off the queue, there is a flag that says True or False. If True, I want to
          > put the message back onto the queue without acknowledge. If False, I want
          > to acknowledge. My session instantiation looks like this:
          >
          >
          >
          > qsession = qcon.createQueueSession(false,Session.CLIENT_ACKNOWLEDGE);
          >
          >
          >
          > Currently, I receive messages by correlation ID in order to filter messages
          > based on the flag. First, I receive all messages with False. Those messages
          > I will acknowledge. Then, I receive messages with True. This group of
          > messages will not be acknowldeged. Instead, I use qsession.recover. The
          > messages are put back on the same queue after forwarding them to another
          > process. The process will return success or failure. If failure, the
          > process will call again, and I'll resend the group of messages I just
          > recovered.
          >
          > What I would like to have happen is to do this procedure in one loop, not
          > two. Instead, I would rather get all messages, and check if True or False.
          > If True, I would want to skip acknowledgement. If False, I would want to
          > acknowledge. The problem is, the JMS Message.acknowledge method will
          > acknowledge all the messages it received before.
          >
          >
          >
          > In BEA WebLogic, is there an ability to acknowledge a particular message,
          > rather than all previous messages?
          The is a FAQ. And no, BEA does not provide an "acknowledge-one"
          extension. It does provide an "acknowledge-previous" extension, via a
          connection factory configurable, but this won't help in your case.
          One common solution is to use a pool of multiple sessions (one per
          current message).
          > If it is not possible, is the reason
          > because the acknowledge underneath is actually like a database commit?
          No. BEA JMS is just following the JMS spec here.
          > Is
          > there any other way to process these two types of messages given that I may
          > need to keep one type around in case resending is necessary?
          Use multiple sessions.
          >
          >
          >
          > Regards,
          >
          > Scott Lynch
          >
          >
          >
          >

Watch all queue message in xi/pi

Similar Messages

Maybe you are looking for