JMS message filtering

Hi,
I publish messages to JMS topic on WLS. In the payload, there is a property operatorName whose value is in:
Tom,Jim,Andy,Alex
and I configured the jms client with the message selector as:
operatorName='Tom'
However, I found that the jms client can't receive message from JMS server.
Could somebody give me an instruction on this?
-Junger

There could be many reasons why your jms client didnt get the message. It would be good to start with checking whether your jms client had a subscription to the topic.

Similar Messages

Jms message filtering with multiple fields

Hi
Can anybody please tell me how to do message filtering with multiple fields. i using jdeveloper11.1.1.4.0 , soa11g suite and weblogic 10.3.
previously i used JMSType property for one field filtering.
and is it possible to invoke jms adapter with our own properties (adding property to jms).
thanks,
Sourbh

thanks atheek
i worked with the same and it helped me a lot i can share one more link that will help.
http://forums.oracle.com/forums/thread.jspa?messageID=9650255&#9650255
Regards,
Sourbh.

Correlation for JMS Messages possible? JMSCorrID in JMSHeader not accepted

Is Correlation for communication over JMS messages possible?
If I define the JMSHeader field "JMSCorrelationID" in a correlation set ("as usual") then I get
compiler errors:
Error ORABPEL-10036: invalid correlation set
BPEL seems not to accept JMSHeader fields for correlation but only fields from the actual payload msg.
Is this true?
Is there soemwhere a guide on how to correlate JMS messages?
Thank you
Michael

you can use the "Message Selector" on the JMS adapter to filter to achieve that;
here is extract from oracle help document
Message Selector
Specify filtering logic that enables you to receive messages that match a certain criteria. Enter an expression between 1 and 255 characters in length. Use SQL92 syntax in this field. The JMS server uses this criteria to filter messages received by this consumer. The message selector works with variables defined in standard JMS headers and user-defined properties. You cannot use variables or elements that are in the payload of the message.
For example, you can enter logic such as: JMSPriority > 3. Based on this, messages with a priority greater than 3 are consumed; all other messages are rejected. JMSType = 'car' AND color = 'blue' AND weight > 2500 Country in ('UK', 'US', 'France')
it's got some limitations but works fine for our requirements so far...

Specify JMS message properties with UMS send protocol ?

Hi,
is there a way to specify JMS Message properties when sending a message throught Universal Message Service (UMS) ?
I was not able to find any reference to this kind of usage.
Additionally, how do we specify filters (if possible) when receiving messages from UMS?
Thanks.

I have written an UDF to determine the filename dynamicly:
//write your code here
String str = "SAPDATA-" + a + "ES" + ".xml";
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
conf.put(FileName, str);
return "";

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

