[ESBJAVA-4601] When creating an endpoint template and defining template endpoint with dynamic duration it fails Created: 05/May/16  Updated: 05/May/16

Status: Open
Project: WSO2 ESB
Component/s: Endpoints Management, Templates
Affects Version/s: 5.0.0 - Alpha
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: Chathurika De Silva Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

JDK: 1.8.0
OS:Ubuntu 14.04


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

Tried to create a endpoint template and use it in template endpoint. It failed with the following error

Template

<template xmlns="http://ws.apache.org/ns/synapse" name="NewTemplate">
   <endpoint name="$name">
      <address uri="$uri">
         <suspendOnFailure>
            <progressionFactor>1.0</progressionFactor>
         </suspendOnFailure>
         <markForSuspension>
            <retriesBeforeSuspension>0</retriesBeforeSuspension>
            <retryDelay>0</retryDelay>
         </markForSuspension>
         <timeout>
            <responseAction>discard</responseAction>
            <duration>$du</duration>
         </timeout>
      </address>
   </endpoint>
</template>

Endpoint

<endpoint xmlns="http://ws.apache.org/ns/synapse" template="NewTemplate" name="newEndpoint" uri="http://10.100.5.63:8080/erandi">
   <axis2ns10:parameter xmlns:axis2ns10="http://ws.apache.org/ns/synapse" name="du" value="{get-property('timeout')}"/>
</endpoint>

Exception

[2016-05-05 17:25:02,885] ERROR - EndpointAdmin Unable to add Endpoint 
org.apache.synapse.SynapseException: Endpoint timeout duration expected as a number but was not a number
	at org.apache.synapse.config.xml.endpoints.EndpointDefinitionFactory.handleException(EndpointDefinitionFactory.java:357)
	at org.apache.synapse.config.xml.endpoints.EndpointDefinitionFactory.createDefinition(EndpointDefinitionFactory.java:156)
	at org.apache.synapse.config.xml.endpoints.AddressEndpointFactory.createEndpointDefinition(AddressEndpointFactory.java:112)
	at org.apache.synapse.config.xml.endpoints.AddressEndpointFactory.createEndpoint(AddressEndpointFactory.java:86)
	at org.apache.synapse.config.xml.endpoints.EndpointFactory.createEndpointWithName(EndpointFactory.java:143)
	at org.apache.synapse.config.xml.endpoints.EndpointFactory.getEndpointFromElement(EndpointFactory.java:80)
	at org.apache.synapse.endpoints.Template.create(Template.java:59)
	at org.apache.synapse.endpoints.TemplateEndpoint.reLoadAndInitEndpoint(TemplateEndpoint.java:137)
	at org.apache.synapse.endpoints.TemplateEndpoint.init(TemplateEndpoint.java:101)
	at org.wso2.carbon.endpoint.service.EndpointAdmin.addEndpoint(EndpointAdmin.java:182)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
	at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
	at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
	at org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.wso2.carbon.endpoint.stub.types.EndpointAdminStub.addEndpoint(EndpointAdminStub.java:2212)
	at org.wso2.carbon.endpoint.ui.client.EndpointAdminClient.addEndpoint(EndpointAdminClient.java:68)
	at org.apache.jsp.endpoints.ajaxprocessors.submitEndpoint_002dajaxprocessor_jsp._jspService(submitEndpoint_002dajaxprocessor_jsp.java:144)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
	at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)
[2016-05-05 17:25:02,896] ERROR - EndpointAdminClient Endpoint timeout duration expected as a number but was not a number
org.apache.axis2.AxisFault: Endpoint timeout duration expected as a number but was not a number
	at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
	at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.wso2.carbon.endpoint.stub.types.EndpointAdminStub.addEndpoint(EndpointAdminStub.java:2212)
	at org.wso2.carbon.endpoint.ui.client.EndpointAdminClient.addEndpoint(EndpointAdminClient.java:68)
	at org.apache.jsp.endpoints.ajaxprocessors.submitEndpoint_002dajaxprocessor_jsp._jspService(submitEndpoint_002dajaxprocessor_jsp.java:144)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
	at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)

When the same configuration is copied to the Source configuration following log was observed

[2016-05-05 17:19:21,646] ERROR - EndpointDefinitionFactory Endpoint timeout duration expected as a number but was not a number
[2016-05-05 17:19:21,647] ERROR - SynapseConfiguration  Error in initializing endpoint [newEndpoint] Endpoint timeout duration expected as a number but was not a number
[2016-05-05 17:25:02,884] ERROR - EndpointDefinitionFactory Endpoint timeout duration expected as a number but was not a number






[ESBJAVA-4600] [Data Mapper]Cannot map Array elements Created: 05/May/16  Updated: 05/May/16

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

Type: Bug Priority: High
Reporter: Viraj Rajaguru Assignee: Viraj Rajaguru
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

 Description   

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:enterprise.soap.sforce.com">
<soapenv:Header>
<urn:SessionHeader>
<urn:sessionId><b>QwWsHJyTPW.1pd0_jXlNKOSU</b></urn:sessionId>
</urn:SessionHeader>
</soapenv:Header>
<soapenv:Body>
<urn:delete>
<!-Zero or more repetitions:->
<urn:ids><b>003D000000OXWBg</b></urn:ids>
<urn:ids><b>003D000000OXWBh</b></urn:ids>
</urn:delete>
</soapenv:Body>
</soapenv:Envelope>

