Introduce delay in processing a JMS message

Hi All
Looking for clean solution to introduce a fixed time delay (n minutes) in processing messages from a MQ Queue?
The sending and receiving applications both using SOA Suite 11g JMS adapter.
regards.

Hi
Thanks a lot for the suggestion. Such "time to deliver" (i.e. delay before the message is delivered to destination) is supported by almost all other providers - Weblogic, AQ, JBoss, ActiveMQ etc, but I could not find how to set it for Websphere MQ, doubtful if it supports same. Any idea?
Also no clear documentation on if Oracle JMS Adapter supports dynamic message selector.
regards

Similar Messages

Kick off a business process with JMS message

I'm a newbie with a job that's way over my head and I'm thouroughly confused on
the logic involved with kicking off a business process (workflow) through the
reciept of a JMS message. The docs say it can be done. I have a business process
in one project folder of an enterprise app, its start node is a channel subscription.
Can I somehow send a JMS message directly to the business process? (Send a message
NOT from within the weblogic environment, but from outside) I have created a
Message Driven bean in a seperate project folder of the same application as the
business process. From an outside client, I think I might need to invoke the
MDB with a JMS message, then call the business process from there. Is this totally
off-base? What do event generators have to do with any of this?
Please help.

Yes, you use the event generator.
Open up the Weblogic Integration console, click on Event Generators.
Add a JMS Event generator that listens to the queue you are interested
in, and then select the channel that your process has subscribed to.
Lisa wrote:
I'm a newbie with a job that's way over my head and I'm thouroughly confused on
the logic involved with kicking off a business process (workflow) through the
reciept of a JMS message. The docs say it can be done. I have a business process
in one project folder of an enterprise app, its start node is a channel subscription.
Can I somehow send a JMS message directly to the business process? (Send a message
NOT from within the weblogic environment, but from outside) I have created a
Message Driven bean in a seperate project folder of the same application as the
business process. From an outside client, I think I might need to invoke the
MDB with a JMS message, then call the business process from there. Is this totally
off-base? What do event generators have to do with any of this?
Please help.

Weblogic spiking to 99% CPU resources while processing inbound JMS messages

We have an Integration Gateway server that is receiving data into a JMS queue from SAP/TIBCO and a legacy system for processing. We have Weblogic 8.1 SP3 and the server is running ClarifyCRM 12.5 Integration Gateway components including Tuxedo. In the past few weeks, Weblogic has been hanging up multiple times trying to receive this data from these systems. Specifically java.exe process used by Weblogic spikes to 99% CPU and the server becomes completely unresponsive. So far the only workaround we have is shutting down Weblogic, moving the incoming messages stored in the JM file store that are hanging the server to a different location so that they won't be processed by Weblogic and then restart Weblogic.
          What we see when this happens is that the hung up messages stay in the "Messages Pending" queue.
          A developer has mentioned that this may be happening because the threads handling the messages are hanging.
          I want to know if there is a tool from BEA to view and edit the JMS File Store on the file system to further analyze the incoming messages.

I agree about the older version. However this particular version and service pack are the only ones that have been tested in our production and dev environments. So currently I don't have any options but to use it. However the system has been running relatively fine for the past 1-1.5 years.
          Do you happen to know the name of that tool that you mentioned below?
          Thanks in advance.

Why are my JMS messages automatically dequeued without consumer?

I created a simple in-memory JMS queue.
Now I wrote a BPEL process which writes (successfully ?) JMS message to this JMS queue.
Another consuming BPEL process is deployed but not started.
However I cannot see them in MBean JMSDestinationResource on the OC4J Enterprise Manager Web page.
When I tell the AppServer to browse all currently existing (and waiting) JMS message then there are none.
However the statistics for this queue show 17 messagesEnqueued and 17 messagesDequeued Messages.
It seems to me that my JMS messages are automatically dequeued. But why?
Are in-memory JMS messages not persistent (as long as the AppServer is up and running) ?
Do I have to set a certain preference to let JMS live in the Queue as long as they are not retrieved by another BPEL process?
Furthermore I tried the following:
I started a consuming BPEL process. Yes, he is waiting at the JMS adapter until a new JMS message arrive.
Then I send from the first BPEL process a JMS message. But even when consumption is possible the JMS message is dequeued and not forwarded to the consumer.
Why?
Peter

