[
https://jira.jboss.org/jira/browse/JBESB-3103?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3103:
-------------------------------------
This is by design.
The first one is logged by the ServiceInvoker for synchronous messages (logged but no
delivery retries) and can be configured on a global and/or per message basis.
The second is because your service uses default or oneway semantics as seen by the
following
2010-01-07 14:12:44,890 WARN
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-26-thread-1) No fault
address defined for fault message!
Message is sent to DLQ two times.
----------------------------------
Key: JBESB-3103
URL:
https://jira.jboss.org/jira/browse/JBESB-3103
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.7
Reporter: Boris Belovic
Priority: Minor
Attachments: server.log, ssi.tar.bz2
I have a small ESB service with SyncServiceInvoker action. When service invoker timeout
is exceeded in proxied service, the message is sent to DLQ This is the first time the
message is sent to DLQ. After this, there is a ResponseTimeoutException (which is
expected) and the message is sent to DLQ for second time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira