You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/05/12 13:21:55 UTC
[jira] Created: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Axis2FlexibleMEPClient.send logs misleading debug message
---------------------------------------------------------
Key: SYNAPSE-310
URL: https://issues.apache.org/jira/browse/SYNAPSE-310
Project: Synapse
Issue Type: Bug
Components: Core
Reporter: Andreas Veithen
Priority: Minor
Fix For: 1.3
Axis2FlexibleMEPClient.send logs a debug message like this:
DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "George Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753808#action_12753808 ]
George Sanchez commented on SYNAPSE-310:
----------------------------------------
Ok. Instead of having to check for null. I added the Message from and message to log from the synapseOutMessageContext.
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-310)
Axis2FlexibleMEPClient.send logs misleading debug message
Posted by "George Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753808#action_12753808 ]
George Sanchez edited comment on SYNAPSE-310 at 9/10/09 2:01 PM:
-----------------------------------------------------------------
Ok. Instead of having to check for null. I added the Message from and message to log from the synapseOutMessageContext. I will revisit the code again.
was (Author: petabyte):
Ok. Instead of having to check for null. I added the Message from and message to log from the synapseOutMessageContext.
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-310)
Axis2FlexibleMEPClient.send logs misleading debug message
Posted by "George Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753411#action_12753411 ]
George Sanchez edited comment on SYNAPSE-310 at 9/9/09 9:05 PM:
----------------------------------------------------------------
Changed the debug log
was (Author: petabyte):
Change the debug log
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "George Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Sanchez updated SYNAPSE-310:
-----------------------------------
Attachment: Axis2FlexibleMEPClient.patch
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch, Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka reassigned SYNAPSE-310:
-------------------------------------------
Assignee: Hiranya Jayathilaka (was: Ruwan Linton)
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Hiranya Jayathilaka
> Priority: Minor
> Fix For: 2.0
>
> Attachments: Axis2FlexibleMEPClient.patch, Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596290#action_12596290 ]
Ruwan Linton commented on SYNAPSE-310:
--------------------------------------
Yes, we can get the address of the endpoint if specified using the endpoint.getAddress(), and add a conditional to switch between messageContext to address and the received address.
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Priority: Minor
> Fix For: 1.3
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "George Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Sanchez updated SYNAPSE-310:
-----------------------------------
Attachment: Axis2FlexibleMEPClient.patch
Change the debug log
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "George Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759380#action_12759380 ]
George Sanchez commented on SYNAPSE-310:
----------------------------------------
Attached a new patch
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch, Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753550#action_12753550 ]
Hiranya Jayathilaka commented on SYNAPSE-310:
---------------------------------------------
Hi George,
Thanks for the patch.
Just a minor improvement: As mentioned in Ruwan's comment it's better if we can have a conditional to check whether the endpoint address is not null. If it is null we should log the Synapse message context's To address.
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
> Attachments: Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-310:
------------------------------------
Assignee: Ruwan Linton
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Priority: Minor
> Fix For: 1.3
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-310) Axis2FlexibleMEPClient.send logs
misleading debug message
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka resolved SYNAPSE-310.
-----------------------------------------
Resolution: Fixed
Fixed on the trunk
> Axis2FlexibleMEPClient.send logs misleading debug message
> ---------------------------------------------------------
>
> Key: SYNAPSE-310
> URL: https://issues.apache.org/jira/browse/SYNAPSE-310
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Andreas Veithen
> Assignee: Hiranya Jayathilaka
> Priority: Minor
> Fix For: 2.0
>
> Attachments: Axis2FlexibleMEPClient.patch, Axis2FlexibleMEPClient.patch
>
>
> Axis2FlexibleMEPClient.send logs a debug message like this:
> DEBUG Axis2FlexibleMEPClient Sending [add = false] [sec = false] [rm = false] [ mtom = false] [ swa = false] [ format = null] [ force soap11=false] [ force soap12=false] [ pox=false] [ get=false] [ encoding=null] [ to Address: http://www.w3.org/2005/08/addressing/anonymous]
> The "to" address is retrieved using synapseOutMessageContext.getTo(). However, this address is changed later in the code if the EndpointDefinition has a non null address property. Therefore the debug message doesn't show the real destination of the message (as in the example above). This is very misleading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org