It seems to me that my JMS messages are automatically dequeued. But why?
This is how BPEL PM is designed; The activation-agent is running that belongs to the BPEL process. When a message arrives in a Queue or Table or File it is read into the dehydration store. Then an instance of the appropriate BPEL process is started. This functionality makes the system more stabel and reliable when something is goingin wrong in quees/files/db or any adapter that is used for polling.Are in-memory JMS messages not persistent (as long as the AppServer is up and running) ?
As you desribed: in-memory messages are only persistent in memory, if you restart the server, the messages are gone.Do I have to set a certain preference to let JMS live in the Queue as long as they are not retrieved by another BPEL process?
No you can not.Marc
http://orasoa.blogspot.com

Processing JMS messages in sequence one after another

This is my use case which I wan to implement in OSB.
1. I have a queue which will receive messages in huge numbers from a single sender.
2. I have a proxy which will read each message and process the message and send it out.
In step 1 , I want each message to be read sequentially and when step 2 finishes executing then I want to read the next message from the queue.
I need to give an acknowledgment to JMS that the message has finished processing and it can make the next message available to the proxy.
What is the best option to implement this use case ?.
Regards

By default Weblogic JMS Queues are FIFO. But that is true only if there is only one consumer of the queue.
In case of a clustered environment that is not true and in case of OSB even with a single managed server multiple threads are created for a JMS listener Proxy(by default 16). So there will be 16 instances of the Proxy trying to read messages from the Queue and each will be handed out a message and sequential integrity is disturbed.
There are three ways to overcome this problem:
1. Unit of Order
This is suitable only when you want messages of the same group to be processed sequentially while multiple groups can be processed in parallel.
For e.x. you are getting multiple orders for multiple customers and you want to ensure that the orders of same customer are processed sequentially (in case a customer tries to change the quantity of an order then the latest one should be processed last). In this case you can set UOO as the CustomerID and each customer's order will be processed sequentially but orders of different customers will be still processed in parallel. WLS JMS achieves this by assigning a target queue instance on the cluster for each UOO value. It will assign Q!MS1 to CustID=1, Q!MS2 to CustID=2 and so on. All messages of the same UOO(of the same customer) will go to the same instance on the queue. Furthermore it will ensure that no two messages of the same UOO are released together to the listeners. So if a queue instance has 5 messages each of both Cust=1 and Cust=2, only one message each of Cust1 and Cust2 will be processed by the listeners even if there are 16 listening threads.
Pros and Cons:
Overall performance is improved since you can still achieve some parallel processing.
There will be a slight overhead of processing the UOO headers on the JMS servers.
Can not ensure sequencing of all the messages. (Although you can achieve that by setting the same UOO on all the messages)
If the managed server assigned to a UOO is down, if a publisher tried to put the next message for that UOO, it will fail since it will not try to send that message to any other managed server.
2. Single threaded processing
If you don't want to process even different groups of messages in parallel and if you want absolute sequencing (i.e. irrespective of the CustomerID you want all the messages to be processed in the sequence they arrive) you will need to process them in a single threaded model. The JMS queue should be deployed on only one managed server of the cluster. The JMS proxy listening to the queue should also be deployed on a single managed server(You will need to change the targeting for the EJB created for this Proxy in the Deployments) and there should be a Work Manager for this Proxy with Maximum Thread Constraint set as 1. In the Connection Factory which the Proxy uses, set the Maximum Messages per session to 1. Another approach for Single threaded could be to set the same value of UOO on all of the messages. This will make all the messages to go to the same Q instance in the cluster and also will make sure that even if Proxy has multiple threads, only one message will be processed at a time.
Pros and Cons:
Completely single threaded processing, will take more time since messages will be processed one after the other.
Load balancing will go awry as all the messages will be processed by only one server.
3. Using custom implementation
The most complex way is to create a completely custom implementation. Put all the messages in a DB and then process them one at a time based on timestamp.
Pros and Cons:
It will take more effort to implement than the other two approaches.
It will again need single threaded processing after the messages are put on the DB
Performance wise there will be more impact because of additional DB calls
More complex to maintain
Based on your exact requirements you can choose which approach you want. If you have SOA suite as well them it would be better to move this solution to SOA suite as OESB(Mediator) component of SOA suite has re-sequencing feature.

