Large Message picking Wrong Queue.....???

Hi,
We are processing a large message of size around 50 MB and its going to queue XBTO9. But i want it to be processed through XBTM.
Can someone please reply of how can it be done.
Thanks
Sourav

Its in KB...
Parameter EO_MSG_SIZE_LIMIT
Meaning
   The parameter EO_MSG_SIZE_LIMIT enables you to process messages of a
   particular size in series. 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 an extra queue.
   The prefix for the outbound queue of the Integration Server is XBTM, for
   all others it is XBTL.
   This parameter is designed to improve performance since there is not
   usually enough memory to process multiple large messages simultaneously.
   Serial processing ensures that the main memory only has to process one
   large message at a time, while smaller messages and processes continue
   to be processed uninterrupted.
Possible Values
   0 - 2,097,151 (KB)
   Note: 0 means deactivated (no messages are processed in an extra queue);
   the maximum value 2,097,151 corresponds to the value of roughly 2 GB.
Nilesh

Similar Messages

Large Message Payload - Queue selection

Hi,
I have one message with payload size around 105MB when I am trying to send through XI this message gets failed in the queue (inbound) of integration engine saying some memory problem to process the message. I have seen the queue it is picking up some XBT09_000 but I want to use the queue XBTL* as this queue is for large messages. The whole thing is that when my message is around 100MB I want it route large message processing queue i.e XBTL*. Is there anyway to do this? Any help on this greatly appreciated.
Thanks.,
Daniel.LA

There is a way to defer large messages from the rest and process them using a job in a specific queue.
Please check this configuration :
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm</a><a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/14/8024">Message Selection Filter</a>
in this path:
Under Runtime - > Integration engin ->
Prioritized Message Processing
Queues for Prioritized Message
Good luck
Nimrod

Error while trying to pick message from weblogic queue

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

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

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.

MDB is not picking up messages in the Queue

Hi ,
I am trying to implement a MDB (Producer) , that acts as a Message Producer also . This MDB pickes up a message from a Queue and sends it to another Queue(Queue 2) after some processing. The MDB listening to the Queue 2 is not being able to pick this message.
The Weblogic console shows that the message is pending.
The transaction-type is Container and transaction-attribute is 'Required' for the Producer (MDB) ...
I am creating a QueueSession as con.createQueueSession(true, Session.AUTO_ACKNOWLEDGE) . I also tried specifying queuesession.commit() ...
even then the Message is not picked by the MDB listening on the other side...
Please help me out

any one

Message sitting in Queues for 30 minutes before MDB picks them up

We're seeing a situation where we place messages on a queue and a small percentage of them will sit on the queue for 30 minutes before being picked up by the MDB to process. Anyone see this before?
          Here is the background. We're running 3 distributed queues on a cluster of 4 Weblogic 8.1 sp3 servers. The 30 minute issue happens on all 3 queues on all 4 servers. Currently we do not see a pattern. It can happen at a busy hour and in the middle of the night with nothing going on. During a busy timeframe, we can get up to 50 msg that hangup over a few minutes; less than 5 minutes.
          Our Service is an enterprise email service where various clients send email request to us via EJB. The EJB puts an entry into the database and puts a request msg into the queue. The MDB pulls it off the queue sends it to an email subsystem and updates the database.
          We added log msgs in both the EJB and MDB to track messages and narrowed it down to the requests just sitting in the JMS queue. We DO NOT set a delivery time via setJMSDeliveryTime().
          As mentioned is happens anytime during the day (busy or idle), may go for days without occuring, on any of the 3 JMS queues, on any of the 4 cluster servers, and for any of the clients. It's consistantly 30 minutes. This occurs on a small number of requests, but is enough to concern our business owner.
          Any thoughts on possible problems or any thoughts on monitoring or tracking down the issue is greatly appreciated.
          Thanks. Later...
          - Wayne

One possibility is that the messages have already been pushed to an MDB instance in the JMS asynchronous consumer pipeline, but the MDB instance has stalled during message processing - which delays processing of the following messages. The waiting messages count as "pending" in the JMS statistics.
          You can reduce the number of messages in a JMS asynchronous consumer's pipeline via the "MessagesMaximum" connection factory setting (default is 10). First: create a custom connection factory with transactions enabled (to support transactional MDBs), and ack-mode set to "previous" (to support pub/sub MDBs), and MessagesMaximum set to its lowest possible value. Second: specify this connection factory's JNDI name in the MDB's weblogic descriptor.
          Tom, BEA

JMS Sender SAP JMS Provide large message problem

Hi,
we have configured a JMS sender channel to pick up messages from a queue hosted by our SAP JMS provider. Unfortunately a message of about 6 MB size isn't picked up. Smaller messages are picked up.
Has anybody experienced a problem like this before?
Kind regards,
Heiko

