[ESBJAVA-5063] Request message tracing through ESB Created: 28/Mar/17  Updated: 28/Mar/17

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

Type: Improvement Priority: Highest
Reporter: Lasindu Charith 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: Advanced
Test cases added: Yes

 Description   

Currently ESB does not have a direct way to trace a given message end to end, where a user can obtain all the information a given message/flow. (Even though using a combination of logs and analytics could work, this is not something available OOTB). It would be good to have this feature for easy debugging and many of the current systems has this built-in nowadays.

i.e tracing a combination of synapse messageId and requestId throughout the mediation flows






[ESBJAVA-5062] Add Amazon Linux AMI to tested operative systems Created: 27/Mar/17  Updated: 27/Mar/17

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

Type: Wish Priority: Normal
Reporter: Miguel Lorono 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
Test cases added: Yes

 Description   

I would like to know if Amazon Linux AMI is tested with following WSO2 Products:

  • WSO2 ESB 5.0.0
  • WSO2 ESB-Analitics 5.0.0 (DAS 3.1.0)

Thanks.






[ESBJAVA-5061] Two test cases are failure in Product-ESB in "tests-service" module Created: 27/Mar/17  Updated: 27/Mar/17

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

Type: Bug Priority: Normal
Reporter: vivekananthan sivanayagam 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
Test cases added: Yes

 Description   

I am getting the following error[1] in testDynamicDelayedTimeoutEndpoint and testDynamicDelayedTimeoutTemplateEndpoint[2] when building the Product ESB.

[1]
FAILED: testDynamicDelayedTimeoutEndpoint
Test delayed endpoint with dynamic timeout
java.lang.AssertionError: expected:<

{"error_code" : 101504, "error_msg" : Send timeout}

> but was:<

{"error_code" : 101504, "error_msg" : "Send timeout"}

>

FAILED: testDynamicDelayedTimeoutTemplateEndpoint
Test template endpoint with dynamic delayed timeout
java.lang.AssertionError: expected:<

{"error_code" : 101504, "error_msg" : Send timeout}

> but was:<

{"error_code" : 101504, "error_msg" : "Send timeout"}

>

[2]
@Test(groups =

{ "wso2.esb" }, description = "Test template endpoint with dynamic delayed timeout")
public void testDynamicDelayedTimeoutTemplateEndpoint() throws Exception {
String request = "{}";
String response = sendRequest(getProxyServiceURLHttp("MockDelayedTimeoutTemplateProxy"), request);
Assert.assertEquals(response, "{\"error_code\" : 101504, \"error_msg\" : Send timeout}");
}

After I made the modification like below, getting build success.

