[ESBJAVA-4969] ESB drops the generated Response Body generated within the ESB flow when HTTP 404 Response with Empty Body from Backend with Content-Length: 0 Header Created: 08/Dec/16  Updated: 08/Dec/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: Vijitha Ekanayake Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Critical
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When REST Backend sends a Response with HTTP SC 404 with Empty Body and Content-Length Header value 0, ESB fails to respond with the generated Body in the ESB flow.

If the REST Backend responds with Transfer-Encoding: chunked instead of the Contnet-Length Header, it works fine.






[ESBJAVA-4968] HTML response is returned for WS-Security errors. Created: 08/Dec/16  Updated: 08/Dec/16

Status: Open
Project: WSO2 ESB
Component/s: Core Engine
Affects Version/s: 4.9.0
Fix Version/s: FUTURE

Type: Patch Priority: Highest
Reporter: Asela Pathberiya Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Estimated Complexity: Moderate
Test cases added: Yes

 Description   

This is a spec violation according to line 2043 of [2]. A SOAP Fault should be returned instead.

[1] https://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf






[ESBJAVA-4967] Cannot remove API when created by CAPP Created: 08/Dec/16  Updated: 08/Dec/16

Status: Open
Project: WSO2 ESB
Component/s: API
Affects Version/s: 5.0.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Kleber Rocha Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WSO2ESB 5.0.0, RedHat Linux 7, Java 1.8.0_112


Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

When deployed a CAPP with API, everything works fine, but when I tried delete CAPP ou redeploy CAPP, the API cannot removed, only after restart server, API is removed. These problema only happens with API, sequence, endpoints work fine.

Thank you






[ESBJAVA-4966] ESB sample 800 get failed Created: 05/Dec/16  Updated: 05/Dec/16  Resolved: 05/Dec/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 5.0.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Nuwan Wimalasekara Assignee: Nuwan Wimalasekara
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When the incoming message does not have the content type, It fail to set the content type, when the backend endpoint format is SOAP11 and SOAP12

Ex: Get request does not send the content type

https://docs.wso2.com/display/ESB500/Sample+800%3A+Introduction+to+REST+API



 Comments   
Comment by Nuwan Wimalasekara [ 05/Dec/16 ]

Fixed in https://github.com/wso2/wso2-synapse/pull/681





[ESBJAVA-4965] LogMediator doesn't manage well debug and trace category Created: 02/Dec/16  Updated: 02/Dec/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: gregory eve Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0
Test cases added: Yes

 Description   

If we want to log a message with LogMediator in debug or trace category. We need to set the Logger of the mediator in DEBUG/TRACE. if we do that we will have all the log messages of all the proxy services, APIS, etc. we can not restrict it to only on one proxy service for example

The problem in the implementation is that the level of log of the implementation of the LogMediator and the level of Log in which the end user want to log its own message are linked.

LogMEdiator.java

            case CATEGORY_TRACE :
            	if(synLog.isTraceEnabled()){
            		synLog.auditTrace(getLogMessage(synCtx));
            	}
                break;
            case CATEGORY_DEBUG :
            	if(synLog.isDebugEnabled()){
            		synLog.auditDebug(getLogMessage(synCtx));
            	}
                break;

synLog.isDebugEnabled() / synLog.isTraceEnabled() return the level of the LogMediator Logger not the the Level of the Service Logger.

So if you set

  • your service logger to debug and log mediator logger to info no log will be generated
  • your service logger to info and log mediator logger to debug log of the mediator and log of the end user will be generated
  • your service logger to debug and log mediator to debug log will be generated on each logger

First case is not working and it's a bug.






Generated at Thu Dec 08 21:34:10 IST 2016 using JIRA 7.2.2#72004-sha1:9d5132893cc8c728a3601a9034a1f8547ef5c7be.