Questions on "General Warning: This Release Does Not Support JMQ Notify Type"
(Doc ID 2684640.1)
Last updated on JUNE 26, 2020
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
On : Oracle Communications Messaging Server (MS) 8.1.0 version, Message Store
General Warning: This release does not support JMQ notify type except ...
We were previously led to believe that JMQ would be removed from 8.1 and therefore upgrade to 8.1 meant you could not use ISS. See Doc ID 2599763.1.
Now we understand that is not the case. The components are still there. But we are only allowed to be using them if we are in the process of upgrading to use Elasticsearch.
1. Please confirm that our new understanding is correct. What then is the point of Doc ID 2599763.1 ?
And finally, imapd (and other processes) on startup with Messaging Server 8.1 log this:
2. What does the ignoring 'notifytarget:index' mean?
It does not seem to be correct because we can see in the ISS logs that imapd is sending flagchange events. So what does that part mean?
3. While we can see imapd is sending flagchange events in the ISS logs, the newmsg events are not. The newmsg events in Messaging Server 8.1 should also to be sent to ISS the same way as Messaging Server 8.0.2.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document