[ESBJAVA-3653] Header lost in processor mediator Created: 17/Apr/15  Updated: 17/Apr/15

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

Type: Bug Priority: Highest
Reporter: Sajini De Silva Assignee: Isuru Udana Loku Narangoda
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   

My use case is to listen to a message queue and when a message is received, consume it and send it to a secured backend. Username and password for the backend is saved in a configuration file in registry.
I was able to successfully implement the message storing and forwarding part without authentication. For authentication part, I''m setting user name and password to message header. But header is missing when it comes out from processor mediator.






[ESBJAVA-3652] Upgrade HTTP Core Nio version to handle SSL Renegotiation Created: 16/Apr/15  Updated: 16/Apr/15

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

Type: Improvement Priority: Highest
Reporter: Isuru Wimalasundera Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

When invoking a backend endpoint which does SSL renegotiation using Passthrough transport or NIO transport the request times out. This happens because of the second SSL handshake done in SSL renegotiation is not identified by the above mentioned transports.

The workaround for this issue is to use Callout mediator. But since this has already been fixed in latest HTTP Core Nio, the products should upgraded to use this new version.



 Comments   
Comment by Isuru Wimalasundera [ 16/Apr/15 ]

Please refer the issue https://issues.apache.org/jira/browse/HTTPCORE-371





[ESBJAVA-3651] Target Handler Unexpected Error during load testing Created: 16/Apr/15  Updated: 16/Apr/15

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

Type: Bug Priority: Normal
Reporter: isuru ranawaka Assignee: Kasun Indrasiri
Resolution: Unresolved 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




[ESBJAVA-3650] HTTP headers are not preserved when the message goes through Message store > Message processor Created: 16/Apr/15  Updated: 16/Apr/15

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

Type: Bug Priority: Highest
Reporter: Isuru Udana Loku Narangoda Assignee: shafreen anfar
Resolution: Unresolved 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   

Sample 702 with Authorization header
--------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
   <endpoint name="StockQuoteServiceEp">
      <address uri="http://localhost:9000/services/SimpleStockQuoteService">
         <suspendOnFailure>
            <errorCodes>-1</errorCodes>
            <progressionFactor>1.0</progressionFactor>
         </suspendOnFailure>
      </address>
   </endpoint>
   <sequence name="fault">
      <log level="full">
         <property name="MESSAGE" value="Executing default 'fault' sequence"/>
         <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
         <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
      </log>
      <drop/>
   </sequence>
   <sequence name="main">
      <in>
         <log level="full"/>
         <property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
         <property name="Authorization" value="foo:bar" scope="transport"/>
         <property name="OUT_ONLY" value="true"/>
         <property name="target.endpoint" value="StockQuoteServiceEp"/>
         <store messageStore="MyStore"/>
        </in>
      <description>The main sequence for the message mediation</description>
   </sequence>
   <messageStore name="MyStore"/>
   <messageProcessor class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
                     name="ScheduledProcessor"
                     messageStore="MyStore">
      <parameter name="interval">10000</parameter>
   </messageProcessor>
</definitions>



 Comments   
Comment by Isuru Udana Loku Narangoda [ 16/Apr/15 ]

If we remove FORCE_FC_ACCEPTED headers are getting transferred. So it looks like TRANSPORT_HEADER map is getting removed when acknowledging client with 202.
If we put store mediator within a clone mediator, it works fine.
So this means we need to clone the entire message context before passing to the message producer. Cloning only the message body is not sufficient.





[ESBJAVA-3649] AvoidInitiation=false results in no management console Created: 15/Apr/15  Updated: 15/Apr/15

Status: Open
Project: WSO2 ESB
Component/s: Administration Console, Core Engine
Affects Version/s: 4.8.1
Fix Version/s: None

Type: Bug Priority: Low
Reporter: Colin Roy-Ehri Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 3.13.0-24-generic, amd64
Java Version : 1.7.0_60 64-Bit


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

 Description   

When the axis2.xml AvoidInitialization parameter is set to 'false', the tomcat server fails to initialize properly and the management console cannot be reached.






[ESBJAVA-3648] Can create Proxy with "-" in its name in Developper Studio 3.7.1 but cannot edit it Created: 14/Apr/15  Updated: 14/Apr/15

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

Type: Bug Priority: Normal
Reporter: Ravaka Razafimanantsoa Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB, developerStudio
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian Wheezy
Developper Studio 3.7.1
ESB 4.8.1


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: No

 Description   

Hi !

I can create a proxy with "-" in its name in Developper Studio 3.7.1. I can deploy it and use it without problem.

When I try to edit the source, when saving, I get the following error :"Unable to find proper name attribute in the XML".

Best regards,

Ravaka






[ESBJAVA-3647] SimpleDateFormat in org.apache.synapse.transport.nhttp.debug.AbstractConnectionDebug needs to be synchronized Created: 14/Apr/15  Updated: 14/Apr/15

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.0
Fix Version/s: 4.9.0 - M8

Type: Bug Priority: Highest
Reporter: Sandamal Weerasinghe Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File diff.patch    
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: Not-applicable

 Description   

SimpleDateFormat is not thread safe, should not use 1 implementation of SimpleDateFormat across multiple threads.






[ESBJAVA-3646] Calling multiple endpoint Created: 13/Apr/15  Updated: 13/Apr/15

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

Type: Bug Priority: Normal
Reporter: Przemyslaw Moskal Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
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   

When recall endpoint (sometimes for a second, sometimes for the fourth time) at an interval of 2-3 seconds, I get timed out. Backend service referenced by the endpoint for sure answer, but I did not get any response.

Configuration my endpoint:
<call>
<endpoint>
<default format="soap11">
<timeout>
<duration>60000</duration>
<responseAction>fault</responseAction>
</timeout>
<suspendOnFailure>
<initialDuration>2000</initialDuration>
<progressionFactor>1.0</progressionFactor>
<maximumDuration>3000</maximumDuration>
</suspendOnFailure>
</default>
</endpoint>
</call>

wso2-esb-errors.log:
[HTTPS-Listener I/O dispatcher-1] WARN SourceHandler Connection time out after request is read: http-incoming-45
[HTTPS-Sender I/O dispatcher-1] WARN TargetHandler http-outgoing-31: Connection time out while in state: REQUEST_DONE
[PassThroughMessageProcessor-120] WARN FaultHandler ERROR_CODE : 101507
[PassThroughMessageProcessor-120] WARN FaultHandler ERROR_MESSAGE : Error in Sender
[PassThroughMessageProcessor-120] WARN FaultHandler ERROR_DETAIL : Error in Sender
[PassThroughMessageProcessor-120] WARN FaultHandler ERROR_EXCEPTION : null
[PassThroughMessageProcessor-120] WARN FaultHandler FaultHandler : AnonymousEndpoint
[PassThroughMessageProcessor-120] WARN EndpointContext Endpoint : AnonymousEndpoint will be marked SUSPENDED as it failed
[PassThroughMessageProcessor-120] WARN EndpointContext Suspending endpoint : AnonymousEndpoint - current suspend duration is : 2000ms - Next retry after :






[ESBJAVA-3645] ESB drops attachment when we define wsdlendpoint Created: 12/Apr/15  Updated: 12/Apr/15

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

Type: Bug Priority: Highest
Reporter: Vijayaratha Vijayasingam Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Defined a wsdlproxy and sends an attachment. From the wirelog, esb receives the attachment, but not forwarding that to backend.

Related jira
https://wso2.org/jira/browse/APIMANAGER-3440






Generated at Sun Apr 19 05:04:09 IST 2015 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.