Persistent and Non-Persistent messages coexisting

Hi all,
I'd like to know if it is possible to send a persistent and a non-persistent message over the same queue using the "deliveryMode"
argument from "send" method.
Thanks.

Yes.
James
http://logicblaze.com/

Similar Messages

Difference between Persistent Messaging and Non Persitent Messaging

Hi ,
I have a confusion related to Persistent messaging.
According to my knowledge the message becomes persistent if the flag JMSDeliveryMode is set
SO what is it by defalut ??
Where do messges get stored for time being for non -persistent messages.
Thanks in Advance:)

Message persistence is set by Delivery mode attribute of the message producer in the JMS client or it can bet set on a message basis during the send operation. The default value for the delivery mode on the message producer is PERSISTENT.
Weblogic JMS has a feature to override the delivery mode set by the message producer. This is at the Destination configuration where there is an attribute called the Delivery Mode Override which can take the values:
No-Delivery: Delivery mode of the message producer will not be overridden
Persistent: All messages are marked as persistent irrespective of the message producer setting
Non Persistent: All Messages are marked as non persistent irrespective of the message producer setting.
All non persistent messages are stored in memory in normal case. If there is a pile up of messages, weblogic moves the body Messages to disk within what is called as a paging store for the JMS server, only retaining message headers in memory. The characteristic of non persistent messages is that it can't survive server restart. So these messages even when they are on the disk within the paging store wont survive the server restarts.

SSO to ITS through WebSEAL gives secure/non-secure messages

Hi
We running the following setup:
EP6 SP14
Stand-alone ITS 6.20 patch 18
4.7 R/3 Enterprise
TAM/WebSEAL 5.1
We are running SSO through WebSEAL to the portal and everything seems to be working just fine.
But when we try to access a transactional iView or an IAC iView running on the ITS server I get a pop-up message saying "This page contains both secure and nonsecure items."
We are accessing WebSEAL through HTTPS, we are running HTTPS between WebSEAL and the portal and HTTP between WebSEAL and ITS.
I have tried to access the ITS through WebSEAL without using the portal, and I still get the message. So it must be something between the WebSEAL and the ITS server.
Does anybody have any ideas what is causing this?
Cheers,
Jacob Vennervald

The "secure and non-secure" message, displayed when accessing ITS through WebSEAL when using IE and HTTPS, is caused by an empty source reference (<IFRAME ... SRC="" ...>) within the ITS menu page (...d_menu.html).
The integration guide, available on the <a href="http://www-1.ibm.com/support/docview.wss?uid=swg24003605">IBM website</a> and the <a href="http://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/developerareas/ibm">SAP SDN</a>, contains the information on how to stop the message from appearing.
The message should not be displayed when accessing ITS through WebSEAL using HTTP.
Regards,
Peter Tuton.

Difference between a persistent messages and non persistent messages in JM

Hi
This question is with respect to persistent messages , and non persistent messages .
As per the docs it says that for persistent messages the QueueSender.send() blocks until it recivies an acknowledgement .
Here my question is what is the difference between a persistent messages , and non persistent messages
Thanks in advance .

The exact behaviour depends on the JMS provider being used. But since non-persistent messages are defined to be unreliable, the provider may indeed decide that it's not necessary for the server to acknowledge the receipt of a non-durable message from a producer.
Nigel

JMS Specification Question regarding persistent messages and reliability.

In section 6.15 of the JMS Specification, titled reliability it is stated that:
"When all messages for a topic must be received, a durable subscriber should be used. JMS insures that messages published while a durable subscriber is inactive are retained by JMS and delivered when the subscriber subsequently becomes active.
Nondurable subscribers should be used only when missed messages are tolerable."
Then in a table following the above text it states that a nondurable subscriber on a topic flowing persistent messages will receive a message "once-and-only-once (missed if inactive)."
To me this implies that if a nondurable subscriber is active, it is guaranteed to receive all persistent messages published to the topic while it is active. However there seems to be some ambiguity about what it means to be "active." Does active mean subscribed, does it mean subscribed and not busy processing messages, something else?
I ask this because I'm seeing a somewhat slow subscriber not receiving all persistent messages published while it is subscribed. This was surprising to me, given my interpretation of this reliability clause, so I'm wondering if I have not interpreted it correctly in this case.
Could anyone fill me in, particularly if you had something to do with writing the spec or can point me to the rationale behind this portion of the spec?
Thanks,
Jeff Singer

I am looking at the JMS 1.1 Spec version 1.1 April 12, 2002.
Section 4.10 "Reliabilty" has what reads to me as kind of a CYA statement that the contributing JMS providers got inserted. It reads:
"A JMS provider may have resource restrictions that limit the number of messages that can be held for high-volume destinations or non-responsive clients. If messages are dropped due to resource limits, this is usually a serious administrative issue that needs attention. Correct functioning of JMS requires that clients are responsive and that adequate resources to service them are available.
+
+
+Once-and-only-once message delivery, as described in this specification, has the important caveat that it does not cover message destruction due to message expiration or other administrative destruction criteria. It also does not cover loss due to resource restrictions. Configuration of adequate resources and processing power for JMS applications is the job of administrators, who must be aware of their JMS provider's reliability features."
+