Hey,
I guess you are using XML messages:
We had some problems with large XML messages (e.g more the 10MB),
This is usally cause by memory problems.
There are some work-around, like increasing the memory usage of the application server.
The first thing you do is try to understand where the message stacked (in the ABAP/J2EE).
If this is a memory problem, changing the memory configuration can improve this,
but be aware that there are hardware limitation (32bit application server can use with one process only 2GB), therefore messages over 100MB probably will not pass trough XI.
If you have huge files (e.g more than 100MB)
You must develop a program that would split the large message into several small messages. the program can not be written in the XI, and should be written before the adapter. (you might install and use in this case the conversion agent)
If you are using a message with csv format (not XML),
than it is possible to configure the adapter to split every X lines
(no program need to be written)

Error while sending the messages to JMS Queue

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

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

Best practices for handling large messages in JCAPS 5.1.3?

Hi all,
We have ran into problems while processing larges messages in JCAPS 5.1.3. Or, they are not that large really. Only 10-20 MB.
Our setup looks like this:
We retrieve flat file messages with from an FTP server. They are put onto a JMS queue and are then converted to and from different XML formats in several steps using a couple of jcds with JMS queues between them.
It seems that we can handle one message at a time but as soon as we get two of these messages simultaneously the logicalhost freezes and crashes in one of the conversion steps without any error message reported in the logicalhost log. We can't relate the crashes to a specific jcd and it seems that the memory consumption increases A LOT for the logicalhost-process while handling the messages. After restart of the server the message that are in the queues are usually converted ok. Sometimes we have however seen that some message seems to disappear. Scary stuff!
I have heard of two possible solutions to handle large messages in JCAPS so far; Splitting them into smaller chunks or streaming them. These solutions are however not an option in our setup.
We have manipulated the JVM memory settings without any improvements and we have discussed the issue with Sun's support but they have not been able to help us yet.
My questions:
* Any ideas how to handle large messages most efficiently?
* Any ideas why the crashes occur without error messages in the logs or nothing?
* Any ideas why messages sometimes disappear?
* Any other suggestions?
Thanks
/Alex

* Any ideas how to handle large messages most efficiently? --
Strictly If you want to send entire file content in JMS message then i don't have answer for this question.
Generally we use following process
After reading the file from FTP location, we just archive in local directory and send a JMS message to queue
which contains file name and file location. Most of places we never send file content in JMS message.
* Any ideas why the crashes occur without error messages in the logs or nothing?
Whenever JMSIQ manager memory size is more lgocialhosts stop processing. I will not say it is down. They
stop processing or processing might take lot of time
* Any ideas why messages sometimes disappear?
Unless persistent is enabled i believe there are high chances of loosing a message when logicalhosts
goes down. This is not the case always but we have faced similar issue when IQ manager was flooded with lot
of messages.
* Any other suggestions
If file size is more then better to stream the file to local directory from FTP location and send only the file
location in JMS message.
Hope it would help.

Processing of large messages

Hi,
is anyone experienced in boosting performance of large message processing in XI? I've got messages of about 3MB size. Their processing in XI takes about 5 minutes. The respective mappings are quite simple. I have seen that I can configure a special queue for large messages but the usage of this queue doesn't help.
Kind regards,
Heiko

Hi,
3MB essage shouldnt be taking 5 mins for getting processed. IS there a lot of load on your Inegration Server?? In SXMB_MONI do you see the message in Waiting stage for a lot of time and then is it getting processed??
if so hen You can try to priotirize this particular message to be processed first
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413
cheers,
Naveen

OC4J 9.0.4: Problem receiving message from JMS queue

I've created an application which puts XML files in a JMS queue and try to get it out again. The enqueing (sending) is no problem, but when I dequeue from the same queue I receive nothing and if I don't specify a wait time the programs hangs.
If I create a QueueBrowser I can see there are messages in the queue.
Can someone tell me what I do wrong?
Here is the code of my dequeue action:
public String dequeue(int qName) throws RbsSysException
        final String method = "dequeue(int qName)";
        _log.debug(method);
        QueueConnection queueConnection = null;
        try
            queueConnection = _queueConnectionFactory.createQueueConnection();
            QueueSession queueSession = queueConnection.createQueueSession(false,
                    Session.AUTO_ACKNOWLEDGE);
            QueueReceiver queueRcv = queueSession.createReceiver(getQueue(qName));
            _log.debug("queue = "+ queueRcv.getQueue().getQueueName());
            // Due to bug 3376983 in OC4J We cannot use TextMessage if it exceeds
            // 64 kb. Therefore use ObjectMessage.
            Message msg = queueRcv.receiveNoWait();
            _log.debug("msg = " + msg);
            ObjectMessage objMsg = (ObjectMessage)msg;
            //ObjectMessage objMsg = (ObjectMessage) queueRcv.receiveNoWait();
            _log.debug("objMsg = " + objMsg);
            if (objMsg != null)
                return (String) objMsg.getObject();
            else
                return null;
        catch (JMSException je)
            throw new RbsSysException(je);
        finally
            if (queueConnection != null)
                try
                    queueConnection.close();
                catch (Exception any)
                    _log.error("Error while closing QueueConnection: ", any);
    }

