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

Similar Messages

QueueBrowser not scaning all messages in JMS queue (ie not showing inprogre

Hi all,
I am using JMS in jboss-3.2.3, when scaning for pending messages i am using QueueBrowser.
But QueueBrowser not scaning all messages in JMS queue (ie not showing inprogress message)
But i need to know all messages including ongoing messages..
Antone plz help me
I am using Queuesender and QueueReceiver ..But some Exception or Error causes my JMS server(QueueReceiver listening for onMessage()) hanged up..and not responding to remaining messages...So i need to find pending messags in JMS queue..How can find?
Now i am using QueueBrowser to get list of pending msgs in queue... But doesn't contains Message which passed for processing (called onMessage())
.. But i need to find this also..How can?
Thanks,
Thilsen

You're right in thinking that the behaviour you describe looks wrong.
Take a look at the QueueBrowser interface which can be used to inspect a queue. You get one using QueueSession.createBrowser(Queue). The QueueBrowser allows you to scan a queue without consuming the messages. However note that the state of the queue may change while you're observing it through the QueueBrowser so what you see might not always be a 100% accurate representation of the queue at any given time.
Other things to check:
- message selectors - are you setting a message selector on your queue receiver which is resulting in not all of the messages 'matching'.
- expired messages - are you setting a time-to-live on the messages that you publish.
Hope this helps,
David Ingham
http://www.arjuna.com

Queue sometimes not picking the message

Hi,
In my project from JCD I am calling jar methods when needed when I call methods with parameters it will create xml and keep in queue. And the queue has to process the message. Every thing is working fine but some times queue suddenly stops pickinh the message from queue. When I undeploy the preoject and deploy it again then its picking again.
Please let me why queue not picking message some times.

Hi,
I am assuming you are dealing with standard SeeBeyond queues here (as opposed to MQ). And, in your case, you are saying a JCD or an activity is not picking up messages from a queue? Can you see these messages on the JMS server? What version of JavaCAPS are you using? (this does not matter much, though). What is the volume of the messages?
-Sri

SOA 10g JMS adapter does not pick up large messages in Oracle AQ

I am using SOA 10g 10.1.3.4 MLR #9. When I enqueue a large JMS message ( of type SYS.AQ$_JMS_TEXT_MESSAGE ) into the AQ from SOA 11g it goes into the TEXT_LOB portion of the USER_DATA column in AQ. In addition to this GROUPID and GROUPSEQ do not seem to get set. When that happens, my JMS adapterfrom SOA 10g does not seem to dequeue the message. But if I enqueue the same message using sql and set the GROUPID and GROUPSEQ my JMS adapter from 10g picks up the clob message.
How do we make the 10g adapter always pick up the large message in TEXT_LOB? I don't have this problem when the message is small because it goes into TEXT_VC field instead of TEXT_LOB field.

We are having this problem and have not figured it out yet. We need help. An oracle SR is opened but no progress from Oracle yet. I need to get some traction on this so anyone's help is appreciated. Our suspicion is that the AQ client in the wls 10.3.1 is incorrectly choosing to put the xml payload in TEXT_LOB even though the character size is less than 4000.
Here is a summary of our observations....
Today we did some testing with our old 6.3.1 OSM environment and our new 7.0.2 environment. We tested each against our QA1 environment and then our QA2 environment. Scenrio 1 is our problem. Scenario 2,3,and 4 all behave similar to each other. Why does Scenario 1 behave differently. It is causing AIA a problem when it dequeues the message.
Scenario 1:
We pointed our 7.0.2 OSM/Weblogic 10.3.1/Out of the Box AQ (which is part of our QA1 environment) to send messages to the AIA AQ table in our QA1 environment. The AIA database uses ALT32UTF8 character set. We don't know what character set the 7.0.2 OSM/Weblogic/AQ uses. Wehn we sent messages to the AIA QA1 table we saw that everything under TEXT_LEN 1000 went to TEXT_VC, Over 1000 went to TEXT_LOB. This is causes AIA to throw an exception if the message is over 1000 when it dequeus the message, because it thinks it shoudl look in the TEXT_VC which is null for AIA.
Scenario 2:
We pointed our 7.0.2 OSM/Weblogic 10.3.1/Out of the box AQ (which is part of our QA1 environment) to send messages to the AIA AQ table in our QA2 enviornment. The AIA database uses UTF8 character set. We don't know what character set the 7.0.2 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA2 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.
Scenario 3:
We pointed our 6.3.1 OSM/Weblogic 9.2.1/Custom AQ Solution (which is part of our QA2 environment) to send messages to the AIA AQ table in our QA2 environment. The AIA database uses UTF8 character set. We don't know what character set the 6.3.1 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA2 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.
Scenario 4:
We pointed our 6.3.1 OSM/Weblogic 9.2.1/Custom AQ Solution (which is part of our DEVINT1 environment) to send messages to the AIA AQ table in our QA1 enviornment. The AIA database uses ALT32UTF8 character set. We don't know what character set the 6.3.1 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA1 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.

JMS Adapter is not picking messages from Topic ( AIA Error Notification)

Hi All,
One of my service is not picking messages from topic. This service was working in one environment but not working in this environment.
I am using AIA 2.5 and using AIAErrorNotification.
Service AIAAsyncErrorHandlingBPELProcess is enquing the message but consumer service AIAReadJMSNotificationProcess is not being invoked automatically.
Whenever we are manually invoking this service, then this service is dequing messages from topic.
Is any have any clue for this?
Thanks in Advance.
Edited by: vikky123 on Dec 22, 2010 1:46 PM

Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

JMS Queue is not accepting requests after restarting the weblogic server

Hi,
JMS queue is able to receive message after redeploying the application or restarting the weblogic server. It is intermittent , not happening every time.
Please suggest how to resolve this issue. do we missed any configuration settings we are missing at clinet side or server side.
we are using Weblogic 92 MP2 version.
thanks.
[email protected]

I assume you meant "is unable to receive messages".
Are you getting any exceptions in the code, or errors in the log, or is nothing happening when you know there's a message on the queue to be read?
Are you perhaps reading from a distributed destination?

Mbean that listen for jms queue messages

Hi to all,
          I must use a Jmx notification listener architecture to trap when a new message arrives (i must also handle the message content) in a weblogic jms queue.
          Do you know which mbean could help me to observe the new ariving message?
          In the javadocs i cant' find any useful mbean to do that..
          Thanks

Hi to all,
          I must use a Jmx notification listener architecture to trap when a new message arrives (i must also handle the message content) in a weblogic jms queue.
          Do you know which mbean could help me to observe the new ariving message?
          In the javadocs i cant' find any useful mbean to do that..
          Thanks

Restarting foreign server, messages not picked up.

Hi,
I have a setup wherein a local weblogic 10 instance attempts to pull messages off a remote weblogic 10 queue, via Spring JMS.
The local weblogic has a JMS module configured with a 'Foreign Destination', via JNDI.
Both the local and the remote weblogic servers are clustered. When the local weblogic is started up, it picks messages normally and hums along. However, if the remote weblogic is restarted, messages remain on the remote weblogic queue and are not consumed.
If the local weblogic is then restarted, messages are consumed as normal.
I can provide more details as needed.
Does anyone have any ideas?
Thank You

Hi,
This question has come up before in this newsgroup. It's usually advantageous to use standard WebLogic JEE MDBs to consume from WebLogic destinations, as MDBs are specifically designed to work well in this use case: for one, they will automatically ensure that all members of a clustered destinations are serviced by consumers. Search this newsgroup for the keyword "Spring" for details.
Tom

SP15, JMS Sender, "Messages not fetched"

JMS Sender Communication Channel, Transport Protocol "Access JMS Provider with JNDI" and Name of JNDI initial ContextFactory "com.sonicsw.jndi.mfcontext.MFContextFactory".
Error in Adapter Monitor "Sender channel. Details: Last Exception during send at Sat Mar 11 07:55:45 EET 2006: Value with name enableDynConfigSender not available."
There is messages in SonicQ Queue but they are not fetched by XI. I've start/stop SAP XI Adapter: JMS, no help.
What does that error actually mean and what should I check next?

Hi Tapio,
If you are on SP14, SAP has introduced 'dynamic headers' with this support Pack. Your problem may be related to this. See the related section in SAP Note#856346 (JMS Adapter - FAQ)
To fix your problem try deactivating your sender communication channel, make a small change to your description and activate it again. Test your scenario to see if it works.
Hope this helps.
Regards,
Sam Raju

DB Adapter: Message not picked up

Hi,
I have an iConnect 10g working fine with the FTP adapter. Messages come through no problem. But now I'm trying to use the DB adapter to publish a message. I have the adapter running and cannot see anything wrong in the logs, but whenever I create and publish a message (and commit afterwards) I can the message appearing in the MESSAGEOBJECTTABLE and the AOTABLE, but the adapter doesn't pick it up.
What can cause this?
Arjan

Hi,
Did you see any errors in the DB adapter log file? Connection errors?
What is your logging level on the adapters set to? In the adapter.ini file, set the "agent_log_level=2".
Merlin is correct regarding when your DB Adapter message is not published.
Some other checks to make are these:-
Log on via SQL*Plus to your publishing database, connecting to the OAI user (usually OAI/OAI) and do:-
select count(*) from oai.aotable;
and
select count(*) from oai.messageobjecttable;
If there is the same number of records on there, and your publishing adapter hasn't pick them up, then run this:-
select APPLICATIONTYPE from oai.messageobjecttable;
This should be the same as your publishing adapter name.
Hint: in adapter.ini check the entry for "application= "
e.g.
// Application (as created in iStudio) that this Adapter corresponds to.
application=DB1
If they are different, or if APPLICATIONTYPE is null, then this is caused because you need to specify the "srcAppName" when you call your publish
procedure.
If you send me a mail to [email protected] I'll send you a complete worked, yet simple, DB Adapter to DB Adapter example and code which may help you.
Rene,
It is worth noting that ordinarily, the OAI schema has absolutly nothing to do with a subcribing DB adapter. The OAI schema contains the AOTABLE and MESSAGEOBJECTTABLE (MOTABLE), and the AGENT package which creates the message for the publishing event. That is it. The OAI schema does not usually "consume" the subcribed message, and therefore should never end up in the AOTABLE or MOTABLE.
The target schema to where the subcribed DB message will be posted to is the schema you will define in the DB Adapters "adapter.ini" file.
Specifically the entries below this line in your adapter.ini
// Application (spoke) database schema #1 writer information
Do you have any errors in your log files? The message cannot have just disappeared. Your FTP Adapter must be throwing an error somewhere, or your DB Adapter must be complaining.
Please can you check you log files for both adapters. If there are any strange errors let us know.
What type of document are you trying to publish using the FTP Adapter? XML? D3L? If XML, then check out the post "istudio publish event & xml ftp adapter" on this forum.
Again, if you drop me an email, then I can send you my DB Adapter to DB Adapter example which may help.
Yan

Copy JMS (queue) message

          I have a MDB receiving messages from a queue on a MQ. In the onMessage method or
          some where down the thread, I want to send the same message to a different queue,
          also on a MQ. I tried to send it in the same thread or a new thread. It never
          seemed complain but the receiver never gets it. It's as if the message was never
          sent.
          What's preventing the messages being sent?
          I'm using WLS 8.1 and MQ 5.2.
          TIA,
          Bill


          It turns out only one attribute (messageID) seems to matter in this app so that's
          taken care of but it's obviously not a clean solution. "You do what you got to
          do."
          Thanks for the help.
          Tom Barnes <[email protected]> wrote:
          >Hi Bill,
          >
          >This is vendor dependent and should work fine
          >with WebLogic, in your case you are receiving
          >from MQ and forwarding to MQ, and apparently
          >MQ has problems here.
          >
          >One thing that won't work with any vendor is
          >multi-threaded access to the same message -
          >which I don't think you are doing.
          >
          >There is no standard way to clone a message - you
          >will need to create a new message and copy
          >over the old message's fields into it. WebLogic
          >does this for you internally if you pass
          >an MQ message to a WebLogic send.
          >
          >Tom
          >
          >Bill wrote:
          >> Found the reason for the difference - forwarding the original message
          >to another
          >> queue changes the message (destination, etc). With a separate thread,
          >the main
          >> process just had time to get the info out before they are changed.
          >>
          >> Is there anyway to "clone" a message or something to that effect?
          >>
          >> "Bill" <[email protected]> wrote:
          >>
          >>>I have to apologize, Tom. The messages were actually sent but I had
          >a
          >>>selector
          >>>on the receiver. When tested outside of the app, I had the sender satisfy
          >>>the
          >>>selector. The testers were written quite a while back I just forgot
          >about
          >>>the
          >>>minor details...
          >>>
          >>>However, now that messages are copied and received, I have another
          >problem.
          >>>
          >>>The messages are sent OK with or without a new thread (the receiver
          >gets
          >>>them).
          >>>However, the rest of the processing in onMessage, which parses out
          >the
          >>>message
          >>>and processes it, doesn't work properly if the copy message was done
          >>>in the same
          >>>thread. Basically the sender of the original message doesn't like the
          >>>reply and
          >>>I couldn't see any difference by looking at the messages. Any ideas?
          >>>
          >>>Thanks,
          >>>Bill
          >>>
          >>>Tom Barnes <[email protected]> wrote:
          >>>
          >>>>If the MDB is transactional, it may be rolling back the tx.
          >>>>
          >>>>Or it may be that your app code is throwing a run-time
          >>>>exception (which would force a recover or rollback).
          >>>>
          >>>>It may be that the send is never getting called,
          >>>>(instrument your code).
          >>>>
          >>>>It may be that you are calling send, but accidentally
          >>>>you are using "transacted" session. Make sure that
          >>>>the first parameter to "createQueueSession()" is false.
          >>>>
          >>>>Tom
          >>>>
          >>>>Bill wrote:
          >>>>
          >>>>>I have a MDB receiving messages from a queue on a MQ. In the onMessage
          >>>>
          >>>>method or
          >>>>
          >>>>>some where down the thread, I want to send the same message to a
          >different
          >>>>
          >>>>queue,
          >>>>
          >>>>>also on a MQ. I tried to send it in the same thread or a new thread.
          >>>>
          >>>>It never
          >>>>
          >>>>>seemed complain but the receiver never gets it. It's as if the message
          >>>>
          >>>>was never
          >>>>
          >>>>>sent.
          >>>>>
          >>>>>What's preventing the messages being sent?
          >>>>>
          >>>>>I'm using WLS 8.1 and MQ 5.2.
          >>>>>
          >>>>>TIA,
          >>>>>Bill
          >>>>
          >>
          >

Workcenter message not picking contract

Hi All,
I am working solman 7.0 configured incident management serives desk and support notification messages are getting logged from ECC to Solman workcenter along with contract determination . But as we know message can be logged directly from workcenter while i am logging from workcenter contract determination not happening .
Regards
subbaraju

Hi samantha,
              I installed Solman7.0 Ehp1, sucessfully finished after i configured SAPROUTER, MOPZ,SERVICE DESK, Now i am activating SOLMAN_WORKCENTER, unfortunately could not displaying " I activated "AGS*" related all the services above 25 services. but page could not displaying
then check all the services for "TEST SERVICES" this also "CONNECTION TIME OUT ERROR showing"
          1. smicm t-code value is 6000 there.
          2. I activated all the servies also
          3. added roles also 3 roles.
anybody giveme solution please.

Messages not being processed

Hi,
I experience an issue with 10g soa, about not having processed some messages sent to receive activities of my process.
I have my process deployed, I can initiate the instance of the process, I can move the flow of the process by calling some receive activities, but sometimes it seems it stucks on one of these receives. It happens randomly on various processes on various receive activities, like one day one receive operation doesn't proceed at all, and on another day it is another receive operation, and that is without any change to the process and redeployment.
I can see the message has been received by server, because I can query it from DLV_MESSAGE table from BPEL data source, and i see its STATE = 0, which is unprocessed. I am also sure that message has valid content and the correlation bits on the message are also correct, really there is no reason why such message should not be processed, it always worked until the moment it decides not to for unknown reason.
My question:
1. What causes messages to be not processed?
2. What are known options to deal with this situation?
Currently I am in a condition where I can spot unprocessed messages, which is fine, so I am aware of the problem, but I am not able to deal with the problem. Even if I tried to submit the message via BPEL Console, it was not processed either.
Thank you for any suggestions

Some blog information to support this case
http://soacrux.blogspot.com/2010/08/automatic-recovery-program-for-pending.html
Content repaste:
Automatic recovery program for pending BPEL call back messages
BPEL engine maintains all async call back messages into database table called dlv_message. You can see such all messages in BPEL console call-back manual recovery area.The query being used by bpel console is joined on dlv_message and work_item tables.This query simply picks up all call back messages which are undelivered and have not been modified with in certain threshold time.
Call-back messages are processed in following steps
BPEL engine assigns the call-back message to delivery service
Delivery service saves the message into dlv_message table with state 'UNDELIVERED-0'
Delivery service schedules a dispatcher thread to process message asynchronously
Dispatcher thread enqueues message into JMS queue
Message is picked up by MDB
MDB delivers the message to actual BPEL process waiting for call-back and changes state to 'HANDLED=2'
So given above steps, there is always possibility that message is available in dlv_message table but MDB is failed in delivering it to BPEL process which keeps message always in state= 0.
Following program can be tailored to suite one's own requirements to recover from such state-0 messages.
Note:- This program contains logic to recover from invocation and call-back messages. Please comment out appropriately.
package bpelrecovery;
import com.oracle.bpel.client.*;
import com.oracle.bpel.client.util.SQLDefs;
import com.oracle.bpel.client.util.WhereCondition;
import java.util.ArrayList;
import java.util.Hashtable;
import java.util.List;
import javax.naming.Context;
public class bpelrecovery {
public bpelrecovery() {
public static void main(String[] args) {
bpelrecovery recover = new bpelrecovery();
String rtc = "";
try{
rtc = recover.doRecover();
catch (Exception e){
e.printStackTrace();
rivate void recoverCallbackMessages(List messages)
throws Exception
String messageGuids[] = new String[messages.size()];
for(int i = 0; i < messages.size(); i++)
ICallbackMetaData callbackMetadata = (ICallbackMetaData)messages.get(i);
String messageGuid = callbackMetadata.getMessageGUID();
messageGuids[i] = messageGuid;
System.err.println((new StringBuilder()).append("recovering callback message =
").append(messageGuids).append(" process
[").append(callbackMetadata.getProcessId()).append("(").append(callbackMetadata.getRevisionTag()).ap
pend(")] domain [").append(callbackMetadata.getDomainId()).append("]").toString());
Locator locator = getLocator();
IBPELDomainHandle domainHandle = locator.lookupDomain();
domainHandle.recoverCallbackMessages(messageGuids);
public String doRecover() throws Exception{
// Connect to domain "default"
try{
System.out.println("doRecover() instantiating locator...");
Locator locator = getLocator();
System.out.println("doRecover() instantiated locator for domain " +
locator.lookupDomain().getDomainId());
// look for Invoke messages in need of recovery
StringBuffer buf1 = new StringBuffer();
WhereCondition where = new WhereCondition(buf1.append(SQLDefs.IM_state).append( " = "
).append(IDeliveryConstants.STATE_UNRESOLVED ).toString() );
System.out.println("doRecover() instantiating IInvokeMetaData... with where = "+ where.getClause());
IInvokeMetaData imd1[] = locator.listInvokeMessages(where);
System.out.println("doRecover() instantiated IInvokeMetaData");
// iterate thru the list
List l1 = new ArrayList();
for (Object o:imd1){
l1.add(o);
// See how many INVOKES are in the recovery zone
System.out.println("doRecover() instantiated IInvokeMetaData size = " +l1.size());
// look for Callback messages in need of recovery
StringBuffer buf = new StringBuffer();
where = new WhereCondition(buf.append(SQLDefs.DM_state).append( " = "
).append(IDeliveryConstants.TYPE_callback_soap ).toString() );
System.out.println("doRecover() instantiating ICallbackMetaData... with where = "+
where.getClause());
ICallbackMetaData imd[] = locator.listCallbackMessages(where);
System.out.println("doRecover() instantiated ICallbackMetaData");
// recover
List l = new ArrayList();
for (Object o:imd){
l.add(o);
recoverCallbackMessages(l);
catch (Exception e){
e.printStackTrace();
return "done";
public Locator getLocator(){
System.out.println("getLocator() start");
Locator locator = null;
// set JNDI properties for BPEL lookup
String jndiProviderUrl = "opmn:ormi://localhost:6003:oc4j_soa/orabpel";
String jndiFactory = "com.evermind.server.rmi.RMIInitialContextFactory";
String jndiUsername = "oc4jadmin";
String jndiPassword = "welcome1";
Hashtable jndi = new Hashtable();
jndi.put(Context.PROVIDER_URL, jndiProviderUrl);
jndi.put(Context.INITIAL_CONTEXT_FACTORY, jndiFactory);
jndi.put(Context.SECURITY_PRINCIPAL, jndiUsername);
jndi.put(Context.SECURITY_CREDENTIALS, jndiPassword);
jndi.put("dedicated.connection", "true");
try{
System.out.println("getLocator() instantiating locator...");
locator = new Locator("default", "welcome1", jndi);
System.out.println("getLocator() instantiated locator");
catch (Exception e){
System.out.println("getLocator() error");
e.printStackTrace();
return locator;

How to remove messages from JMS Queue?how to configure queue in spring?

Hi
I have Confiured a JMS configaration in spring applicationConfiguaration.xml file
<bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="tcp://localhost:61616"/>
<property name="useAsyncSend" value="true"/>
</bean>
<bean id="queue" class="org.apache.activemq.command.ActiveMQQueue">
<constructor-arg value="foo"/>
</bean>
<bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
<property name="config" value="classpath:activemq.xml" />
<property name="start" value="true" />

</bean>
<bean id="auditInterface"
class="org.springframework.jms.remoting.JmsInvokerProxyFactoryBean">
<property name="serviceInterface" value="com.infiniti.gpn.auditing.AuditInterface"/>
<property name="connectionFactory" ref="connectionFactory"/>
<property name="queue" ref="queue"/>
</bean>
<bean id="listenerContainer" class="org.springframework.jms.listener.SimpleMessageListenerContainer">
<property name="connectionFactory" ref="connectionFactory"/>
<property name="destination" ref="queue"/>
<property name="messageListener" ref="auditMessageListener"/>
</bean>
Sender is sedning messages continusly messages that messages r storing in queue , these r acupying more memory in RAM , due to that jboss is restarting for each request, is there any way to clean up messages in Queue ? if it is there then how will configure that queue in apllicationConfiguaration.xml file?
Thanks in advance
Nara

Hi,
Even i have a similar kind of requirement where in, i want to clear the JMS Queue Message programmatically, on certain condition.
i am using Spring JMS. The JMS Queue has a listener. In the listener we want to clear the Queue contents based upon the condition.
If anybody has any idea about this, please reply back.
Thanks in Advance.
Manjunath.

JMS queues

Hi Group,
We have scenarion JMS to File, using SAP Pi as JMS provider,configured sender JMS channel to pick up the message from queue,some times the message in queues are not picking up and strucking in the queue,is there any way we can tune or adjust
queues to pick up the messages immediately.Also is there JMS queues prioritization option available within 7.1 version.
Regards,
Rajiv

Hi,
depending on the JMS provider check question
3. Provider specific Issues from
Note 856346 - J2EE JMS Adapter: Frequently Asked Questions (FAQ
>>>Also is there JMS queues prioritization option available within 7.1 version.
yes:
http://help.sap.com/saphelp_nwpi71/helpdata/en/59/25ee41c334c717e10000000a155106/content.htm
>>>>there any way we can tune or adjust queues to pick up the messages immediately
yes
check service :XPI Service: AF Core
where you can change the number of queues per adapter (so JMS for example)
http://help.sap.com/saphelp_nwpi71/helpdata/en/a7/c3d341c4cbc317e10000000a155106/content.htm
hope this helps,
Regards,
Michal Krawczyk

JMS Queue Messages not picked up.

Similar Messages

Maybe you are looking for