Acknowledging individual message, leaving others in the queue

Hi,
I am trying to find a way to acknowledge some messages while leaving others on the queue but when I do call m.acknowledge() on the message I want to ack all the messages previously received are removed from the queue. I have read the doc and it seems to me like what I want to do is not possible, hence my post :/
The scenario is:
1. I have 2 messages on a queue
2. I receive message 1 and decide to keep it on the queue
3. I receive message 2, process it and acknowledge it
4. Both messages have been removed from the queue
Do you know how I could achieve the following behaviour:
1. I have 2 messages on a queue
2. I receive message 1 and decide to keep it on the queue
3. I receive message 2, process it and acknowledge it
4. Only message 1 is left on the queue
Thanks a lot,
Mickael

The behavior you are seeing is expected by JMS specification for javax.jms.Message.acknowledge().
Have you looked at MQ's com.sun.messaging.jms.Message.acknowledgeThisMessage() ?

Similar Messages

How to check if Message already exists in the queue and if message is processing currently

Hi everyone
I am new to Azure and worked on adding messages to the queue through workerrole1. Worker role 2 pulls them out from queue and processing them and de-queing them.
Worker role1 runs method gets called after every 10 seconds and puts messages in queue
CloudQueueMessage
message = newCloudQueueMessage(oAzureWorker.WorkerInstanceOf
+ "_"+ oAzureWorker.AgentId.ToString()
+ "|"+ ExecutionId.ToString());
queue.AddMessage(message);
Worker role2 runs method gets called after every 10 seconds too and checks the queue like this
foreach
(CloudQueueMessagemessage
inqueue.GetMessages(20,
TimeSpan.FromMinutes(5)))
// Process all (20) messages in less than 5 minutes, deleting each message after processing.
// Process message
queue.DeleteMessage(message);
Following are my questions
1) How do I check in worker role1 if the message is already in queue, Because I don't want to queue it back again if its not yet processed and is in the queue already
2) How do I check in worker role1 if the message is currently processing. Because I don't want to queue it back again.
3) How do I make sure that ALL the messages get processed in the order they are inserted. I know Queue is FIFO, but I know if the message gets delayed in processing another instance can pick it up, even if it gets picked up by another instance, I want to
make sure that the order remains.
Right now the instances of both these worker roles are 1, in the future when we increase them, I don't want them to queue the same messages multiple times or queue them if the message is already in process mode.

Hi Sarah,
I agree to the Frank's suggestion. Why you need to burden the worker role 1 to check if the message really sits on the queue or not? You can do this simply in your code before pushing it on queue instead querying queue.
All you need to do on worker role 1 is - push the message on the queue and forget as the entire queue design in azure is designed from asynchronous processing.
About worker role 2 - Use the GetMessage method which hides retrieved message's from other clients and hence makes sure that only one client is processing it at a time. If processing is successful - delete the message. if it is not - the message will be
visible anyways after the mentioned time provided in the GetMessage method.
I agree that when you will increase number of instances of your worker role 1 which might insert duplicates in the queue - in that case - you might need to introduce the shared entity (like database) and let all instances communicate through it to avoid
the duplication of messages on queue.
Bhushan | http://www.passionatetechie.blogspot.com | http://twitter.com/BhushanGawale

***Raising Alerts When the message is struck in the Queue

Hi Experts,
Is there any way of Raising Alerts When the message is struck in the Queue I want to notify the user if the message is struck in Queue(smq1,smq2).Please let me know the same.
Thanks,
Srinivasa

hi
you can trigger alert for any of the component failure.
for this u nees the ccms configuration.
than you need to configure in RZ20 and RZ21.
steps.
1. create alert category in ALRTCATDEF
2.enter long text
3. add fixed recepient.
4.go to RZ21.
5. select display overview for method
6. serch for method CCMS_Send_Alert_to_ALM.
7. copy the method and create ur own Z method.
8. open ur method.
9. under control tab select ONLY IN CENTRAL SYSTEM TRIGGERED BY CCMS AGENTS.
10. in parameter tab give ur alert cat created before.
11.under release tab select AUTO REACTION METHOD.
12. go to RZ20.
13. a list of system will be displyed select ur own xi system
14. now select the queue name for which u want to trigger alert.
15.goto property button and double click.
16. go to method tab and click on method assigment.
17. goto method radio button and assigne the method u created in RZ21.
done.....enjoy....
u can check the log in slg1 tcode
regards,
navneet

