Delay messages being placed on a queue.

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

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

Similar Messages

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

Generating Alert Message XML file and placing it in Queue

Hello Team,
I want the alert mechanism to generate the Alert file in XML format and it should be placed in the Queue it is the requirement of the client and it should be done without the help of the BPM can any one suggest me is this scenario can be done and if it can be done then please suggest me how can we do it.I have also refereed http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/10/23/customize-e-mail-body-and-subject-in-alerts-in-sap-pi-731-java-stack-only-part-1-esr this link of customized alert mail but i want that attached file of email to be placed in the Queue and also without using BPM.
I am also thinking is it possible to combine multiple interfaces without using BPM.
Please help me in this issue thanks very much in advance.
Regards,
Avinash.

Hi Avinash,
One option is genrate customize alert as per blog, pick the alert email from mail box and place in the desired queue with another interface.
So you have two flow
customize alert interface to create customize alert and send the message to mail box
Pick the alert from mail box and place in the queue
regards,
Harish

** 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

Cases where messages are not being consumed from a queue

MQ 4.0
I have a cluster of 3 brokers. Java clients use RANDOMIZE to connect to the cluster of brokers. Message selectors are not used. My consumers are all synchronous, and connection.start() is called prior to calling MessageConsumer.receive().
What I have seen on random occassions are messages not being consumed from the queue. The problem seems to be sporadic.
I was thinking that the reason it is sporadic is because of the RANDOMIZE configuration of the client connetion / object-store.
That is, there is a possibility for the following to happen:
1) There were messages produced on a queue on broker A, but before these messages were consumed, all the consumers have been shutdown. Thus, the messages on queue stayed on broker A .... and have not been copied / clustered to the other brokers in the cluster ( As per online documentation, a queue is "copied" to other brokers only when there is a consumer for that queue on the other brokers ).
2) Then the client applications started up produced and consumers again. This time, the producers were all connected to broker B, and all consumers for the queue were also connected to broker B.
3) Because there are no other consumers for the queue on the other brokers, the messages in the queue on broker A are never consumed.
Can someone confirm that this is a possibility ?

Well ... it does seem to be the case.
I changed the object-store so that instead of using RANDOMIZE for imqAddressListBehavior, it uses PRIORITY. Therefore, all clients ( producers and consumers ) will connect to only 1 broker out of the 3 in the cluster.
After restarting all JMS clients with the new imqAddressListBehavior, there were messages in various queues in the other brokers that were not being consumed, because there are no longer any consumers on any of the other brokers.
All the messages in that broker that all JMS clients connect to are being consumed ...
Except for about 6 messages that stays in the queue for whatever reason. All consumers receiving with receive( 10000 ), and after consuming all messages above the 6, it returns without any more messages in the queue.
Well ... so much for cluster of brokers. I'll have to think of an alternative.

BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

Hi All,
I have a BPM interface running fine since 1 year.
In this BPM I have wait step for 5 minutes.
But yesterday message is stopped on wait and not proceeding ahead.
I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
Regards

Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

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

CcBPM: Message outbound status, Message being sent

Hi
I have a message with status flag message being sent at the outbound status PE since 30 days. Because of this message many messages got blocked with scheduled on outbound side status.
I tried to delete work items related to the message in SWWL, but i am not able delete.
Please suggest solution
Regards
Subba Rao

Hi velidi subba rao,
Please go to SMQ2 and right click on the entry and Select Save to LUW. It saves it to SMQ3. You will be able to reprocess it from there.
Give it a try and let me know if it worked. Also just release the queues once you have saved the message that is stuck.
Regards,
Jannus Botha

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
          >
          >

Stopping delayed messages from going out

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

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

Why is This message being relayed?

I have my relay settings to only accept 127.0.0.0/8 and 192.168.88.0/24, so how did this message get through?
Dec 5 19:55:34 mycompany postfix/smtp[24709]: 6852E91833E: to=<[email protected]>, relay=cluster4.us.messagelabs.com[216.82.250.19]:25, delay=256, delays=0.01/0.01/69/186, dsn=2.0.0, status=sent (250 ok 1323136534 qp 15594 server-5.tower-87.messagelabs.com!1323136279!47765957!1)
This weekend I found that someone was sending thousands of spam messages through my server even though I use authentication.

You need to look further back in your logs for the answer.
Dec 5 19:55:34 mycompany postfix/smtp[24709]: 6852E91833E: to=<[email protected]>, relay=cluster4.us.messagelabs.com[216.82.250.19]:25, delay=256, delays=0.01/0.01/69/186, dsn=2.0.0, status=sent (250 ok 1323136534 qp 15594 server-5.tower-87.messagelabs.com!1323136279!47765957!1)
The 'Accept SNMP relays...' option only relates to blind/untrusted relaying - if a connection comes from these IP addresses then accept the message, but that's not the only method that postfix will allow. If a user authenticates against the server (using one of the authentication methods you've selected) then they can also relay mail, regardless of their IP address.
Therefore, my first guess would be that someone's guessed a valid username/password on your server and is therefore using an authenticated connection. This can happen easily if users don't have strong passwords.
You'll need to track back through your logs to find where this message was injected into the mail queue. Start off by searching for that message ID (6852E91833E) in the logs, or look back in time (this message has been in the queue for 256 seconds. Eventually that will tell you where it came from, and what user authenticated the connection. Then shut down that account until you can change that user's password and educate them on how to choose effective passwords.

HT1495 How do I stop SMS messages being shared between multiple iphones on my itunes account? One is my wife's, one is mine and we do not want each others messages appearing on the other.

How do I stop SMS messages appearing on two devices on my iTunes account?
One phone is mine, one is my wife's and we dont want messages being shared.
We do have contacts and music etc shared.

If your are recieving mixed information on your phone on multiple devices this is going to be related to iMessage.
On your phone navagate to settings > messages > send and receive.
Check the information in that section make sure it relates to your AppleID and your phone. If you share a AppleID with the individual create a new AppleID for their device and insert that information.
If the numbers don't remove turn of iMessage restart your phone and turn it back it.
If all else fails disable iMessage otherwise turning it off is the quickest fix.

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

Messages getting stuck in QRFC Queue

Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
Hans

Hi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi

Messages stucked in moni with queue status as "RUNNING"

Hi All,
Few of messages stucked in moni with queue status as "RUNNING" from the past 6 to 7 hours. all the stucked messages running on same dialog instance app server 03 (ucobpi03_PIP_03). i checked PIP appserver its working fine.
Can any one please expalin me how to clean the queues..is there any effect of other queues ?
Thanks,
Siva.

Hi,
it can be due to multiple reasons....
check the interface logic built ...it can be either due to this or can be of large volume of data...
Also check the queues have been registered or not...
HTH
Rajesh

Delay messages being placed on a queue.

Similar Messages

Maybe you are looking for