[JBoss JIRA] Created: (JBESB-1282) How does DLQ work when message payload types are out of scope of the service?
6:04 a.m.
How does DLQ work when message payload types are out of scope of the service?
-----------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
9:19 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1282) How does DLQ work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=comments#action_12385290 ]
Kurt Stam commented on JBESB-1282:
----------------------------------
Let me clarify this. This is a generic issue with our transport where do NOT leave the
payload opaque. Instead we serialize the *entire* message on the way out and deserialize
it on reception in the Courier. So now this courier will need access to the specific java
classes contained in the message (let's say the dvd store classes). This is a
consequence of the transport/message Implementation design and has nothing to do with the
DLQ Service.
IMO we should leave the payload OPAQUE until we need to interact with the message. This
will make sending messages around much easier.
How does DLQ work when message payload types are out of scope of the
service?
-----------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
9:21 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1282) How does DLQ work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=all ]
Kurt Stam updated JBESB-1282:
-----------------------------
Attachment: stack.txt
the stacktrace.
How does DLQ work when message payload types are out of scope of the
service?
-----------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
9:23 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=all ]
Kurt Stam updated JBESB-1282:
-----------------------------
Summary: How does a service work when message payload types are out of scope of the
service? (was: How does DLQ work when message payload types are out of scope of the
service?)
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
10:17 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=comments#action_12385312 ]
Kevin Conner commented on JBESB-1282:
-------------------------------------
The generic problem with this issue is that each service is forced to deserialise the
object when the message is deserialised. It is not just the DLQ which will be affected by
this, all other services will be.
It should be possible to modify the message implementation so that this deserialising is
done on a Just In Time basis, this would solve the generic problem.
This will not happen for the GA though, it will have to make it into the release (CP and
trunk) at a later date.
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
10:59 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=comments#action_12385330 ]
Tom Fennelly commented on JBESB-1282:
-------------------------------------
Kurt and I had a chat about this and came to the conclusion that there 2 issues... the
generic issue as described by Kev above (i.e that the message payload is not opaque) and
that there's potentially a general "patterns" type issue re whether or not
messages being sent to the DLQ (or other orthogonal type services) should themselves be
wrapped as payloads to a new message that is itself governed by its own set of contracts
(i.e. between the ServiceInvoker and the DLQ).
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
12:23 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=all ]
Kurt Stam closed JBESB-1282.
----------------------------
Resolution: Done
Further discussion on the forum:
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
12:23 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=all ]
Kurt Stam reopened JBESB-1282:
------------------------------
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
12:23 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1282) How does a service work when message payload types are out of scope of the service?
[ http://jira.jboss.com/jira/browse/JBESB-1282?page=all ]
Kurt Stam closed JBESB-1282.
----------------------------
Resolution: Rejected
How does a service work when message payload types are out of scope
of the service?
-----------------------------------------------------------------------------------
Key: JBESB-1282
URL: http://jira.jboss.com/jira/browse/JBESB-1282
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1 IR2
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2.1 triage
Attachments: stack.txt
Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a
failed message that contains payload types that it knows nothing about... what should
happen?
I'm seeing an exception related to this on th aggregator quickstart. The DLQ service
is running on the AS, while the individual serives are all running standalone. The DLQ
Service has no visibility on the payload types bound to them failed messages that get
delivered to it.
--
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
6236
days inactive
6236
days old
8 comments
3 participants
participants (3)
-
Kevin Conner (JIRA) -
Kurt Stam (JIRA)
-
Tom Fennelly (JIRA)