Backing Up and Restoring the Message Store v.s. the queue

Hello,
We are running iPlanet 5.2 Messaging Server and need to migrate to another (duplicate) 5.2 Messaging Server. We have all the software installed and the LDAP user accounts created. Now we just need to move the existing mail from one server to the other.
I found the Backing Up and Restoring the Message Store section in the Admin Guide says to back up and restore your data, Messaging Server provides the imsbackup and imsrestore utilities.
However I am wondering about the Queue?
Under <instance>/imta/queue
What is the difference between the Message Store
and the Queue? Can I just backup and restore the Queue using tar or cpio?
Thanks in advance for any advice.
Regards,
Tim

Hello,
We are running iPlanet 5.2 Messaging Server and need
to migrate to another (duplicate) 5.2 Messaging
Server. We have all the software installed and the
LDAP user accounts created. Now we just need to move
the existing mail from one server to the other.
I found the Backing Up and Restoring the Message
Store section in the Admin Guide says to back up and
restore your data, Messaging Server provides the
imsbackup and imsrestore utilities.
However I am wondering about the Queue?
Under <instance>/imta/queue
What is the difference between the Message Store
and the Queue? The Message Store is where messages get delivered to, so you can read them.'
The queue is where messages are temporarily stored, pending delivery to wherever they go.
You can use tar, cpio, or what have you for the queue. Stop the server first. . .
You then just restore the files to the new server. No need to restart or anything like that. Just dump the files in, and run
imsimta cache -sync
to tell the MTA to re-read the queue.
Can I just backup and restore the
Queue using tar or cpio?
Thanks in advance for any advice.
Regards,
Tim

EOIO messages got held in the queue