We cannot map field value of <b> in <urn:ids> array.






[ESBJAVA-4599] [Data Mapper]Cannot map attributes with namespaces Created: 05/May/16  Updated: 05/May/16

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

Type: Bug Priority: High
Reporter: Viraj Rajaguru Assignee: Viraj Rajaguru
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

 Description   

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:enterprise.soap.sforce.com"
xmlns:urn1="urn:sobject.enterprise.soap.sforce.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<urn:SessionHeader>
<urn:sessionId><b>QwWsHJyTPW.1pd0_jXlNKOSU</b></urn:sessionId>
</urn:SessionHeader>
</soapenv:Header>
<soapenv:Body>
<urn:upsert>
<!-Custom Field defined in Setup as the External ID->
<urn:externalIDFieldName urn:fieldName="WSO2"><b>External_Id__c</b></urn:externalIDFieldName>
<urn:sObjects xsi:type="Account"> <!-Zero or more repetitions:->
<b><!-Existing Id, this record will be updated-></b>
<External_Id_c><b>ars1</b></External_Id_c>
<Name><b>Acme Rocket Superstore</b></Name>
<b><!-You may enter ANY elements at this point-></b>
<NumberOfEmployees><b>340</b></NumberOfEmployees>
</urn:sObjects>
</urn:upsert>
</soapenv:Body>
</soapenv:Envelope>

Cannot map with attributes with namespaces

Eg:
urn:fieldName="WSO2"






[ESBJAVA-4598] Dynamic Endpoint Timeout value takes negative integers Created: 05/May/16  Updated: 05/May/16

Status: Open
Project: WSO2 ESB
Component/s: Endpoints Management
Affects Version/s: 5.0.0 - Alpha
Fix Version/s: None

Type: Bug Priority: High
Reporter: Chathurika De Silva Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS:Ubuntu 14.04
JDK: 1.8.0


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

Used the following sequence

<?xml version="1.0" encoding="UTF-8"?>
<sequence name="dyn_seq_2" xmlns="http://ws.apache.org/ns/synapse">
    <property expression="$url:a" name="timeout" scope="default"
        type="INTEGER" xmlns:ns="http://org.apache.synapse/xsd"/>
    <send>
        <endpoint>
            <address uri="http://10.100.5.63:8080/erandi">
                <timeout>
                    <duration>{get-property('timeout')}</duration>
                    <responseAction>discard</responseAction>
                </timeout>
            </address>
        </endpoint>
    </send>
</sequence>

Used the above sequence in following API

<api xmlns="http://ws.apache.org/ns/synapse" name="TestAPI" context="/testapi">
   <resource methods="POST GET" inSequence="dyn_seq_2"/>
</api>

Sent the following request to ESB with query parameters (testing purposes)
http://10.100.5.63:8280/testapi?a=-5000

The negative integer was taken without an issue and following log was observed

[2016-05-05 14:05:59,055] DEBUG - wire >> "GET /testapi?a=-5000 HTTP/1.1[\r][\n]"
[2016-05-05 14:05:59,056] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
[2016-05-05 14:05:59,056] DEBUG - wire >> "Host: 10.100.5.63:8280[\r][\n]"
[2016-05-05 14:05:59,056] DEBUG - wire >> "User-Agent: Apache-HttpClient/4.2.6 (java 1.5)[\r][\n]"
[2016-05-05 14:05:59,056] DEBUG - wire >> "[\r][\n]"
[2016-05-05 14:05:59,056] DEBUG - headers http-incoming-39 >> GET /testapi?a=-5000 HTTP/1.1
[2016-05-05 14:05:59,056] DEBUG - headers http-incoming-39 >> Connection: keep-alive
[2016-05-05 14:05:59,056] DEBUG - headers http-incoming-39 >> Host: 10.100.5.63:8280
[2016-05-05 14:05:59,056] DEBUG - headers http-incoming-39 >> User-Agent: Apache-HttpClient/4.2.6 (java 1.5)
[2016-05-05 14:05:59,059] DEBUG - headers http-outgoing-15 >> GET /erandi?a=-5000 HTTP/1.1
[2016-05-05 14:05:59,059] DEBUG - headers http-outgoing-15 >> Host: 10.100.5.63:8080
[2016-05-05 14:05:59,059] DEBUG - headers http-outgoing-15 >> Connection: Keep-Alive
[2016-05-05 14:05:59,059] DEBUG - headers http-outgoing-15 >> User-Agent: Synapse-PT-HttpComponents-NIO
[2016-05-05 14:05:59,059] DEBUG - wire << "GET /erandi?a=-5000 HTTP/1.1[\r][\n]"
[2016-05-05 14:05:59,059] DEBUG - wire << "Host: 10.100.5.63:8080[\r][\n]"
[2016-05-05 14:05:59,059] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-05-05 14:05:59,059] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-05-05 14:05:59,059] DEBUG - wire << "[\r][\n]"
[2016-05-05 14:06:12,258]  WARN - TimeoutHandler Expiring message ID : urn:uuid:eebbbc64-63da-4eef-a70a-a03713f78bdb; dropping message after timeout of : -5 seconds
[2016-05-05 14:07:59,062] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2016-05-05 14:07:59,062] DEBUG - wire >> "Content-Type: application/xml[\r][\n]"
[2016-05-05 14:07:59,062] DEBUG - wire >> "Content-Length: 4[\r][\n]"
[2016-05-05 14:07:59,062] DEBUG - wire >> "Server: Jetty(6.1.26)[\r][\n]"
[2016-05-05 14:07:59,062] DEBUG - wire >> "[\r][\n]"
[2016-05-05 14:07:59,062] DEBUG - wire >> "test"
[2016-05-05 14:07:59,062] DEBUG - headers http-outgoing-15 << HTTP/1.1 200 OK
[2016-05-05 14:07:59,062] DEBUG - headers http-outgoing-15 << Content-Type: application/xml
[2016-05-05 14:07:59,062] DEBUG - headers http-outgoing-15 << Content-Length: 4
[2016-05-05 14:07:59,062] DEBUG - headers http-outgoing-15 << Server: Jetty(6.1.26)
[2016-05-05 14:07:59,063]  WARN - SynapseCallbackReceiver Synapse received a response for the request with message Id : urn:uuid:eebbbc64-63da-4eef-a70a-a03713f78bdb But a callback is not registered (anymore) to process this response
[2016-05-05 14:08:59,229]  WARN - SourceHandler Connection time out after request is read: http-incoming-39