Lost (and found) JMS - messages

 Using WLS 6.1 and have experienced that JMS messages has not been delivered to
 its consumer correctly. We are interested in any suggestions to what has happend,
 what can be done to avoid the problem in the future, or perhaps how we can find
 out more about the problem.
 We have a message driven bean A which sends messages to the queue Q, of which
 the message driven bean B is the only consumer.
 What we recently have experienced is that some of the messages delivered by A
 to Q never are delivered to B. But the messages seems to be persisted correctly,
 because after a restart they reappear!
 Following is a more detailed description of the scenario:
 1. A message is sendt with DeliveryMode=PERSISTENT and TimeToLive=0. QueueSender.send
 is invoked and returns normally.
 2. The consumers never gets the message (B.onMessage i never invoked with this
 message).
 3. Point 1-2 is repeated for 13 different messages over a period when ~100 similar
 messages are delivered normally.
 4. The server is then restarted.
 5. In the starup log it is indicated that 44 records are found in the JMSStore.
 6. When the server restarts, the "lost" messages gets delivered to B.
 After the server restart we have not experienced the problem again.
 Logs does not show anything unusual about the previous restart.
 Other details:
 There is always exatly 1 instance of A running, and 5-20 instances of B. A implements
 and uses a pool of javax.jms.XAQueueSession instances, which shares a single instance
 of javax.jms.XAQueueConnection. The aknowledge-mode for B is "Auto-aknowledge".
 We're using Weblogic Server 6.1.3.0 / Red Hat Linux 7.3.
 Any help on this problem is appreciated!


 I believe we've seen just the behaviour you describe on 6.1 SP2, but only on a
 multi-cpu box (Solaris), and only under load. We can't reproduce the problem reliably,
 and get no error messages/warnings anywhere, so very little to send to customer
 support; by the time we notice this, the problem's long passed, so a thread dump's
 of no use.
 We're going to try and see how SP5 (which has loads of JMS fixes) pans out.
 But if you find anything out, could you post here?
 simon.
 "Harald Stendal" <[email protected]> wrote:
 >
 >Using WLS 6.1 and have experienced that JMS messages has not been delivered
 >to
 >its consumer correctly. We are interested in any suggestions to what
 >has happend,
 >what can be done to avoid the problem in the future, or perhaps how we
 >can find
 >out more about the problem.
 >
 >We have a message driven bean A which sends messages to the queue Q,
 >of which
 >the message driven bean B is the only consumer.
 >What we recently have experienced is that some of the messages delivered
 >by A
 >to Q never are delivered to B. But the messages seems to be persisted
 >correctly,
 >because after a restart they reappear!
 >
 >Following is a more detailed description of the scenario:
 >
 >1. A message is sendt with DeliveryMode=PERSISTENT and TimeToLive=0.
 >QueueSender.send
 >is invoked and returns normally.
 >2. The consumers never gets the message (B.onMessage i never invoked
 >with this
 >message).
 >3. Point 1-2 is repeated for 13 different messages over a period when
 >~100 similar
 >messages are delivered normally.
 >4. The server is then restarted.
 >5. In the starup log it is indicated that 44 records are found in the
 >JMSStore.
 >6. When the server restarts, the "lost" messages gets delivered to B.
 >
 >After the server restart we have not experienced the problem again.
 >
 >Logs does not show anything unusual about the previous restart.
 >
 >Other details:
 >There is always exatly 1 instance of A running, and 5-20 instances of
 >B. A implements
 >and uses a pool of javax.jms.XAQueueSession instances, which shares a
 >single instance
 >of javax.jms.XAQueueConnection. The aknowledge-mode for B is "Auto-aknowledge".
 >
 >We're using Weblogic Server 6.1.3.0 / Red Hat Linux 7.3.
 >
 >Any help on this problem is appreciated!
 >

When using Message Filters on an IMAP account I often get duplicate messages in my local folder where important messages are put. How can I stop this?

Since switching to IMAP and using message filters, I often get duplicate messages in my local folders. I think this is a bug.
That is my guess as to what is happening.
When the IMAP part starts syncing with the server to fill in the inbox, the message filter system starts working before it is done syncing. I appears that the filters runs too quickly because as the filter moves a msg to a local folder, the sync thread think it need to download it again from the server. If the sync with the remote server takes a long time, I could end up with 5 or more copies of the exact same email.
This has always happened for years now but I figured someone would have noticed it and fix it by now. Now I am wondering it it has something to do with my filters or my settings.
Has anyone run into this before?

Toys,
I was just doing a search to see if anyone else was feeling this way! I am also at a university and I don't really like see thousands of unread messages in mail. (Fortunately, with Leopard you can select the dock icon to show only the messages in your inbox but I still don't like having the public folder in there).
Please let me know if you find out anything and I will do the same for you. If I have time later I am going to run by our IT office later and ask them.

Problem in sending JMS message on remote OC4J

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

Specifying additional JMS message attributes in Sender Adapter

Hi,
Iam using sender JMS adapter and I have to use the option " Specify Additional JMS Message Properties" for adding addtionalJMS properties in XI message header.
Once I cselect the option in the below table Iam not able to add new lines to add addtional JMS Message Properties..But In receiver adapter I was able to add the new lines.
Is this option graded in SAP PI 7.3 or relatd to any authorization issue..?
Is anyone faced this issue before.. Please help me out
Thank you

