[ESBJAVA-3709] WADL and Swagger support for ESB APIs Created: 22/May/15  Updated: 22/May/15

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

Type: New Feature Priority: High
Reporter: Kasun Indrasiri Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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




[ESBJAVA-3708] Tenant is not getting loaded when coordination is false Created: 21/May/15  Updated: 21/May/15

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

Type: Bug Priority: Highest
Reporter: Malaka Silva Assignee: Malaka Silva
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   

Due to that coordination=false is not supported in tenant mode.



 Comments   
Comment by Malaka Silva [ 21/May/15 ]

https://github.com/wso2/carbon-mediation/pull/172





[ESBJAVA-3707] Getting warnings when Call mediator is followed by an iterate mediator Created: 21/May/15  Updated: 21/May/15  Resolved: 21/May/15

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

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

[2015-05-21 12:19:18,897] WARN - ContinuationStackManager Continuation Stack is empty. Probably due to a configuration issue


<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="sampleProxy"
       transports="https,http"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence>
         <property name="FORCE_SC_ACCEPTED"
                   value="true"
                   scope="axis2"
                   type="STRING"/>
         <call>
            <endpoint>
               <http method="GET"
                     uri-template="http://foo.bar.com"/>
            </endpoint>
         </call>
         <iterate id="it1" expression="//data/foo">
            <target>
               <sequence>
                  <iterate xmlns:ns="http://org.apache.synapse/xsd"
                           id="it2"
                           expression="//data/bar"
                           sequential="true">
                     <target>
                        <sequence>
                        </sequence>
                     </target>
                  </iterate>
               </sequence>
            </target>
         </iterate>
         <log level="custom">
            <property name="done" value="yes"/>
         </log>
      </inSequence>
   </target>
   <description/>
</proxy>








 Comments   
Comment by Isuru Udana Loku Narangoda [ 21/May/15 ]

Regression of ESBJAVA-3634

Comment by Isuru Udana Loku Narangoda [ 21/May/15 ]

Fixed with https://github.com/wso2/wso2-synapse/pull/200





[ESBJAVA-3706] Taking long time to start the server Created: 21/May/15  Updated: 21/May/15

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

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

 Description   

After introducing CXF inbound, ESB pack takes long time to start. Removing cxf bundle, solves the problem. So it is something to do with CXF bundles






[ESBJAVA-3705] Invalid log when starting HL7 inbound endpoint Created: 21/May/15  Updated: 21/May/15

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

Type: Bug Priority: Normal
Reporter: Ravi Undupitiya Assignee: Ravi Undupitiya
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   

[2015-05-21 11:34:06,518] INFO - InboundEndpoint Initializing Inbound Endpoint: TestEP
[2015-05-21 11:34:06,521] INFO - InboundHL7Listener Starting MLLP Transport Reactor
[2015-05-21 11:34:06,523] INFO - InboundHL7Listener Starting HL7 Inbound Endpoint on port 0
[2015-05-21 11:34:06,523] INFO - InboundHL7IOReactor MLLP Transport IO Reactor Started
[2015-05-21 11:34:06,525] INFO - HL7EndpointManager Starting HL7 Inbound Endpoint on port 9090






[ESBJAVA-3704] Startup errors when having https inbound endpoints Created: 21/May/15  Updated: 21/May/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: isuru ranawaka
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   

[2015-05-21 10:15:40,670] ERROR - PassThroughListeningIOReactorManager Cannot Start Endpoint for EP2
java.lang.Exception: Cannot create ServerConnectionFactory for EP2in port 6666already registered a server connection factory
at org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager.getSharedSSLIOReactor(PassThroughListeningIOReactorManager.java:586)
at org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager.startDynamicPTTSSLEndpoint(PassThroughListeningIOReactorManager.java:182)
at org.apache.synapse.transport.passthru.api.PassThroughInboundEndpointHandler.startSSLEndpoint(PassThroughInboundEndpointHandler.java:105)
at org.wso2.carbon.inbound.endpoint.protocol.http.management.HTTPEndpointManager.startSSLListener(HTTPEndpointManager.java:164)
at org.wso2.carbon.inbound.endpoint.EndpointListenerLoader.loadListeners(EndpointListenerLoader.java:63)
at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:258)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)



 Comments   
Comment by isuru ranawaka [ 21/May/15 ]

https://github.com/wso2/carbon-mediation/pull/170





[ESBJAVA-3703] [BAM Mediator] Possible OOM due to BAM mediator creating SynapseXPath object per request Created: 20/May/15  Updated: 22/May/15

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 4.6.0
Fix Version/s: FUTURE

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

Attachments: File ESB_3703.diff    
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   

The following code segment creates a new SynapseXPath object per each request.

            String stringProperty;
            String propertyType;
            if(property.isExpression()){
                SynapseXPath synapseXPath = new SynapseXPath(property.getValue());
                stringProperty = synapseXPath.stringValueOf(messageContext);
            } else {
                stringProperty =  property.getValue();
            }