How to read JMS message properties from BPEL or BPMN process

Hi all,
I have a JMS Adapter that consumes messages from a remote ActiveMQ queue and I don't find the way the get the properties of the JMS message as I would like to map them in BPEL or BPMN process variable. I only manage to get the content of the message.
I've also read that if using a MapMessage, one of the map entry can be mapped directly and that the other map entries go to jca.jms.Map.xxxx where xxxx is key of the map entry.
But how can I map those "jca.jms.Map.xxxx" properties on process variables ? and how to map JMS Properties (that seem to be mapped on jca.jms.JMSProperty.xxxx) to process variables ?
I use SOA Suite version : 11.1.1.4.0
Thanks for your help

SOA Suite 11g - how to set/get JMS headers ?

How to send JMS Message from a BPM Process

Hi All
I have small query regarding sending JMS Message from a bpm process. Is it possible to send JMS message from one bpm process to another bpm process.
I have a scenario in which I need to send a JMS message to a queue where another process is listening on that queue and as soon as the message is received on the queue the process instance is created.
I know how to listen for the JMS message on the queue, but I don't how to send a JMS message from a process.
Also Can I create process by sending the Notification to the process instead of a JMS message. But the process to be created is not a subprocess i.e. Can notification be send accross different processes.
Any information or example in this regard would be helpful.
Thanks in advance
Edited by: user9945154 on Apr 22, 2009 7:46 PM

Hi,
Here's one approach to sending JMS messages from an Oracle BPM process. If you're doing this just to send a message into another process, do not take this approach. It's far easier and quicker if you do this using the OOTB "send notification" logic.
These steps describe how to do this using WebLogic. The steps would be different if you're using another ap server / JMS provider.
1. Guessing you've already done this, but first expose the two required WebLogic jar files for JMS messaging as Java components in the External Resources. The two files for WebLogic are weblogic.jar and wljmsclient.jar” (located in the < WebLogic home directory > /weblogic/server/lib” directory).
AquaLogic BPM JMS Queue Listener for WebLogic 8.1
2. You've probably already done this, but add an External Resource to represent the J2EE container:
• Name: “weblogicJ2EE” - this is important and will be used in the next step
• Supported Type: “GENERIC_J2EE”
• Initial Context Factory: “weblogic.jndi.WLInitialContextFactory”
• URL: “t3://localhost:7001”
• Principal: and Credentials: whatever userid and password you defined to access theWebLogic administrative console.
3. Create the External Resource that represents the send queue configuration. In this example, I'm calling it “WebLogic Send Queue”. This is important - remember what you named it because you will use this name in the logic that sends the JMS message. This new External Resource is configured as:
• J2EE: “weblogicJ2EE” (same name as the second External Resource you created)
• Destination Type: “QUEUE”
• Lookup Name: “weblogic.examples.jms.exampleQueue”
• Connection Factory Lookup Name: “weblogic.examples.jms.QueueConnectionFactory”
4. Here's the logic to send a Message to the Queue
<pre class="jive-pre"><p />msg as String = "Hello World"
jmsMsg as Fuego.Msg.JmsMessage
msg = "<?xml version=\"1.0\"?><Msg>" + msg + "</Msg></xml>"
jmsMsg = JmsMessage(type : JmsMessageType.TEXT)
jmsMsg.textValue = msg
sendMessage DynamicJMS
using configuration = "WebLogic Send Queue",
message = jmsMsg</pre>
Note that the “sendMessage” method uses the configuration parameter “WebLogic Send Queue”. You previously created a JMS messaging service External Resource with this name in the third step.
Again, please don't go this route if you're just using it to send notifications between processes,
Dan

How to test BPEL Process that starts with a pick consuming a JMS message