Did you implement javax.jms.MessageListener and the method onMessage(Message)?
If you use onMessage() as wel as receive (or receiveNoWait() or receive(long)), the onMessage() can be called, while the main thread is blocking on a synchronous receive, so make sure you use only one of the two methods: onMessage() or receive.
Receive() blocks your thread until a message is published. So your program 'hangs' by design. Usually this is used when your program is waiting for a particular message. Otherwise use onMessage().
ReceiveNoWait() checks if something is in the queue at that very moment, so if nothing is there (yet), the main thread continues.
Hope this helps,
Lonneke

Handling large messages with MQ JMS sender adapter

Hi.
Im having trouble handling large messages with a MQ JMS sender adapter.
The messages are around 35-40MB.
Are there any settings I can ajust to make the communication channel work?
Error message is:
A channel error occurred. The detailed error (if any) : JMS error:MQJMS2002: failed to get message from MQ queue, Linked error:MQJE001: Completion Code 2, Reason 2010, Error Code:MQJMS2002
The communication channel works fine with small messages!
Im on SAP PI 7.11, MQ Driver is version 6.
Best Regards...
Peter

The problem solved itself, when the MQ server crashed and restarted.
I did find a note that might could have been useful:
Note 1258335 - Tuning the JMS service for large messages or many consumers
A relevant post as well: http://forums.sdn.sap.com/thread.jspa?threadID=1550399

Processing large message payload with weblogic JMS

Hi,
I have a requirement in my project to process 50MB-500MG-1GB file using the JMS queue.
We could able to process 50MB payload but it's talking almost 2-3min to post the message and 2-4min to consume the message. Are there any configurable parameters available to fine tune the JMS queue to handle large payload? or is there any limitation on the size of the queue to process ?
Please advise.
Thanks,
Sri

There is a way to defer large messages from the rest and process them using a job in a specific queue.
Please check this configuration :
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm</a><a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/14/8024">Message Selection Filter</a>
in this path:
Under Runtime - > Integration engin ->
Prioritized Message Processing
Queues for Prioritized Message
Good luck
Nimrod

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

Dear All,
We have an application that is running on Weblogic 10.3.
This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
Can anyone tell us why our expired messages don't seem to be deleted from the queues?
Tim

Thank you for the response Rene.
We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
We have set up the expiration scan time interval. See a portion of our config.xml below:
<jms-server>
<name>brokerJMSServer</name>
<target>AdminServer</target>
<persistent-store xsi:nil="true"></persistent-store>
<store-enabled>true</store-enabled>
<allows-persistent-downgrade>false</allows-persistent-downgrade>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
*<expiration-scan-interval>30</expiration-scan-interval>*
<production-paused-at-startup>false</production-paused-at-startup>
<insertion-paused-at-startup>false</insertion-paused-at-startup>
<consumption-paused-at-startup>false</consumption-paused-at-startup>
</jms-server>
<jms-system-resource>
<name>broker-jms</name>
<target>AdminServer</target>
<sub-deployment>
<name>EhrBrokerRequestQueue</name>
<target>brokerJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
We have set up the message expiration policy in our jms descriptor. See a portion below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<queue name="EhrBrokerRequestQueue">
<delivery-params-overrides>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>-1</redelivery-limit>
*<expiration-policy>Discard</expiration-policy>*
</delivery-failure-params>
<jndi-name>EhrBrokerRequestQueue</jndi-name>
</queue>
</weblogic-jms>
What could we be doing wrong?
Kind Regards,
Tim

Large Messages fail on Integration Engine

Hello Guys!
I have an integration scenario with <b>large</b> messages going from ECC to XI (RFC -> XI -> JDBC) and these messages frequently fail on Integration Engine (inbound queue SYSFAIL).
1) Can't XI process large messages?
OR
2) Is there an integration engine configuration parameter that limits message size? (<i>I think that's not the case, because sometimes I can manually restart a message that failed on a first attemp</i>)
OR
3) Is there an integration engine configuration parameter that limits processing time of a message?
Thanks
Julio

Hi Julio,
i think you can click on the sysfail to get more info. Check as well SM21 for the error. Assumedly it was too much for Java Runtime and you should find a temporary down destination AI_RUNTIME_JCOSERVER.
SAP note 723909 shows how to tune JVM and increase Java Heap Size.
You should control if more than one msg leads to the error. If that is the case, may be a simple change of QOS to EOIO could solve the task to avoid more than one msg processing parallel. Reducing parallel JCO server threads would be similar strategy.
A direct Java Maping could be another idea. Message Mappings will be generated to Java with a quite huge source code, a direct written mapping could be more performant / stabil.
Regards,
Udo

Large Message picking Wrong Queue.....???

Similar Messages

Maybe you are looking for