The concept of http persistent and non-persistent

pls somebody explain me the concept of "keepalive type http".
when and where configure the persistent and non-persistent? not clear from the doc that HTTP-head, HTTP-get, classA and classB.
Thanks in advance.

Persistent will use HTTP version 1.1 while non-persistent will use version 1.0.
Use non-persistent only if your server does not support http version 1.1.
HTTP method HEAD or GET is selected with the command 'keepalive method'.
A head does not require the server to send us the content of the requested file, but simply an acknowledgement that the file is available.
The GET will request the complete file from the server and the CSS will verify that the content did not change compare to first GET request.
Again, I would recommend the default - head, unless you believe somebody could corrupt the content of your website.
Regards,
Gilles.

Temporary JMS paging files for non-persistent messages

Hello,
WLS 9.2
When does the server clean up, if at all, the temporary paging files created for large non-persistent messages? Should the files be deleted after the messages are acknowledged?
Thanks,
Bob

Or are they really gets stored ?
i.e the non_persistent messages are not stored atall either in memory or anywhere.
Or non_persistent messages are stored in memory only ....similar to PERSISTENT messages with no file store/database store ?

JMS - remove persistent messages from memory

Hi,
I have a problem with RAM and JMS. I have to store many JMS-messages (overall size
of more than 2GB). By default they are stored in RAM and in the database.
How can I configure WL not to store all messages in RAM.

Do you mean Time to Live Override value that we set in Overrides tab for the jms queue.Yes. Time to Live override can be used for that purpose.
Do all messages get stored in persistent (file)store while a jms server is up or only the messages with certain status like "Pending" get stored in jms.If yes,do the >pending messages get automatically deleted once the messages are read by the client application.All persistent messages gets stored in the jms store which includes messages in Messages Current ( status - visible ) state.
Some of the non persistent messages which gets paged out to free physical memory also end up in the store.
Messages get deleted from the store, but file stores doesn't relieve the disk space to OS after deleting ie file stores never shrink in size automatically. You can even end up with a huge file store even though no messages are pending in any of the queues under it.

MessagingPattern: Persistent Messages not supported ?

Hi,
in the INC10 MessagingPattern page, it is advocated:
"A Message may be Persistent or Non-Persistent. In the case of Persistent Messages, the infrastructure managing the Destination must safely store the said Messages to a persistent (and recoverable) storage device so that in the case of infrastructure failure, Messages may be recovered (not lost)."
But I can't find, examining the source code, how a message can be made persistent.
Can you give me directions on how to do it ?
Thanks

Hi
The Wiki is incorrect, we will fix it. Messaging does not support Persistence.
Paul

Persisted messages without durable subscriptions

Does weblogic JMS support PERSISTED MESSAGES without durable subscriptions. As per jms spec message persistence does make sense even without durable subscriptions in case when the JMS server fails before a message is sent and acknowledged.
          "A JMS provider must deliver a PERSISTENT message once-and-only-once. This means a JMS provider failure must not cause it to be lost and it must not deliver it twice."
          This implies that a persisted message will be persisted before sending and if JMS server fails, it resends the message to available consumers when server is back up and has nothing to do with durable/non-durable subscriptions.
          Please let me know what you guys think and if it is supported in weblogic JMS.
          Thanks,
          -Raj

- Topics require durable subcriptions to persist messages. This is a standard part of the JMS API. Nondurable subscribers have absolutely no need for persistence by definition - as such subscriptions exist solely for the life of the client's connection.
          - And yes, queues support persistence. This is required by the JMS spec, which BEA fully implements.
          - True "exactly-once" behavior usually requires the use of transactions in conjunction with JMS. This ensures that the message being processed and any related application work either atomically all fails or all succeeds.
          The above applies to all JMS vendors.
          Tom, BEA

Persistent messages are not deleted from JMS store

          Hi,
          I'm experiencing some unexperienced JMS store behaviour with WLS 6.1 sp 4. I have
          a servlet that posts a message to persistent JMS queue, which will be eventually
          consumed by an MDB. Even though consumption is successful, the message is not
          deleted from JMS store.
          The message will be redelivered after server restart and is still not deleted
          from JMS store. I verified this using file store and JDBC store. The messages
          actually stay in the JMSSTORE table till doom's day.
          I couldn't reproduce the case with WLS 6.1 sp 3. Exactly the application code
          was used in all cases.
          Subsequently I ran the same case with various ServerDebug DebugJMSXXX-flags set,
          and discovered that WLS 6.1 sp3 logs 'asyncDeleteL' and 'ZZZDelete' for the consumed
          message. WLS 6.1 sp4 didn't log this information.
          I'm running WLS 6.1 on WinNT and Win2000.
          Comments?
          b r
          Juha Räsänen


