Bug 777590 (SOA-98) - Unwanted warning: "No reply to address defined for reply message!"
Summary: Unwanted warning: "No reply to address defined for reply message!"
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-98
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 IR4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 IR5
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA-98
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-06 08:12 UTC by Martin Vecera
Modified: 2011-09-15 06:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
soa-standalone
Last Closed: 2007-11-06 16:14:02 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-98 0 None None None Never

Description Martin Vecera 2007-11-06 08:12:35 UTC
Complexity: Low
Date of First Response: 2007-11-06 11:13:18
project_key: SOA

In the Programmers guide there's is: "Because the recommended interaction pattern for within JBossESB is based on one-way message exchange, responses to messages are not necessarily automatic: it is application dependent as to whether or not a sender expects a response."

In my performance test I don't expect a reply and therefore I'm not setting the reply to field (the documentation says it is not required). Why I'm getting this warning for every single message then?
10:15:27,885 WARN  [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_helloworld_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-116 RelatesTo: jms:correlationID#ID:JBM-610

Printing these warnings on console influences overall performance. This is critical in performance testing. But I don't want to disable all warnings from ActionProcessingPipeline - there can be other important warnings.

I suggest switching this warning to info or hiding it completely.

Comment 1 Mark Little 2007-11-06 16:13:18 UTC
You're getting this warning because the last Action in your chain is returning a Message, which the ESB needs to route somewhere and it's telling you that you haven't provided the "where". You can a) change the Action so it returns null, b) set a ReplyTo, or c) use the  <actions mep="OneWay"> (documented).

Comment 2 Martin Vecera 2007-11-07 07:36:06 UTC
Sorry for wasting your time, this was my mistake. I thought the action was not returning a message but it did.

Comment 3 Mohan Kumar 2011-09-15 06:43:16 UTC
Hi Martin,

I am newbie to the world of Jboss.

Can you please guide to work on sample project to read a data from Database and insert into the another database.

Please Reply to the email-address: mohankumarc8988 

Thanks in Advance.


Note You need to log in before you can comment on or make changes to this bug.