[ESBJAVA-4597] Call mediator inside fault sequence does not work when getting invoked after a "javax.net.ssl.SSLException" Created: 05/May/16  Updated: 05/May/16

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

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

Attachments: XML File myFaultSequence.xml     XML File testProxy.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

This happened only for "javax.net.ssl.SSLException". It works well when there is a different error. The fault sequence is getting executed, but the call mediator is not working. This is working with send mediator.

Please see the sample configurations attached.






[ESBJAVA-4596] [Mediation Debugger] Json payloads should be shown as JSON message Created: 05/May/16  Updated: 05/May/16  Resolved: 05/May/16

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

Type: Improvement Priority: Normal
Reporter: Nuwan Pallewela Assignee: Nuwan Pallewela
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   

Create proxy to handle JSON payload and debug the mediation sequence.
When mediation flow suspended at a breakpoint envelope should be shown as a JSON message.



 Comments   
Comment by Nuwan Pallewela [ 05/May/16 ]

This issue is fixed with following commit
81ea142166d43a5210918c7c70d30ca9d3902791





[ESBJAVA-4595] Error when restart esb with deactivated proxy which published to CG Created: 05/May/16  Updated: 05/May/16

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

Type: Bug Priority: Normal
Reporter: Nadeeshaan Gunasinghe 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   

When there is a deactivated proxy which is already published to CG, ESB throws following Error,

[2016-04-07 17:16:47,049] ERROR - CGAgentAdminService Could not un-publish the service 'StockQuoteProxy'
org.apache.axis2.AxisFault: The system is attempting to access an inactive service: StockQuoteProxy
at org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:1048)
at org.wso2.carbon.cloud.gateway.agent.service.CGAgentAdminService.unPublishService(CGAgentAdminService.java:146)
at org.wso2.carbon.cloud.gateway.agent.internal.CGAgentServiceComponent$ServiceRePublishingTask.run(CGAgentServiceComponent.java:186)
at java.lang.Thread.run(Thread.java:722)
[2016-04-07 17:16:47,052] ERROR - CGAgentServiceComponent Error while re-publishing the previously published service 'StockQuoteProxy', you will need to re-publish the service manually!
org.wso2.carbon.cloud.gateway.common.CGException: Could not un-publish the service 'StockQuoteProxy'
at org.wso2.carbon.cloud.gateway.agent.service.CGAgentAdminService.handleException(CGAgentAdminService.java:610)
at org.wso2.carbon.cloud.gateway.agent.service.CGAgentAdminService.unPublishService(CGAgentAdminService.java:171)
at org.wso2.carbon.cloud.gateway.agent.internal.CGAgentServiceComponent$ServiceRePublishingTask.run(CGAgentServiceComponent.java:186)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.apache.axis2.AxisFault: The system is attempting to access an inactive service: StockQuoteProxy
at org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:1048)
at org.wso2.carbon.cloud.gateway.agent.service.CGAgentAdminService.unPublishService(CGAgentAdminService.java:146)
... 2 more






[ESBJAVA-4594] [Mediation Debugger] Operation and axis2client scope property set/clear operation doest not work properly Created: 05/May/16  Updated: 05/May/16  Resolved: 05/May/16

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

Type: Bug Priority: High
Reporter: Nuwan Pallewela Assignee: Nuwan Pallewela
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   