I've am having exactly this problem with wl 5.1....
          I first saw it with 5.1 sp8....
          In the release notes for 5.1 sp10, the following CR was fixed, which seemed
          like it might have been my problem:
          CR 45915
          Fixed a JMS problem with messages begin left in the queue after received messages had been acknowledged. When a high volume of
          messages was sent to a queue and a consumer retrieved those messages and sent them to another queue, the messages were not being
          removed from the first queue even though they were acknowledged.
          We upgraded to 5.1 sp12, and it appeared that the incidence of that problem was reduced.
          However it still occurs once or twice a week, with 5.1 sp12....
          My situation is a little bit different, in that my consumer retieves a message, and sends another
          message to the SAME queue instead of another queue as described in the CR above...
          It does happen under heavy load, etc....
          Don't know if this has been reported and identified for wl 5.1 sp12 or not...
          It is of course a really difficult to deal with bug....
          Jason
          "Juha Räsänen" <[email protected]> wrote in message news:[email protected]...
          >
          > Hi,
          > I'm experiencing some unexperienced JMS store behaviour with WLS 6.1 sp 4. I have
          > a servlet that posts a message to persistent JMS queue, which will be eventually
          > consumed by an MDB. Even though consumption is successful, the message is not
          > deleted from JMS store.
          >
          > The message will be redelivered after server restart and is still not deleted
          > from JMS store. I verified this using file store and JDBC store. The messages
          > actually stay in the JMSSTORE table till doom's day.
          >
          > I couldn't reproduce the case with WLS 6.1 sp 3. Exactly the application code
          > was used in all cases.
          >
          > Subsequently I ran the same case with various ServerDebug DebugJMSXXX-flags set,
          > and discovered that WLS 6.1 sp3 logs 'asyncDeleteL' and 'ZZZDelete' for the consumed
          > message. WLS 6.1 sp4 didn't log this information.
          >
          > I'm running WLS 6.1 on WinNT and Win2000.
          >
          > Comments?
          >
          > b r
          > Juha Räsänen

Persistent Messages, What heppens if a system is started!

Hi,
I am new to JMS and trying to understand. I have a Web Service that put messges on a queue. Now on the consumer side I have a Message Driven Bean. What if my MDB is not available and the WS puts some messages in a queue. The messages are still in a queue but not consumed as MDB is not available. Now I restarted the whole system and server and redeployed the MDB but I don't see any messages being consumed by MDB even though there are some messages that are put by Web Service before starting the System. Are the messages lost if in a queue but not yet consumed and a system or server is restarted.
How can I make the messages available in a queue all the time even after a restart. Here is a snippet of code that ques the messages.
InitialContext context = new InitialContext();
QueueConnectionFactory fac = (QueueConnectionFactory)context.lookup("jms/MainQueueConnectionFactory");
QueueConnection conn = fac.createQueueConnection();
QueueSession session = conn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue que = (Queue)context.lookup("jms/MainQueue");
QueueSender sender = session.createSender(que);
MapMessage message = session.createMapMessage();
message.setString("Subject","subject");
message.setString("Content","Content");
sender.send(message);If messages gets lost if the system or server is restarted then what's the point of Persistent Messages. Any help is appreciated.
Thanks

How do I set it never to expireBy setting the message time-to-live to zero. This can be done on the message and possibly on the connection factory. I'm pretty sure the default is zero anyway, but couldn't find this in the spec - http://java.sun.com/products/jms/docs.html
I believe all the messages are by default persistentThis depends on your JMS Provider. See you providers docs for how to configure for persistent messaging.
Where exactly in queue definition any small sampleAgain this depends on your JMS provider. I don't have experience of your app server so I can't provide and example - sorry.

Delete persisted message

hi,
i configure sender side mail adapter and it picked all the mail from my mailbox.
how to delete the persisted messages
t & r
vijender

HI VS,
goto SE38 and execute the report RSXMB_DELETE_MESSAGES...it will delete the messages
Regards
Biplab

Persistent message saying browser version isn's supported etc. etc.

persistent message saying browser version isn't supported etc. etc.
How do I fix that?

https://discussions.apple.com/docs/DOC-6413 and Apple menu -> About This Mac should help you identify the machine.

WIFI stopped working after I woke the computer up, now says connected to the network but not the internet, all other coputers and devices connected still with no problems, have pinged IP address from router and got the message "4 packets sent none receive

Hi,
WIFI stopped working after I woke the computer up, now says connected to the network but not the internet, all other coputers and devices connected still with no problems, have pinged IP address from router and got the message "4 packets sent none received"... Help
I have tried network diagnostics which doesnt help... The only other ting is, when I woke the computer up it said tat another device was using my IP... My wife had plugged her phone into the computer to charge etc but even when i turn wifi off on the phone there is no change... also in settings on the phone the IP address is different...

The answer to your question is - neither!
Your PC should to configured to obtain an IP address automatically, and to obtain DNS server IP addresses automatically, from the Airport Express. This is the way Windows (and Macs for that matter) are configued by default, and that is the way most people have their computers set up. If you manually configured your PC's IP address to be the same as your wife's Mac, it certainly explains why your PC is not able to access the internet.

Persistent and Non-Persistent messages coexisting

Similar Messages

Maybe you are looking for