Hi everybody
I'm starting a project where I have to take adptadores JMS and I'm in the same situation kirian, I am need to configure a JMS adapter with version of SAP PI 7.3 and I wonder if anyone can help me or give me manuals leagues where information comes related.
Someone can help me with this information
Regards

How to stop and start MDBs to listen for JMS messages

Hello! This might be more of an architecture question rather than a technical questing, but I post it here, in the lack of a better place...
For several years I have been using Webster and Webster MQ to send messages back and forth to clients. The architecture for the middleware platform has been designed around the functionality of ListenerPorts. Listenerports is a Webster functionality that let you "stop" and start to listen to JMS messages for a given MDB either by admin console, or by JMX.
The arhitecture we used was something like this :
1.Client sends a persistent message to a queue. (order)
2. An MDB pics up the order message, calls a SessionBean that "fronts" the IIOP back end system.
This is quite "out of the box" architecture, but we used the Listenerports to solve a stability problem for our back end system.
The backEnd system was quite unstable, so the EJB threw an exception (typically because of timeout or connection refused) back to the MDB.
The Listenerport was "defined" to handle 3 errors before stopping, so the MDB resent the message twice before the listenerport automatically stopped. The nice thing about this feature was that the client could continue to send orders, and was not bothered when the back end system was down.
When the backEnd system was up and running, we could start the listenerport and it was all back to normal state. We even had a start script that checked the state of the listenerport every 30 minute, and started it automatically if it was stopped, making the admin task of starting the MDB unnecessary..
Now.. Why am I telling this story..
I would like to know how this could be done using "clean" J2EE technologies..That is..Not using any technology that is not portable..
I`m playing with glassfish at home, and it struck me that there is nothing in the J2EE spec that defines the functionality described above ? Am i missing something ?
I Do not want to stop My application because the back end system is down? That is the only way (i know of) that i can "stop" to listen for messages..
I can put all the messages on an error queue when the backbend system is down, but that would lead to more code just to handle the error messages. Maybe the easiest way to solve this is to "move" (programmatically) all messages from the error queue over to the "standard" queue every XX minute, but somehow that sounds "wrong"
Can anyone give me some advice to how this problem situation should be solved ? I`m interested in the solution both from an architectural perspective and from a more technical perspective..
Best regards
Hans-Jacob Melby

Breakpoints, whether normal or conditional, are just meant for debugging of your code. I had the sense from your question that the pausing you want to do is a part of normal operation of your code. I would NOT recommend using a breakpoint for that situation. It would bring up the block diagram showing the breakpoint when it occurs. A user besides the programmer would not know what to do in that case.
Yes, both the inner and outer loops would have shift registers.
Putting a case structure with a small while loop inside the "Pausing Case" is doable. It just depends on what you are doing or waiting for while the program operation is "paused".

I am unable to send JMS message to application which resides in third party

I am able to produce the Message into JMS demoQueue which is available in SOA 10.1.3.3. And also I tried remote server which is available in my office it having the application SchoolMAX with JMS Configuration. So I need to produce the JMS message into SchoolMAX application. But I am unable to pass to the data’s to that SchoolMAX JMS.
for this I have configured the respective queues, queue factory etc in Enterprise Manager , but i am not able to access our application which is in remote server through third party in JDeveloper for BPEL Process.
please i am very new to this JDeveloper & BPEL Console , please help me out in resolving the issue ASAP. please we will be waiting for some reply.

Hi Kathy,
Happy Holidays! Do you have an iPad with cellular service and a text-messaging plan?
Send messages with your iPhone, iPad, or iPod touch - Apple Support
http://support.apple.com/en-us/HT201287
What's the difference between SMS/MMS and iMessage?
SMS/MMS lets you send text messages and photos to other cellular phones or devices. iMessage lets you send text messages and photos to another iOS device over Wi-Fi, without worrying about text-messaging charges (cellular data charges may apply).
What do I need to use SMS/MMS and iMessage?
Here's what you need to use SMS/MMS and iMessage:
SMS/MMS: A text-messaging plan. Contact your carrier for more information.
iMessage: An iPhone, iPad, or iPod touch with iOS 5 or later.
How do I know if my message used SMS/MMS or iMessage?
You can tell which type of message you're sending by the color of the Send button and text bubble.
SMS/MMS: Send button and text bubbles are green.
iMessage: Send button and text bubbles are blue.
How can I link my iPhone number with Messages on my iPad, iPod touch, or Messages for Mac?
When you sign in to Messages with your Apple ID on your iPhone, you link your phone number to your Apple ID. If you then sign in to Messages with the same Apple ID on your iPad, iPod touch, or Mac, Messages will link that device to your phone number as well.
I hope this information helps ....
- Judy