Hi,
We are using App Server v 10.1.3.3.0 and attempting to test a BPEL process which starts with a pick operation which is awaiting a JMS message on a specific queue.
We are using the Oracle JMS adapter to achieve this.
Is there any way in which this particular configuration can be easily tested using the BPEL testing framework? I have problems when I write the first initiate XML statement in my test case (stack trace below)
<2011-01-27 10:23:47,028> <ERROR> <ProvisioningInterface.collaxa.cube.bpeltest> test run failed!
ORABPEL-20011
Instance initiation error.
An error occurred while launching an instance for suite "BasicTest", test "baseline.xml".
Please examine the log file for details or contact the system administrator.
at com.collaxa.cube.engine.test.BPELTestRunManager.initiate(BPELTestRunManager.java:218)
at com.collaxa.cube.ejb.impl.BPELTestBean.runSuites(BPELTestBean.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Unfortunately, there are no further details or any example I can see which simulate the kind of setup I have for my test.
Any help much appreciated,
Kind Regards,
Colin.

Hi,
I assume you mean the JMS example under the $OH BPEL examples area. Unfortunately, this only shows how to get a BPEL process kicked off by awaiting a JMS message - but there is no test code there! There are specific examples which show off the testing framework facilities but it appears that all the examples which use async type of interactions are in the middle of a process which is kicked off by a normal synchronous client interaction.
Any further help much appreciated.
Colin.

JMS Message resent for for long processes

Hi,
Currently we using Webspher App Server 6 and WSAD 6 as our development platform. We are also using Websphere MQ as our JMS server.
We have one MDB resposible for processing data extraction/migration jobs from legacy databases that can take anywhere from 20minutes to several hours to complete. Once the MDB receives the message, it starts the extraction process based on the information received in the message.
The problem is, once the job completes, it restarts again because the same message is resent to the MDB. Checking the value of getJMSRedelivered() from the message shows it is true the second time the message is received. I suspect the problem is the long time taken to execute the job, as when i test with a shorter job (1-2mins), the message is not resent. If the job takes approx more than 6mins, then the message is resent, but im not exactly sure of the actual time before the message is resent.
Im unsure where the problem lies. Currently i just check if the message is redelivered, and just ignore it, but this should not be the case, as redelivery is needed if there were any problems.
How do i avoid the redelivery? Where could the problem be ??
need help as im no expert on JMS :-)
Thanks.

Hi,
Currently we using Webspher App Server 6 and WSAD 6
as our development platform. We are also using
Websphere MQ as our JMS server.
We have one MDB resposible for processing data
extraction/migration jobs from legacy databases that
can take anywhere from 20minutes to several hours to
complete. Once the MDB receives the message, it
starts the extraction process based on the
information received in the message.
The problem is, once the job completes, it restarts
again because the same message is resent to the MDB.
Checking the value of getJMSRedelivered() from the
message shows it is true the second time the message
is received. I suspect the problem is the long time
taken to execute the job, as when i test with a
shorter job (1-2mins), the message is not resent. If
the job takes approx more than 6mins, then the
message is resent, but im not exactly sure of the
actual time before the message is resent.
Im unsure where the problem lies. Currently i just
check if the message is redelivered, and just ignore
it, but this should not be the case, as redelivery is
needed if there were any problems.
How do i avoid the redelivery? Where could the
problem be ??
need help as im no expert on JMS :-)
Thanks.hi buddy, hope while depyloying the you are setting the acknowledte mode to Auto-acknowledge in ejb-jar.xml file as shown below.
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>SimpleMessageBean</ejb-name>
<ejb-class>in.co.persistent.SimpleMessageBean</ejb-class>
<message-selector>MessageType = 'Fatal'OR MessageType ='Error''</message-selector>
<transaction-type>Bean</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode> <message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
Auto-acknowledge avoids duplicate messages because the acknowledgment is sent immediately. Therefore, the JMS provider won't send a duplicate. Most MDBs use Auto-acknowledge, to avoid processing the same message twice.
Dups-ok-acknowledge exists because it may allow a JMS provider to optimize its use of the network. In practice, though, the overhead of an acknowledgment is so small, and the frequency of communication between the MDB container and JMS provider is so high, that Dups-ok-acknowledge doesn't have a big impact on performance. Obviously, with Dups-ok-acknowledge, your MDBs must be able to handle duplicate messages correctly.

Failed to process JMS message

Hi,
While trying to read the message in Queue from my BPEL, Iam getting the following error:
JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WTextMessageIn@ffae4c] in onMessage: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
Can any one provide some suggestion on how to resolve this error.

No, Iam just storing a simple message say "Hello" in the queue, the message is stored in the queue but it is shown in the below format when I opened that file in Notepad:
UUªª ªªUU ‡ÿãÂ- ‡ 6›4•Z 6›4”öÿ Â
Ô£9™ÿÿ¬h ÎM o „ fÂ6›4”ñ Trial4 com.sun.messaging.BasicQueue Hai ªªUU
and soon Iam getting this error below:
[Fatal Error] :1:1: Content is not allowed in prolog.
JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WTextMessageIn@1e377d5] in onMessage: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.

Delayed JMS Message with MQSeries?

Hello,
          does anyone know a possibility to delay the delivery of a JMS message
          in a MQSeries queue?
          I know that Weblogic JMS messages can be delayed with the
          setTimeToDeliver method. But this only works with the Weblogic
          JMSServer.
          Any ideas?
          Thanks.


This doesn't work well in that it requires polling with a new selector over
          and over again. This means creating a new consumer with each selector. It
          is very expensive.
          _sjz.
          "Hans-Peter Keilhofer" <[email protected]> wrote in message
          news:[email protected]..
          > I have a solution now: Use a message selector, which compares the
          > time_now with the time set in a property of the message. (as long
          > value).
          > That's it.
          >
          > [email protected] (Hans-Peter Keilhofer) wrote in message
          news:<[email protected]>...
          > > Hello,
          > >
          > > does anyone know a possibility to delay the delivery of a JMS message
          > > in a MQSeries queue?
          > > I know that Weblogic JMS messages can be delayed with the
          > > setTimeToDeliver method. But this only works with the Weblogic
          > > JMSServer.
          > >
          > > Any ideas?
          > >
          > > Thanks.

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

JMS messages not being redelivered correctly ..

Hi Folks
I am having this weird problem with JMS using workshop/weblogic 8.1 SP2. I am
using a JMS control from within my pageflow to post a JMS message to a predefined
JMS queue (created by workshop for every web project . Mine is called testweb.queue.AsyncDispatcher
as my web project is called testweb). Since pageflows cannot receive asysnchronus
callbacks , I have not implemented the callback handler for teh JMS control as
I just need to be able to post from my Pageflow . So far so good.
I have an MDB listening to testweb.queue.AsyncDispatcher and that basically tries
to open a URL connection to a thirdparty web site and if connect is not successful
it should keep trying after every 10 seconds. I have the MDB throw an EJBException
(to simulate message redelivery) . The problem is that the message is redelivered
exactly 8 times and then I get the below message on the console :-
<May 24, 2004 10:18:00 AM EDT> <Error> <WLW> <F1234PiyushK> <cgServer> <ExecuteThread:
'14' for queue: 'weblogic.kernel.Default'> <<anonymous>> <BEA1-001D75CA6E6EB041A149>
<000000> <onMessageException: java.lang.Exception: Unexpected message format>
I also have an MDB listening to the error queue testweb.queue.AsyncDispatcher_error
but its onMessage is never executed .
I am stuck on this for the last efw days so appreciate any help. Should I post
a message to the JMS queue directly from a session bean insetad of from a page
flow ?
my JMS queue config parameters are mentioned below :-
Time To Deliver Delivery 5000
Delivery Mode Override - No Override
Expiration Policy - Redirect
Redelivery Delay Override - 5000
Redelivery Delay Override - 10
Error Destination - testweb.queue.AsyncDispatcher_error
The other parameter values are the default values and I have not changed them

I am having the same problem with a simple WLI timer channel that posts a string message called myMessage every 20 seconds (what I defined in the WLI console).
This works like a charm.
In my process.jpd file, the timer subscription is followed by a JMS control, with a sendTextMessage(myMessage) which sends the message to a queue
@jc:jms
send-type="queue" send-jndi-name="JmsTimerProcessWeb.queue.AsyncDispatcher"
receive-type="queue" receive-jndi-name="NightlySiteProcess.queue.AsyncDispatcher"
connection-factory-jndi-name="weblogic.jws.jms.QueueConnectionFactory"
All goes well while sending but the messages tell otherwise:
=== Timer sent message = This is the WLI message
=== JMS sent message = This is the WLI message
<Aug 24, 2005 1:19:30 PM MDT> <Error> <WLW> <000000> <onMessageException: java.lang.Exception: Unexpected message format>
What does this mean?
I tried to add a project with a Message-bean, I cannot get the string message. I tried with an ObjectMessage, the same scenario everytime.
Any suggestions?

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

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

Introduce delay in processing a JMS message

Similar Messages

Maybe you are looking for