Preconditions:
1) ESB debug mediation should be started. (Followed: https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/ )

Steps to reproduce:
1) Added four debugging points
2) When hit the first payload mediator debug point, added Operation/Axis2Client Scope Property and resume.
3) Clear above added properties.

Expected Result:

Added properties should appear and then should be removed



 Comments   
Comment by Nuwan Pallewela [ 05/May/16 ]

This issue is fixed with following commit
b0488d9da796c5e7175a8c911d9dcfb75822a9ab





[ESBJAVA-4593] [WSO2 ESB Mediation Debugger] Can't add or change axis2 scope property values Created: 04/May/16  Updated: 05/May/16  Resolved: 05/May/16

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

Type: Bug Priority: High
Reporter: Nuwan Pallewela Assignee: Nuwan Pallewela
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   

Preconditions:
1) ESB debug mediation should be started. (Followed: https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/ )

Steps to reproduce:
1) Added four debugging points (Payload factory mediators and send mediators)
2) When hit the first payload mediator debug point, Change the value of Axis2-Scope property and add new property
3) Click on "Resume"

Expected Result:
Value of Axis2-Scope property should be updated with new value.

Actual Result:
Axis2-Scope property does not change/update with new value.



 Comments   
Comment by Nuwan Pallewela [ 05/May/16 ]

This issue is fixed with following commit
38b2df6b8977c3f1ddfd5c7e646726b5a2411c90





[ESBJAVA-4592] Refer External javascript libraries from the main js file referred to by the ScriptMediator Created: 04/May/16  Updated: 04/May/16

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

Type: Improvement Priority: Normal
Reporter: Shabir Mohamed 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   

The current implementation of the ScriptMediator allows for a script to be loaded from a file uploaded externally. However, it is not possible to refer functions or libraries external to this main file indicated in the mediator.

Only code that is within the file referred to by the Mediator is executed and this file cannot refer to functions from external js libraries found in the same location as this file.

There exists a JIRA relevant to this improvement, but its outcome is not evident:
https://wso2.org/jira/browse/ESBJAVA-254






[ESBJAVA-4591] [WSO2 ESB Mediation Debugger][Clear Property] Clearing value of property give an error Created: 04/May/16  Updated: 04/May/16  Resolved: 04/May/16

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

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

Severity: Major
Estimated Complexity: Moderate

 Description   

Preconditions:
1) ESB debug mediation should be started. (Followed: https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/ )

Steps to reproduce:
1) Added four debugging points (Payload factory mediators and send mediators)
2) When hit the first payload mediator debug point, tried to clear one of synapse property.

Expected Result:

Synapse property value should be cleared.

Actual Result:

Error will be pop up and value will remain as before.

[2016-04-12 15:41:00,905] ERROR - SynapseDebugManager Failed to set or remove property in the scope synapse
org.codehaus.jettison.json.JSONException: JSONObject["property-value"] not found.
at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:387)
at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:514)
at org.apache.synapse.debug.SynapseDebugManager.addMediationFlowPointProperty(SynapseDebugManager.java:837)
at org.apache.synapse.debug.SynapseDebugManager.processDebugCommand(SynapseDebugManager.java:302)
at org.apache.synapse.debug.SynapseDebugTCPListener.run(SynapseDebugTCPListener.java:57)
[2016-04-12 15:41:00,906] ERROR - SynapseDebugManager Failed to set or remove property in the scope synapse
org.codehaus.jettison.json.JSONException: JSONObject["property-value"] not found.
at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:387)
at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:514)
at org.apache.synapse.debug.SynapseDebugManager.addMediationFlowPointProperty(SynapseDebugManager.java:837)
at org.apache.synapse.debug.SynapseDebugManager.processDebugCommand(SynapseDebugManager.java:302)
at org.apache.synapse.debug.SynapseDebugTCPListener.run(SynapseDebugTCPListener.java:57)

Note: Added new property within the mediation and tried to clear value of that particular property. It was also failed with the same error.



 Comments   
Comment by Nuwan Pallewela [ 04/May/16 ]

This issue is fixed with following commit
0ecbffb4cbcd47d02ad442be11eb746e71bd42d6





[ESBJAVA-4590] Script Mediator does not support concurrent execution and is using ScripEngine.eval() which does not guarantee state isolation between script executions. Created: 04/May/16  Updated: 04/May/16  Resolved: 04/May/16

Status: Resolved
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 4.8.1, 4.9.0
Fix Version/s: 5.0.0, 5.0.0-Beta

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

Regression from ESBJAVA-3616 causes script executions to happen sequentially. There is another issue with the script mediator where ScriptEngine.eval() method may be called from different threads while script execution is in progress leading to error [1] intermittently. This seems to be because ScriptEngine.eval() can't guarantee state isolation between executions based on https://docs.oracle.com/javase/7/docs/api/javax/script/ScriptEngine.html#eval(java.lang.String,%20javax.script.ScriptContext).

[1] TID: [0] [ESB] [2016-05-02 14:25:40,141] ERROR