What is the recommended way for persisting JMS messages?

What is the recommended way for persisting JMS messages?. As per the IMQ admin documentation , using the default built-in persistence type which is through unix flat files is much efficient and faster, compared to the database persistence .
Tried setting up the jdbc stuff for database persistence on iAS 6.5 . I am getting the following
error .
[24/Apr/2002:16:09:20 PDT] [B1060]: Loading persistent data...
[24/Apr/2002:16:09:21 PDT] Using plugged in persistent store: database connection
url=jdbc:oracle:thin:@dbatool.mygazoo.com:1521:qa1 brokerid=ias01
[24/Apr/2002:16:09:23 PDT] [B1039]: Broker "jmqbroker" ready.
[24/Apr/2002:16:11:56 PDT] ERROR [B4012]: Failed to persist interest
SystemManager%3ASystemManagerEngine%2BiMQ+Destination%0AgetName%28%29%3A%09%09SM_Response%0AClass%3A%09%09%09com.sun.messaging.Topic%0AgetVERSION%28%29%3A%09%092.0%0AisReadonly%28%29%3A%09%09false%0AgetProperties%28%29%3A%09%7BJMQDestinationName%3DSM_Response%2C+JMQDestinationDescription%3DA+Description+for+the+Destination+Object%7D:
java.sql.SQLException: ORA-01401: inserted value too large for column
[24/Apr/2002:16:11:56 PDT] WARNING [B2009]: Creation of consumer SM_Response to destination 1
failed:com.sun.messaging.jmq.jmsserver.util.BrokerException: Failed to persist interest
SystemManager%3ASystemManagerEngine%2BiMQ+Destination%0AgetName%28%29%3A%09%09SM_Response%0AClass%3A%09%09%09com.sun.messaging.Topic%0AgetVERSION%28%29%3A%09%092.0%0AisReadonly%28%29%3A%09%09false%0AgetProperties%28%29%3A%09%7BJMQDestinationName%3DSM_Response%2C+JMQDestinationDescription%3DA+Description+for+the+Destination+Object%7D:
java.sql.SQLException: ORA-01401: inserted value too large for column
Any thoughts?

From the output, you are using imq 2.0. In that release
the key used to persist a durable subscriber in the database
table has a limit of 100 characters. The output shows that
your value is:
SystemManager%3ASystemManagerEngine%2BiMQ+Destination%0AgetName%28%29%3A%09%09SM_Res
ponse%0AClass%3A%09%09%09com.sun.messaging.Topic%0AgetVERSION%28%29%3A%09%092.0%0Ais
Readonly%28%29%3A%09%09false%0AgetProperties%28%29%3A%09%7BJMQDestinationName%3DSM_R
esponse%2C+JMQDestinationDescription%3DA+Description+for+the+Destination+Object%7D:
which is much longer than 100 characters.
You might want to shorten the string you use for the
durable name.
And yes, the default file-based persistence store is
more efficient when compared to the plugged-in persistence
through a database.

How to parse XML content in JMS Message...

Hi everybody,
I am currently developing a Message-Driven Bean and has some problem parsing the XML data that contains in the JMS body.
The XML data is contained in TextMessage (JMS message type) and in order to parse the data, I need to use the DOM builder, which is expecting to read from a file (e.g. abc.xml).
My question is how can I use TextMessage (can be output to a String) as the input source instead of a file.
Thanks in advance.