hi,
In our scenario we are sending an IDOC from SAP whenever a material is newly created in SAP to a third party file share location.
Please note that i have to maintain EOIO(requirement)at the same time when ever we send an IDOC from SAP,the status is set to HOLD in XI(and we know that this message is because it's predecessor got stucked in the queue)
But when we check the queue in SMQ2 it looks fine(no entries there)even then if an IDOC is send from SAP the status goes to HOLD.what could be the reason for this ?
RGds,
Vasanth.

Hi Michael,
we are going as per the blog.evrything looks ok but i could not cancel the message(last step)and we are getting the following error
Unable to cancel 1 of 1 messages; update the status
(reason it says:<i>Predecessor not in final state</i>)
If we could able to cancel that message hope the problem would be solved.
RGds,
Vasanth.
Message was edited by: Vasanthakumar Balasubramani

I have an iPhone 5 on the Sprint Network. My iMessaging seems to work when it wants to when sending a message to others on the Sprint Network. I can send an iMessage to someone on Verizon during the same time and it works just fine?

I have iPhone 5 on Sprint. My husband is also on Sprint and my iMessage to him seems to work whenever it wants. I can iMessage to friends who have Verizon at the exact same time I am trying to iMessage my husband and the iMessages will go to and from the Verizon friends just fine, but not to my husband. With him its not even pretending to send our messages as iMessages. The send bar isn't even blue to him. To me this seems like an issue with the Sprint Network, but I wanted to see if anyone had had the same/simmilar issues and it ended up being the phone.

I can tell you that with Sprint their coverage area isn't as good as Verizon or AT&T.
Are you sending these imessage while on wifi or cellular data? Also your husband would need to be in a good coverage area.
Usually when imessage is unavailable it will send it as a text. Does your husband receive your imessage as a text?

RZ21-CCMS Alerts in case the message is struck in the Queue

Hi all,
How to Configure an alert ,if the message is struck in the SMQ1,SMQ2 an alert needs to be generated and sent to multiple users.
eg:a.xyz.com,:b.xyz.com,:c.xyz.com...
In RZ21 I see there is an Option to send alert to only One receipent.How to Send the same to multiple receipents.
Thanks,
Srinivasa

hi potharaju,
the following blog shows the solution for the stuck EOIO messages-
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
regards,
alpa.

My iphone 4s is suddenly showing all my imessages as texts and i am not receiving any messages back. I am home, connected to our wifi and sending the messages to others in the house. any idea why?

My iPhone has suddenly started showing my imessages in green. I am home, connected to wifi and sending them to others in the house. Also I am not receiving their responses. Any ideas?

Apple is having server issues, hopefully to be resolved in the next 24 hours.

How to check the messages stuck up in the queues.

hi experts,
i have implemented the message queues in the EOIO form. if any message is stuck up in the inbound or the outbound queue. where would i will be able to check it.
i have the answers of checking it up in SXMB_MONI and runtime workbench.
is there any other way where i can get info about where the message has stuck up
regards,
Alpa.

Hi,
you could use transactions SMQ1 and SMQ2.
For more information:
XI Asynchronous Message Processing: Understanding XI Queues -Part I
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/frameset.htm
Regards
Patrick
Edited by: Patrick Koehnen on Oct 22, 2008 2:51 PM

Messages stuck in the queue... how do I make them to be processed again?

Hi,
I'm new to SAP PI and kinda confused with queues.
I have file -> bpm -> file scenario and there was an error in mapping within bpm process.
When I went to qRFC Monitor (smq2), I see that in XBQO$PE_WS90000002 queue,
there's an error, 'Permanent error in BPE inbound processing'... which is expected.
Now, I run the interface scenario again several times but they don't get processed
but stuck in the same queue. At this stage, I didn't know what to do...
I thought by deleting the error message, other messages will be processed...
I deleted the error message but the other messages are still in the queue...
I have two questoins.
1. What is the best way to handle an error in the queue... can I just delete it? or is there a better way to handle an error in the queue?
2. After deleting the queue, what should I do to make the other messages to be processed again...
Thank you.
-Won

Hi Won,
There are programs for restarting the LUW entries:
programs
· RSARFCRD: tRFC Monitor (transaction SM58)
· RSARFCSE: Restart an LUW (background job)
· RSARFCEX: Restart tRFC LUWs (background job)
· RSQOWKEX: Restart QOUT qRFC LUWs
· RSQIWKEX: Restart QIN qRFC LUWs
· RSARFCSE: Delete an LUW (background job)
· RSARFCER: Delete various LUWs
Also, check the url:
http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm
Hope this helps.
Regards,
Sushama

Messages waiting in the queue for long time.

Hi Experts,
We are having some Production issue - messages were waiting in the queue for long time and we found the errors in defaultTrace.12.trc file -
Please help how to solve this issue its production and we need to move forward and solve this issue asap.
XI AF API call failed. Module exception: (No information available). Cause Ex
ception: 'JDBC Adapter configuration not initialized: null'.
Thrown:
com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'JDBC Adapter configuration not
initialized: null'.
        at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
        at com.sap.aii.af.service.api.AdapterAccess.call(AdapterAccess.java:99)
        at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:87)
        at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47)
        at com.sap.aii.mapping.lookup.SystemAccessor.call(SystemAccessor.java:115)
        at com.sony.pi.sp.StoredProceduresHandler.runScalarStoredProcedure(StoredProceduresHandler.java:86)
        at com.sap.xi.tf._MyPage_Invoice_SAP_to_Loyalty_MM_.invokePROC_CUSTOMER_DEDUP$(_MyPage_Invoice_SAP_to_Loyalty_MM_.java:1272)
        at sun.reflect.GeneratedMethodAccessor384.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.sap.aii.mappingtool.tf3.rt.C2CFunctionWrapper.cacheContext(C2CFunctionWrapper.java:91)
        at com.sap.aii.mappingtool.tf3.rt.C2CFunctionWrapper.gotoNextContext(C2CFunctionWrapper.java:44)
        at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.cacheQueue(Q2QFunctionWrapper.java:86)
        at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.gotoNextContext(Q2QFunctionWrapper.java:41)
        at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.cacheQueue(Q2QFunctionWrapper.java:74)
        at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.gotoNextContext(Q2QFunctionWrapper.java:41)
        at com.sap.aii.mappingtool.flib3.CollapseContexts.gotoNextValue(CollapseContexts.java:52)
        at com.sap.aii.mappingtool.flib3.CollapseContexts.gotoNextContext(CollapseContexts.java:37)
        at com.sap.aii.mappingtool.tf3.rt.AResIterator.gotoNextContext(AResIterator.java:37)
        at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.gotoNextContext(FunctionWrapper.java:37)
        at com.sap.aii.mappingtool.flib3.IfWithoutElse.gotoNextContext(IfWithoutElse.java:58)
        at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:266)
        at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:326)
        at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:326)
        at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:415)
        at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142)
        at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118)
        at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
        at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92)
        at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
        at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
        at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)