{org.apache.synapse.mediators.bsf.ScriptMediator} - The script engine returned an error executing the external js script : Value {name ='null', keyValue ='conf:/repository/esb/transform.js'} function transform {org.apache.synapse.mediators.bsf.ScriptMediator}

com.sun.phobos.script.util.ExtendedScriptException: org.mozilla.javascript.EcmaError: TypeError: Cannot read property "name" from undefined (<Unknown source>#8) in <Unknown source> at line number 8



 Comments   
Comment by Ravi Undupitiya [ 04/May/16 ]

Fixed with https://github.com/wso2/wso2-synapse/pull/524 and https://github.com/wso2/product-esb/pull/512





[ESBJAVA-4589] Incoperate thread pool to Kafka Inbound Created: 03/May/16  Updated: 03/May/16

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

Type: Improvement Priority: High
Reporter: viraj senevirathne 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

 Description   

Introducing thread pool for Kafka Inbound. Currently, Kafka inbound only uses one stream when it provided List of streams to consume from [1]. But in this Kafka page [2] it has thread pool implementation for Kafka to read from multiple streams it passes on the list. In my opinion, if we use thread pool like this we can give users to fine tune Kafka inbound as they want. It says that "The first thing to know about using a High Level Consumer is that it can (and should!) be a multi-threaded application.".

[1] https://github.com/wso2/carbon-mediation/blob/8f66d42c1a0fed945fc8fc6046e7ecb86a5a5366/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint/src/main/java/org/wso2/carbon/inbound/endpoint/protocol/kafka/KAFKAMessageListener.java#L145

[2] https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Group+Example



 Comments   
Comment by viraj senevirathne [ 03/May/16 ]

Related to https://wso2.org/jira/browse/ESBJAVA-4520





[ESBJAVA-4588] [DataMapper Mediator] NPE when JSON payload with null values, transform to XML Created: 03/May/16  Updated: 03/May/16

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

Type: Bug Priority: High
Reporter: Chaminda Jayawardena Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

JDK1.8, Ubuntu 14.04, Standalone pack


Attachments: File ESBTestCapp_1.0.0.car    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Getting [1] when I try to transform following JSON to XML using DataMapper mediator. JSON input schema which has null values is in [2] and XML type output schema is in [3] and relevant CAPP attached.

[1]

[2016-05-03 10:34:55,021] ERROR - SequenceMediator Runtime error occurred while mediating the message
java.lang.NullPointerException
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.JSONReader.getFieldType(JSONReader.java:247)
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.JSONReader.primitive(JSONReader.java:220)
	at org.json.simple.parser.JSONParser.parse(JSONParser.java:471)
	at org.json.simple.parser.JSONParser.parse(JSONParser.java:312)
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.JSONReader.read(JSONReader.java:78)
	at org.wso2.carbon.mediator.datamapper.engine.input.InputModelBuilder.buildInputModel(InputModelBuilder.java:52)
	at org.wso2.carbon.mediator.datamapper.engine.core.mapper.MappingHandler.doMap(MappingHandler.java:59)
	at org.wso2.carbon.mediator.datamapper.DataMapperMediator.transform(DataMapperMediator.java:244)
	at org.wso2.carbon.mediator.datamapper.DataMapperMediator.mediate(DataMapperMediator.java:209)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:83)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:160)
	at org.apache.synapse.rest.Resource.process(Resource.java:320)
	at org.apache.synapse.rest.API.process(API.java:378)
	at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:120)
	at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:100)
	at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:68)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
	at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:82)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

[2]

{"menu": {
    "header": "SVG Viewer",
    "items": [
        {"id": "Open"},
        {"id": "OpenNew", "label": "Open New"},
        null,
        {"id": "ZoomIn", "label": "Zoom In"},
        {"id": "ZoomOut", "label": "Zoom Out"},
        {"id": "OriginalView", "label": "Original View"},
        null,
        {"id": "Quality"},
        {"id": "Pause"},
        {"id": "Mute"},
        null,
        {"id": "Find", "label": "Find..."},
        {"id": "FindAgain", "label": "Find Again"},
        {"id": "Copy"},
        {"id": "CopyAgain", "label": "Copy Again"},
        {"id": "CopySVG", "label": "Copy SVG"},
        {"id": "ViewSVG", "label": "View SVG"},
        {"id": "ViewSource", "label": "View Source"},
        {"id": "SaveAs", "label": "Save As"},
        null,
        {"id": "Help"},
        {"id": "About", "label": "About Adobe CVG Viewer..."}
    ]
}}

[3]