Hi Boon,
"Boon Keong" <[email protected]> wrote in message
news:3dd46800$[email protected]..
I am currently developing a Message-Driven Bean and has some problemparsing the XML data that contains in the JMS body.
>
The XML data is contained in TextMessage (JMS message type) and in orderto parse the data, I need to use the DOM builder, which is expecting to read
from a file (e.g. abc.xml).
>
My question is how can I use TextMessage (can be output to a String) asthe input source instead of a file.
What about this:
DocumentBuilder db = ...
Document doc = db.parse(new InputSource(new
StringReader(textMessage.toString()));
or
Document doc = db.parse(new
ByteArrayInputStream(textMessage.toString().getBytes()));
Regards,
Slava Imeshev

Can not dequeue JMS message of type SYS.AQ$_JMS_TEXT_MESSAGE using DBMS_AQ

I'm having a problem using DBMS_AQ package to dequeue a JMS message of type SYS.AQ$_JMS_TEXT_MESSAGE that was put on the queue using Java JMS API.
Both JMS header and payload return empty but if I do "select user_data" from the queue table, I can see the message.
Appreciate any helps or tips.
Kim

This has been asked a lot of times - I'm not sure how my initial searching missed all of the other questions/answers related to this topic.
In our case, the solution was to:
1) Leave the queue as a sys.aq$_jms_text_message type
2) Construct a sys.xmltype object with our desired payload
3) Do a getStringVal() on the xmltype object and use that string as the payload for our queue message
- Nathan

Adapter Status Error : Error in creating message ID map for JMS message:

Currently in the SAP XI 3.0 JMS Adapter, I am receiving the following error
Error in creating message ID map for JMS message:
ie. Error while processing message 'de8265f6-c864-4479-1137-9bab17b78b3b'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in creating message ID map for JMS message: ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:103)
Although I am receivng this error, when I check the details of the message processing, all steps are successful and the message is set to status : DLVD
Audit Log for Message: de8265f6-c864-4479-1137-9bab17b78b3b
Time Stamp     Status     Description
09.06.2009 13:27:24     Success     New JMS message with JMS message ID ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 received. The XI message ID for this message is de8265f6-c864-4479-1137-9bab17b78b3b
09.06.2009 13:27:24     Success     JMS message converted to XI message format successfully
09.06.2009 13:27:24     Success     RRB: entering RequestResponseBean
09.06.2009 13:27:24     Success     RRB: suspending the transaction
09.06.2009 13:27:24     Success     RRB: passing through ...
09.06.2009 13:27:24     Success     RRB: leaving RequestResponseBean
09.06.2009 13:27:24     Success     Transform: using Transform.Class: com.sap.aii.messaging.adapter.Conversion
09.06.2009 13:27:24     Success     Transform: transforming the payload ...
09.06.2009 13:27:24     Success     Transform: successfully transformed
09.06.2009 13:27:24     Success     Application attempting to send an XI message synchronously using connection JMS_http://sap.com/xi/XI/System.
09.06.2009 13:27:24     Success     Trying to put the message into the call queue.
09.06.2009 13:27:24     Success     Message successfully put into the queue.
09.06.2009 13:27:24     Success     The message was successfully retrieved from the call queue.
09.06.2009 13:27:24     Success     The message status set to DLNG.
09.06.2009 13:27:25     Success     The application sent the message synchronously using connection JMS_http://sap.com/xi/XI/System. Returning to application.
09.06.2009 13:27:25     Success     The message was successfully transmitted to endpoint http://sapxia.swets.nl:8000/sap/xi/engine?type=entry using connection JMS_http://sap.com/xi/XI/System.
09.06.2009 13:27:25     Success     The message status set to DLVD.
Not sure why this is occurring.......

No, not using correlation id.
I was able to resolve the issue on this queue by changing the following setting
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds and the adapter has now gone green.
BUT......
That said, I have the exact scenario on another sender JMS channel set to 300 seconds and it exhibits the same issue.
correlation settings:
Set XI message id to = GUID
Set Xi conversation

JMS message filtering

Similar Messages

Maybe you are looking for