7:47 a.m.
Separate DLQ from Message Store
-------------------------------
Key: JBESB-823
URL: http://jira.jboss.com/jira/browse/JBESB-823
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Message Store
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
The Message Store was intended to logging, debugging etc. It keeps track of what's on
the wire. We're now using it for the retry/retransmit and DLQ. Even if the same
backend implementation were used, shouldn't that be a separate service? DLQ is for
reliability, whereas the Message Store implementation isn't necessarily reliable or
available to users, e.g., an organisation may not want to expose it's Message Store
details to the world for security reasons, but a general DLQ may be supported by the ESB
for reliability reasons.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:55 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-823) Separate DLQ from Message Store
[ http://jira.jboss.com/jira/browse/JBESB-823?page=comments#action_12372267 ]
Kurt Stam commented on JBESB-823:
---------------------------------
K: Yeah I agree. So I added a new column called 'classification', which basically
enables use to have more types of stores, rather then setting up different db schemas (or
even tables).
The different types are STORE (this is store as intended), and I added DLQ and RDLVR. So
they function independently from one another. Does that answer your question?
M: Sort of: I think that addresses the back-end implementation issue. But I was wondering
about separate services: they may get configured to be the same implementation, but from a
users perspective they could still remain separate. That way if someone wants to have a
separate MessageStore because of security implications, we can support that.
K:The only problem is that we only have one place to configure the store credentials which
is in the jbossesb-properties.xml. A while ago a figured we should move it out and put it
with the
service configuration, but since there was no real hard reason to make clutter up the
service configuration I left it as it was. So it's a config issue only. That said you
could run different stores on different nodes and get around it that way.
M:OK, so it's possible at the moment, just not ideal. I'll add a JIRA task so we
don't forget this conversation and then we can get back to it in a later revision.
K:Sounds good. Or you can make the messageStore use the JCR, and the DLQ/RDLVR the
DBimpl.
Separate DLQ from Message Store
-------------------------------
Key: JBESB-823
URL: http://jira.jboss.com/jira/browse/JBESB-823
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
The Message Store was intended to logging, debugging etc. It keeps track of what's on
the wire. We're now using it for the retry/retransmit and DLQ. Even if the same
backend implementation were used, shouldn't that be a separate service? DLQ is for
reliability, whereas the Message Store implementation isn't necessarily reliable or
available to users, e.g., an organisation may not want to expose it's Message Store
details to the world for security reasons, but a general DLQ may be supported by the ESB
for reliability reasons.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:17 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-823) Separate DLQ from Message Store
[ http://jira.jboss.com/jira/browse/JBESB-823?page=all ]
Mark Little updated JBESB-823:
------------------------------
Fix Version/s: 4.3
Separate DLQ from Message Store
-------------------------------
Key: JBESB-823
URL: http://jira.jboss.com/jira/browse/JBESB-823
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 4.3
The Message Store was intended to logging, debugging etc. It keeps track of what's on
the wire. We're now using it for the retry/retransmit and DLQ. Even if the same
backend implementation were used, shouldn't that be a separate service? DLQ is for
reliability, whereas the Message Store implementation isn't necessarily reliable or
available to users, e.g., an organisation may not want to expose it's Message Store
details to the world for security reasons, but a general DLQ may be supported by the ESB
for reliability reasons.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-823) Separate DLQ from Message Store
[ http://jira.jboss.com/jira/browse/JBESB-823?page=all ]
Mark Little updated JBESB-823:
------------------------------
Fix Version/s: 5.0
(was: 4.3)
Separate DLQ from Message Store
-------------------------------
Key: JBESB-823
URL: http://jira.jboss.com/jira/browse/JBESB-823
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 5.0
The Message Store was intended to logging, debugging etc. It keeps track of what's on
the wire. We're now using it for the retry/retransmit and DLQ. Even if the same
backend implementation were used, shouldn't that be a separate service? DLQ is for
reliability, whereas the Message Store implementation isn't necessarily reliable or
available to users, e.g., an organisation may not want to expose it's Message Store
details to the world for security reasons, but a general DLQ may be supported by the ESB
for reliability reasons.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6069
days inactive
6310
days old
3 comments
2 participants
participants (2)
-
Kurt Stam (JIRA) -
Mark Little (JIRA)