[ESBJAVA-2529] Message store configuration is not backward compatible Created: 08/Oct/13  Updated: 04/Nov/13  Resolved: 04/Nov/13

Status: Resolved
Project: ZZZ-WSO2 ESB
Component/s: Message Stores
Affects Version/s: 4.8.0 M3
Fix Version/s: 4.8.0

Type: Bug Priority: Highest
Reporter: Isuru Udana Loku Narangoda Assignee: shafreen anfar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ESBJAVA-2529.patch    
Severity: Blocker
Estimated Complexity: Moderate
Test cases added: No


We need to make message store configuration backward compatible. Otherwise this adds an overhead to migrations.

Comment by Isuru Udana Loku Narangoda [ 09/Oct/13 ]

Patch attached to fix this issue

Comment by Isuru Udana Loku Narangoda [ 09/Oct/13 ]

Patch committed in r187663

Comment by Iranga Muthuthanthri [ 01/Nov/13 ]

It is not possible to view messages through the Message Store mediator.

1.) Deactivate message processor (optional)
2.) Send a request.

The messages cannot be viewed through the message store mediator.

Comment by Isuru Udana Loku Narangoda [ 01/Nov/13 ]

Mentioned issue is not related to configuration backward compatibility.

Message cannot be viewed by Message store mediator.
I believe what you meant here is "Messages cannot be viewed from the Message Store".
We removed this functionality for JMS message stores in ESB 4.7.0 release as it leads to many issues.

Comment by dushan abeyruwan [ 04/Nov/13 ]

The reason copied from the mail thread..

It is more of an implementation level decision that we took not to show messages of a particular JMS queue.
The reasons are;
JMS API does not support direct retrieval of messages of a destination. We had implemented it with expensive API methods that used to cause issues with message brokers. (Those methods increased # network communications + used a lot of memory + added a huge latency, as a result, the broker(s) became unresponsive and more often than not the number of messages in the broker and the number of messages shown in the message store view did not add up, which ultimately caused confusion to the users)

Giving a list view of messages in a queue is a part of the functionality of a broker. When using JMS message stores, the ESB is the entity that is handling the 'storing' and the processing of the messages. The functionality is different with In-memory stores where ESB also acts as the entity that actually stores the messages. That is another way to look at this.

Generated at Thu Oct 01 08:30:40 PDT 2020 using JIRA 7.2.2#72004-sha1:9d5132893cc8c728a3601a9034a1f8547ef5c7be.