<menu>
    <header>Adobe SVG Viewer</header>
    <item action="Open" id="Open">Open</item>
    <item action="OpenNew" id="OpenNew">Open New</item>
    <separator/>
    <item action="ZoomIn" id="ZoomIn">Zoom In</item>
    <item action="ZoomOut" id="ZoomOut">Zoom Out</item>
    <item action="OriginalView" id="OriginalView">Original View</item>
    <separator/>
    <item action="Quality" id="Quality">Quality</item>
    <item action="Pause" id="Pause">Pause</item>
    <item action="Mute" id="Mute">Mute</item>
    <separator/>
    <item action="Find" id="Find">Find...</item>
    <item action="FindAgain" id="FindAgain">Find Again</item>
    <item action="Copy" id="Copy">Copy</item>
    <item action="CopyAgain" id="CopyAgain">Copy Again</item>
    <item action="CopySVG" id="CopySVG">Copy SVG</item>
    <item action="ViewSVG" id="ViewSVG">View SVG</item>
    <item action="ViewSource" id="ViewSource">View Source</item>
    <item action="SaveAs" id="SaveAs">Save As</item>
    <separator/>
    <item action="Help" id="Help">Help</item>
    <item action="About" id="About">About Adobe CVG Viewer...</item>
</menu>





[ESBJAVA-4587] [DataMapper Mediator] JSON to XML transform fails in some cases. Created: 02/May/16  Updated: 02/May/16

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

Type: Bug Priority: High
Reporter: Chaminda Jayawardena Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 14.04, jdk1.8.0_05, Standalone pack


Attachments: File ESBTestCapp_1.0.0.car    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

I am getting [1] when I try to transform json[2] to xml[3] using DataMapper mediator. Also attached the relevant CAR application here.

[1]

 [2016-05-02 17:13:13,007] ERROR - DataMapperMediator DataMapper mediator : mapping failed
Error while parsing JSON input stream. Error occurred while sending termination event. Script engine unable to execute the script javax.script.ScriptException: TypeError: Cannot read property "menuitem" from undefined in <eval> at line number 1
	at org.wso2.carbon.mediator.datamapper.engine.input.readers.JSONReader.read(JSONReader.java:82)
	at org.wso2.carbon.mediator.datamapper.engine.input.InputModelBuilder.buildInputModel(InputModelBuilder.java:52)
	at org.wso2.carbon.mediator.datamapper.engine.core.mapper.MappingHandler.doMap(MappingHandler.java:59)
	at org.wso2.carbon.mediator.datamapper.DataMapperMediator.transform(DataMapperMediator.java:244)
	at org.wso2.carbon.mediator.datamapper.DataMapperMediator.mediate(DataMapperMediator.java:209)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:83)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:160)
	at org.apache.synapse.rest.Resource.process(Resource.java:320)
	at org.apache.synapse.rest.API.process(API.java:378)
	at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:120)
	at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:100)
	at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:68)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
	at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:82)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

[2]

{"menu": {
  "id": "file",
  "value": "File",
  "popup": {
    "menuitem": [
      {"value": "New", "onclick": "CreateNewDoc"},
      {"value": "Open", "onclick": "OpenDoc"},
      {"value": "Close", "onclick": "CloseDoc"}
    ]
  }
}}

[3]

<menu id="file" value="File">
  <popup>
    <menuitem value="New" onclick="CreateNewDoc" />
    <menuitem value="Open" onclick="OpenDoc" />
    <menuitem value="Close" onclick="CloseDoc" />
  </popup>
</menu>





[ESBJAVA-4586] Method "getPayloadJSON()" called on the "mc" object inside the ScriptMediator returns null. Created: 02/May/16  Updated: 02/May/16

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

Type: Bug Priority: Normal
Reporter: Shabir Mohamed 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   

Method "getPayloadJSON()" called on the "mc" object inside the ScriptMediator returns null.

This works fine in the synapse-core version 2.1.4-wso2v1 but the issue exists in the version 2.1.5-wso2v2.

ERROR - ScriptMessageContext JSON object is null.






[ESBJAVA-4585] After completing load test "java.lang.OutOfMemoryError: GC overhead limit exceeded" error occours Created: 02/May/16  Updated: 02/May/16

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

Type: Bug Priority: Normal
Reporter: Buddhima Wijeweera Assignee: Gihan Anuruddha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB Analytics ALPHA2


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

 Description   

After complete sending messages in load test, Out Of Memory error seen in the node which contains Analytic Server.
In this case Analytic Server is placed in a separate node with My SQL database mounted.

Test details : Jmeter sending 1 million requests, with 100 threads concurrently.