Hi All,
CPACache refresh worked for one day and the same problem repeated again next day, but need to have parmanent fix and should know the root cause of the problem so that the problem can not be repeated again.
Is there any solution other than CPACache refresh and JDBC adapter stop and start to fix the issue.
And also found some entries in SM12 lock entry list during the same schedule time when the messages was triggered and remains for long time. Let me know whether we can delete those locks ?
user PIAFUSER
Lock mode E
and table SXMSPMAST
with lock argument ......
Any suggestions and tips help us alot in fixing this issue.
Thanks in advance
Gary.

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

MDB messages dont get processed from Queues when involving a remote Topic in transaction

Using WLS 6.1 SP4 on winXP Pro boxes, I have come across a peculiar problem:
          I have several MDBs that process ObjectMessages from queues and forward their payload (wrapped in another new ObjectMessage) to other queues, all of which are located within the same WLS server.
          Right now I'm adding a new MDB that gets messages from a remote Topic with a durable subscription, and forwards the payload to local queues after some processing.
          When the Topic is local as well, there is no problem. But when the Topic is set up in a remote machine, only the MDB that has the remote durable subscription works the way it should. It receives the remote message and forwards it to the corresponding local queue. But then the messages in those local queues dont get processed. The 'Messages Received' count rises and the 'Messages' count stays at 0, as if the messages had been correctly processed and acknowledged, but no onMessage() method is called besides the one from the MDB that has the durable subscription to the remote Topic (I can tell because there's no further processing from the queue those messages get put in). It's as if those messages were simply received and acknowledged without being passed to other MDBs by WLS.
          * All queue MDBs use Required container-managed transaction management and auto-acknowledge
          * All queue MDBs have default durability for their queue subscriptions
          * The topic MDB has a durable subscription stored in a filestore
          * Lookup of the remote Topic is done via JNDI
          Since the processing and forwarding of messages occurs the way it should when everything is local, I am inclined to believe one of two things:
          a) There's some issue with the way WLS treats messages (or even just payloads) when they come from a remote server
          b) WLS is doing something I'm not aware of when propagating a transaction that begins with the delivery of a message from a remote JMS Topic when it involves further forwarding of messages in local JMS Queues.
          Any help will be appreciated.
          regards,
          .munir estevane