This can cause performance degradation. Also the underlying XPathFactory created by Synapse is not thread safe [1].

[1] http://docs.oracle.com/javase/7/docs/api/javax/xml/xpath/XPathFactory.html



 Comments   
Comment by Isuru Udana Loku Narangoda [ 22/May/15 ]

Lasantha,

Can you please attach the diff to fix the issue ?

Comment by Isuru Udana Loku Narangoda [ 22/May/15 ]

Vijitha,

We need to check the possibility of OOM in new data publisher mediators also.

Comment by Lasantha Fernando [ 22/May/15 ]

Sorry, forgot to add PR and diff.

PR - https://github.com/wso2/carbon-mediation/pull/171

Diff attached in ESB_3703.diff.

Thanks,
Lasantha





[ESBJAVA-3702] HTTPS Inbound UI Optional params Created: 20/May/15  Updated: 21/May/15  Resolved: 21/May/15

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

Type: Bug Priority: Highest
Reporter: Isuru Udana Loku Narangoda Assignee: isuru ranawaka
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   

Make optional parameters optional in UI.

In ui, we cannot leave optional parameters as optional, it throws many errors if we if leave them blank.



 Comments   
Comment by isuru ranawaka [ 21/May/15 ]

https://github.com/wso2/carbon-mediation/pull/166





[ESBJAVA-3700] Updating the Kafka in Kafka Inbound EP Created: 19/May/15  Updated: 19/May/15

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

Type: Improvement Priority: Normal
Reporter: Kathees Rajendram Assignee: Kathees Rajendram
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-3699] support dynamic xpath expression generation in ESB Created: 19/May/15  Updated: 19/May/15

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

Type: New Feature Priority: Normal
Reporter: Rajith Vitharana 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

 Description   

Current ESB doesn't support dynamic xpath expression generation.
Requirement is to generate the xpath expression at runtime

example would be as follows

<property name="sampleCode4"
expression="//sfobject[en_US='$ctx:sample']/externalCode/text()"/>






[ESBJAVA-3698] Behavior of Message Building in ESB with different payload types and content types Created: 19/May/15  Updated: 22/May/15

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

Type: Bug Priority: Normal
Reporter: Ravindra Ranwala Assignee: Ravindra Ranwala
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive Test-Artifacts.zip     File invalid-content-type-FIX.diff    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

There are 3 different scenarios to be covered here.
1) Send text/xml payload with application/json content type
2.) Send application/json payload with text/xml content type
3.) Send application/json payload with some invalid content type such as application/test

First two scenarios should throw AxisFaults and should be consistent with each other. Third scenario will not have a matching builder and hence throws an OMException while building the message. This can not be solved and we don't see any inconsistent behaviour coming due to that.



 Comments   
Comment by Ravindra Ranwala [ 21/May/15 ]

All the test artifacts used to reproduce the issue is attached here.

Comment by Ravindra Ranwala [ 21/May/15 ]

The diff file is attached to the ticket.





[ESBJAVA-3697] Test and document the process of upgrading from ESB 4.8.1 to ESB 4.9.0 Created: 19/May/15  Updated: 19/May/15

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

Type: Task Priority: Highest
Reporter: Kasun Indrasiri 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

 Description   

The content in https://docs.wso2.com/display/ESB490/Upgrading+from+the+Previous+Release can be used as a draft and steps can be added/removed as required while testing the upgrade






[ESBJAVA-3696] When a RM message comes to a tenant that is unloaded, that message is lost, subsequent messages are accepted Created: 18/May/15  Updated: 18/May/15  Resolved: 18/May/15

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

Type: Bug Priority: Highest
Reporter: Sandamal Weerasinghe Assignee: Kasun Indrasiri
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: No

 Comments   
Comment by Sandamal Weerasinghe [ 18/May/15 ]

fixed with https://github.com/wso2/wso2-synapse/pull/198





[ESBJAVA-3695] Supporting ISO8583 protocol with WSO2 ESB Created: 18/May/15  Updated: 18/May/15

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

Type: New Feature Priority: Normal
Reporter: Chanaka Fernando Assignee: Kasun Indrasiri
Resolution: Unresolved Votes: 0
Labels: ESB
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: No
Affects Docs:
Yes

 Description   

ISO8583 is a standard used in exchanging credit card information. This has been heavily used in banking industry. Supporting this protocol in WSO2 ESB will make it more useful for our banking customers. [1] and [2] are sample implementations.

[1] http://manoj-fernando.blogspot.com/2013/08/iso8583-with-wso2-esb.html

[2] https://github.com/vanjikumaran/ISO8583Mediator






Generated at Sat May 23 06:41:26 IST 2015 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.