@Test(groups = { "wso2.esb" }

, description = "Test delayed endpoint with dynamic timeout")
public void testDynamicDelayedTimeoutEndpoint() throws Exception {
String request = "{}";
String response = sendRequest(getProxyServiceURLHttp("MockDelayedTimeoutProxy"), request);
Assert.assertEquals(response, "

{\"error_code\" : 101504, \"error_msg\" : \"Send timeout\"}

");
}

@Test(groups =

{ "wso2.esb" }

, description = "Test template endpoint with dynamic delayed timeout")
public void testDynamicDelayedTimeoutTemplateEndpoint() throws Exception {
String request = "{}";
String response = sendRequest(getProxyServiceURLHttp("MockDelayedTimeoutTemplateProxy"), request);
Assert.assertEquals(response, "

{\"error_code\" : 101504, \"error_msg\" : \"Send timeout\"}

");
}



 Comments   
Comment by vivekananthan sivanayagam [ 27/Mar/17 ]

Please find the PR[1]

[1] https://github.com/wso2/product-esb/pull/652





[ESBJAVA-5060] Support HTTP DELETE with content body Created: 24/Mar/17  Updated: 24/Mar/17

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

Type: Bug Priority: Highest
Reporter: Chanaka Fernando 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   

In the existing ESB, it drops the content when sending out HTTP DELETE request. This has already been reported on HTTP-CORE and fixed in the latest version [1]. We need to include this fix with the future ESB version.

[1] https://issues.apache.org/jira/browse/HTTPCORE-380



 Comments   
Comment by Chanaka Fernando [ 24/Mar/17 ]

Fixes are mentioned in the below email thread.

http://mail.wso2.org/mailarchive/dev/2014-January/027006.html





[ESBJAVA-5059] Transaction support for RabbitMQ inbound endpoint Created: 24/Mar/17  Updated: 24/Mar/17

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

Type: Improvement Priority: Normal
Reporter: Indika Sampath Assignee: Indika Sampath
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   

Transaction support needs to implement in the RabbitMQ inbound endpoint.

Inbound Endpoint - RabbitMQConsumer.xml

<?xml version="1.0" encoding="UTF-8"?>
<inboundEndpoint xmlns="http://ws.apache.org/ns/synapse"
                 name="RabbitMQConsumer"
                 sequence="amqpSeq"
                 onError="amqpErrorSeq"
                 protocol="rabbitmq"
                 suspend="false">
   <parameters>
      <parameter name="sequential">true</parameter>
      <parameter name="coordination">true</parameter>
      <parameter name="rabbitmq.connection.factory">AMQPConnectionFactory</parameter>
      <parameter name="rabbitmq.server.host.name">localhost</parameter>
      <parameter name="rabbitmq.server.port">5672</parameter>
      <parameter name="rabbitmq.server.user.name">guest</parameter>
      <parameter name="rabbitmq.server.password">guest</parameter>
      <parameter name="rabbitmq.queue.name">queue</parameter>
      <parameter name="rabbitmq.exchange.name">exchange</parameter>
      <parameter name="rabbitmq.queue.durable">true</parameter>
      <parameter name="rabbitmq.queue.exclusive">false</parameter>
      <parameter name="rabbitmq.queue.auto.delete">false</parameter>
      <parameter name="rabbitmq.queue.auto.ack">false</parameter>
      <parameter name="rabbitmq.exchange.durable">true</parameter>
      <parameter name="rabbitmq.exchange.auto.delete">false</parameter>
      <parameter name="rabbitmq.message.content.type">text/xml</parameter>
      <parameter name="rabbitmq.connection.ssl.enabled">false</parameter>
   </parameters>
</inboundEndpoint>

Sequence - amqpSeq.xml

<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="http://ws.apache.org/ns/synapse"
          name="amqpSeq"
          onError="amqpErrorSeq">
   <property name="OUT_ONLY" value="true"/>
   <callout serviceURL="http://localhost:9000/services/SimpleStockQuoteService">
      <source type="envelope"/>
      <target key="placeOrder"/>
   </callout>
   <log level="custom">
      <property name="Transaction Action" value="Committed"/>
   </log>
</sequence>

Error Sequence - amqpErrorSeq.xml

<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="http://ws.apache.org/ns/synapse" name="amqpErrorSeq">
   <property name="SET_ROLLBACK_ONLY" value="true" scope="default"/>
   <log level="custom">
      <property name="Transaction Action" value="Rollbacked"/>
   </log>
</sequence>





[ESBJAVA-5058] Add initAxis2ClientOptions to Call mediator in blocking mode Created: 23/Mar/17  Updated: 23/Mar/17

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

Type: Improvement Priority: Normal
Reporter: Maduranga Siriwardena 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
Test cases added: Yes

 Description   

CallOut mediator has option initAxis2ClientOptions which will use the options from Axis2MessageContext of synapseInMsgCtx [1] instead of initializing. But in the Call mediator in blocking mode does not has this option.

[1] https://github.com/wso2/wso2-synapse/blob/v2.1.7-wso2v7/modules/core/src/main/java/org/apache/synapse/message/senders/blocking/BlockingMsgSender.java#L164






[ESBJAVA-5057] Security Policy reset after server restart Created: 23/Mar/17  Updated: 23/Mar/17

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

Type: Bug Priority: Normal
Reporter: Udani Gunawardena 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
Test cases added: Yes

 Description   

Security Policy applied to a proxy service is being reset after server restart.

Steps to reproduce:
1. Create a proxy service.
2. Go to Service Dashboard of the particular service.
3. Click "policies" under "Quality of Service Configuration" section.
4. Click "Edit policy" button in the service level.(under
Service Hierarchy)
5. Edit the policy and save.
6. Restart the server.

The policy which is set previously has been reset after server restart.






[ESBJAVA-5056] Need to add the feature to externalise the username, password and url in dblookup mediator Created: 22/Mar/17  Updated: 22/Mar/17

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

Type: Task Priority: Highest
Reporter: Shakila Sivagnanarajah 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   

It would be great to have the feature to get the username, password and url from environment variable or registry or message context in dblookup mediator. So that the end user can externalise those properties and it does not require the code change in case of the value change.






Generated at Wed Mar 29 04:52:25 IST 2017 using JIRA 7.2.2#72004-sha1:9d5132893cc8c728a3601a9034a1f8547ef5c7be.