Is the durable subscriber forwarder rolling back its transactions?
          That would cause the behavior you describe (eg the message gets
          placed in the queue, but is never made visible). What do
          the pending counts on the destination queue look like?
          Munir Estevane wrote:
          > Using WLS 6.1 SP4 on winXP Pro boxes, I have come across a peculiar problem:
          >
          > I have several MDBs that process ObjectMessages from queues and forward their payload (wrapped in another new ObjectMessage) to other queues, all of which are located within the same WLS server.
          > Right now I'm adding a new MDB that gets messages from a remote Topic with a durable subscription, and forwards the payload to local queues after some processing.
          >
          > When the Topic is local as well, there is no problem. But when the Topic is set up in a remote machine, only the MDB that has the remote durable subscription works the way it should. It receives the remote message and forwards it to the corresponding local queue. But then the messages in those local queues dont get processed. The 'Messages Received' count rises and the 'Messages' count stays at 0, as if the messages had been correctly processed and acknowledged, but no onMessage() method is called besides the one from the MDB that has the durable subscription to the remote Topic (I can tell because there's no further processing from the queue those messages get put in). It's as if those messages were simply received and acknowledged without being passed to other MDBs by WLS.
          >
          > * All queue MDBs use Required container-managed transaction management and auto-acknowledge
          > * All queue MDBs have default durability for their queue subscriptions
          > * The topic MDB has a durable subscription stored in a filestore
          > * Lookup of the remote Topic is done via JNDI
          >
          > Since the processing and forwarding of messages occurs the way it should when everything is local, I am inclined to believe one of two things:
          > a) There's some issue with the way WLS treats messages (or even just payloads) when they come from a remote server
          > b) WLS is doing something I'm not aware of when propagating a transaction that begins with the delivery of a message from a remote JMS Topic when it involves further forwarding of messages in local JMS Queues.
          >
          > Any help will be appreciated.
          >
          > regards,
          > .munir estevane

Scheduled delivery of individual messages

I've ready through the forum and have found a way to deliver a JMS message at some point in time by setting the producer:
          ((weblogic.jms.extensions.WLMessageProducer) qsender).setTimeToDeliver(cal.getTime().getTime());
          However, I do NOT want to affect every message sent by the producer, as this method seems to do.
          I want to be able to set a time of delivery for individual messages. Is this the purpose of the DeliveryTime header? How do I set this properly; will this work:
          objectMessage.setLongProperty("DeliveryTime", deliverDate.getTime())
          thanks!

This is how I've solved the problem of setting a delivery time for individual messages. My unit tests confirm it works as expected, it just feels like a hack.
          public void publish(Message message, Date absDeliveryTime) {
          // reset the timeToDeliver for the publisher
          // as the previous call may have set this
          ((WLMessageProducer) publisher).setTimeToDeliver(-1);
          if (absDeliveryTime != null) {
          Date timeNow = new Date();
          ((WLMessageProducer) publisher).setTimeToDeliver(
          absDeliveryTime - timeNow.getTime());
          }

Re: MDB messages dont get processed from Queues

Is the durable subscriber forwarder rolling back its >transactions?                    I receive no log messages or any behavior that would make me think the
          transaction was rolled back. The messages arent being returned to be
          redelivered and there's no trace of that in the log files (unless there's a
          special log for EJB transactions i havent looked at)
          >What do the pending counts on the destination queue >look like?
          The Messages Pending count on the queue stays at 0, as the Messages Current
          count.
          That same count on the durable subscriber forwarder (on the Topic's stats)
          still displays messages and bytes pending.
          (I had checked previously though, and it seems thats a bug in weblogic stats
          recording for MDBs in transactions and durable subscriptions to topics).
          thanks,
          .munir


Hi Munir,
          I don't know what is happening. In case you haven't already done
          so, I suggest putting in trace statements in your application to
          make sure that it is actually invoking the code
          you think it is. If that doesn't help, please create a simple
          reproducer for the problem and contact customer support.
          Tom, BEA
          Munir Estevane wrote:
          >>Is the durable subscriber forwarder rolling back its >transactions?
          >
          >
          > I receive no log messages or any behavior that would make me think the
          > transaction was rolled back. The messages arent being returned to be
          > redelivered and there's no trace of that in the log files (unless there's a
          > special log for EJB transactions i havent looked at)
          >
          >
          >>What do the pending counts on the destination queue >look like?
          >
          >
          > The Messages Pending count on the queue stays at 0, as the Messages Current
          > count.
          > That same count on the durable subscriber forwarder (on the Topic's stats)
          > still displays messages and bytes pending.
          > (I had checked previously though, and it seems thats a bug in weblogic stats
          > recording for MDBs in transactions and durable subscriptions to topics).
          >
          >
          > thanks,
          > .munir
          >
          >

Acknowledging individual message, leaving others in the queue

Similar Messages

Maybe you are looking for