java.lang.OutOfMemoryError: GC overhead limit exceeded
	at java.util.Arrays.copyOfRange(Arrays.java:2694)
	at java.lang.String.<init>(String.java:203)
	at java.lang.StringBuffer.toString(StringBuffer.java:561)
	at org.json.JSONObject.toString(JSONObject.java:1320)
	at org.json.JSONObject.valueToString(JSONObject.java:1443)
	at org.json.JSONArray.join(JSONArray.java:387)
	at org.json.JSONArray.toString(JSONArray.java:832)
	at org.wso2.carbon.analytics.esb.util.CompressedEventProcessorUtils.getFieldValues(CompressedEventProcessorUtils.java:112)
	at org.wso2.carbon.analytics.esb.siddhi.extension.CompressedEventProcessor.process(CompressedEventProcessor.java:83)
	at org.wso2.siddhi.core.query.processor.stream.StreamProcessor.processEventChunk(StreamProcessor.java:36)
	at org.wso2.siddhi.core.query.processor.stream.AbstractStreamProcessor.process(AbstractStreamProcessor.java:97)
	at org.wso2.siddhi.core.query.input.ProcessStreamReceiver.processAndClear(ProcessStreamReceiver.java:111)
	at org.wso2.siddhi.core.query.input.ProcessStreamReceiver.process(ProcessStreamReceiver.java:69)
	at org.wso2.siddhi.core.query.input.ProcessStreamReceiver.receive(ProcessStreamReceiver.java:88)
	at org.wso2.siddhi.core.stream.StreamJunction.sendEvent(StreamJunction.java:165)
	at org.wso2.siddhi.core.stream.StreamJunction.access$000(StreamJunction.java:45)
	at org.wso2.siddhi.core.stream.StreamJunction$Publisher.send(StreamJunction.java:336)
	at org.wso2.siddhi.core.stream.input.InputDistributor.send(InputDistributor.java:39)
	at org.wso2.siddhi.core.stream.input.SingleThreadEntryValve.send(SingleThreadEntryValve.java:59)
	at org.wso2.siddhi.core.stream.input.SingleStreamEntryValve$SingleEntryValveHandler.sendEvents(SingleStreamEntryValve.java:163)
	at org.wso2.siddhi.core.stream.input.SingleStreamEntryValve$SingleEntryValveHandler.onEvent(SingleStreamEntryValve.java:145)
	at org.wso2.siddhi.core.stream.input.SingleStreamEntryValve$SingleEntryValveHandler.onEvent(SingleStreamEntryValve.java:121)
	at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[2016-05-02 16:17:20,815] ERROR {org.wso2.siddhi.core.config.SiddhiContext} -  Disruptor encountered an error processing [sequence: 44582, event: IndexedEvent{streamIndex=0, event=Event{timestamp=1462183346599, data=[true, urn_uuid_99c7bbcc-83a0-425f-ad09-8cea543b6f8d, H4sIAAAAAAAAAO2aW2/aMBSA/8qUZ6jsOFc/FVGqIrUda9G0qaqQSQxECnbmOF1R1f8+h9ILkLRkG7mwSbzYPseX88U+Pgc/aDMeSw1rEBxBAI7MI6hj17ZMraXRO8pkrOGbB83j84gzVRwuIqqkB4LfLz5dU3EXeFSJvrRfknnafq6qWUxXAkvpt1J9P1vmGOBszVgSIYdB2jc0LB06CBkA6khNkvmb9cg0W5qfCCIDzjSsI72ljemECzogi5ATNThLwrClkYmkYqPO40zSe6kGjqiQiwsSPbdIQVgccZHV5s2C0BdUjXYDb9NJSbEY8IDJXFu8ipyReOZxP12CbkDoWKat1jUhSSi7PEm7AC1tpoS6G0KPrW0w1/RHQlkmk8HV52/fR/3L696XnVhAvK7RIAZ6pQwuqB8QyUUWg+dpr0Tw195Zv3veG/VPdmKi4/d7KMRoWf/KCJRJCDWGUPeqd9Ifjrqdq90QoW1E6100hpFRV0bdUJWy2nOhGHhTpxgFBN5SsMukYLbsunqUDuNsMedJnCXTfzFBjqmNXUxtlWlqq64f/Gqhp8RT7YtCX76Jc5WLcUnrKzqIIPi/A8qxtHOAO8A9gB3g1pXLGSU+FS83nY63NM5O4QXAecqNwQKrDfb2wsU6ACy1jf+6JAwLHV4Q4g2dxvgSWN/4oSgFu7kQqg20e8yPluNuQ+izWJlEXZlWM+lFWyi2RY4BztRrDo/9xxhKArqWCwry6M2DOFYGGdJY5iPJlFJU8rSbA8bcNxjbNnUEDGAUPK0606mgUyKLZTwgwlmK2TxSu3/Mo1wfXm3Wo6Y84Fse8B/isa8YPMfS6rf29wUs99s/xDAcGkXj8DqeSocYiJsFI74actGrzRD+1YjP2i3YqOXJpVebEHnners+j4yb7abA1luEd+6z9WSx7yxIW8UayHVd27JKdCNOQTeyhJAJp7rLlF7bv7//wI24xdzI0v4fcyl3yxxOykoHO7mRXArmWvoWolIx7D0W/10volY6V6V8L7IpoLxIhk6DUOw7X9W2oI0sy4ROwR1xRdX0mV9sU+h4Wy0bRvp+7eN3bWWeTk/lkraFoj6ncUym9DTkP5cGTQQbJUngj1zXs8djz2s7iIC2oZuTNvGB23Y8SkwDja2J46tpRE/LTx+Q3j7+AuD65E5oKgAA], isExpired=false}}]
java.lang.OutOfMemoryError: GC overhead limit exceeded
[2016-05-02 16:17:32,652] ERROR {org.wso2.carbon.analytics.dataservice.core.indexing.AnalyticsDataIndexer} -  Error in processing index batch operations: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded






[ESBJAVA-4584] Support High availability for MailTo Transport listen proxies Created: 02/May/16  Updated: 02/May/16

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

Type: Improvement Priority: Normal
Reporter: Madhawa Gunasekara 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




[ESBJAVA-4583] [Script Mediator] When there are multiple script mediators saved in registry used within a proxy service, responses are getting mixed up Created: 02/May/16  Updated: 04/May/16

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

Type: Bug Priority: High
Reporter: Pubudu D.P Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

JDK:- 1.7.0_79
ESB:- Standalone 4.8.1


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

 Description   

Pre-Conditions:-

  • A WSDL endpoint should exist

1. Create a proxy service in WSO2 ESB to call WSDL endpoint
2. Within the proxy service use script mediators saved in registry to validate some values in request body (use more than one script mediator)
3. Send concurrent requests using SOAP UI to the proxy service
4. Observe the results

Expected Results:-

  • Each request should receive the associated result

Actual Results:-

  • Some requests receive results belong to some other requests

eg:-
Sent requests R1, R2, R3
Received responses r1,r2,r3

Displayed in SOAPUI (Incorrect behavior):-
R1-r2
R2-r1
R3-r3

Note:-
Further investigations have revealed that this behavior can be avoided by moving script mediators saved in the registry as inline script mediators. But there is an issue when users are required to re-use these mediators. It is not convenient to always use script mediator in In-Line mode.



 Comments   
Comment by Pubudu D.P [ 02/May/16 ]

Please contact me if you require any further information on this issue.

Cheers,
Pubudu.

Comment by Pubudu D.P [ 04/May/16 ]

Related Issue : ESBJAVA-4590





[ESBJAVA-4582] Null Pointer Exception While running the Salesforce Integration test Created: 02/May/16  Updated: 02/May/16  Resolved: 02/May/16

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

Type: Bug Priority: Highest
Reporter: Hariprasath Thanarajah Assignee: Hariprasath Thanarajah
Resolution: Not a bug 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   

Currently ESB 5.0.0 Alpha released with wso2-axis2-1.6.1.wso2v12, But there is a fix for wso2-axis2-v1.6.1-wso2v17 in https://github.com/wso2/wso2-axis2/blob/v1.6.1-wso2v17/modules/transport/http/src/org/apache/axis2/transport/http/AbstractHTTPSender.java

We need to get it fix in ESB 5.0.0 release.



 Comments   
Comment by Chanaka Fernando [ 02/May/16 ]

What is the pack you are testing? WSO2 ESB 5.0.0 Alpha is released with the correct axis2 version (161wso2v17). Please double check.





[ESBJAVA-4581] ESB Mediation Debug points inside clone mediator does not get hit Created: 02/May/16  Updated: 03/May/16

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

Type: Bug Priority: Highest
Reporter: Nuwan Pallewela Assignee: Kevin Ratnasekera
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File cloneaggregatorconfig.png    
Severity: Blocker
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Create a proxy service as shown in the attachment which includes a clone mediator.
When debugging the created proxy esb server will not suspend at the log mediator inside the clone mediator though it is marked as a breakpoint.






[ESBJAVA-4580] xsi:type support in datamapper engine side Created: 01/May/16  Updated: 03/May/16  Resolved: 03/May/16

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

Type: Improvement Priority: High
Reporter: Viraj Rajaguru Assignee: Viraj Rajaguru
Resolution: Fixed 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

 Comments   
Comment by Viraj Rajaguru [ 03/May/16 ]

Fixed in 5ce52d873357a5f4831aae56842bc3eb7a0040b2 and e5dc9aaab47dc801b59de2cfec23987fc69b6237 in https://github.com/wso2/carbon-mediation





[ESBJAVA-4579] Cannot update Inbound Endpoint definitions deployed via a CApp which contains registry resource references Created: 29/Apr/16  Updated: 29/Apr/16

Status: Open
Project: WSO2 ESB
Component/s: Carbon Applications, Inbound Endpoints
Affects Version/s: 4.9.0
Fix Version/s: None

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

Issue Links:
Reference
relates to ESBJAVA-3682 Support Dynamic parameters for inboun... Resolved
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

1. Create a CApp which contains a File Inbound Endpoint
2. Create a registry resource to point a file endpoint for the parameter: transport.vfs.FileURI

For eg:

<parameter name="transport.vfs.FileURI" key="gov:/endpoints/fileuri" />

3. Deploy the CApp

4. Login to Carbon console and navigate to "Inbound Endpoints" -> Edit

5. Update the "Suspend" parameter and click on update button

Following error is thrown;

[2016-04-29 13:48:47,531] WARN - SynapseXMLConfigurationFactory Inbound Endpoint configuration cannot be built - Continue in fail-safe mode
org.apache.synapse.SynapseException: Error while deploying inbound endpoint FileInbound.Registry entry defined with key: $registry:gov:/endpoints/fileuri not found.

This seems to be a regression of [1]

[1] https://wso2.org/jira/browse/ESBJAVA-3682



 Comments   
Comment by Akila Perera [ 29/Apr/16 ]

Fixed in PR: https://github.com/wso2/carbon-mediation/pull/580





Generated at Fri May 06 09:06:24 IST 2016 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.