[ESBJAVA-3536] BAM Server profile option is not available on ESB490 M5 Pack for tenants Created: 10/Feb/15  Updated: 26/Apr/15  Resolved: 26/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: Administration Console
Affects Version/s: 4.9.0
Fix Version/s: 4.9.0 - Alpha

Type: Bug Priority: Highest
Reporter: Shavantha Weerasinghe Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Centos 6.5
Java Version/Java VM : IBM JDK 1.7.0
Packs : wso2esb-490 m5
DBMS: Orale
Browser : Firefox 27.0
Set up : Nginx fronted clusters with 2 worker nodes


Attachments: PNG File 481.png     PNG File 490.png    
Severity: Blocker
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

BAM Server profile option is not available on ESB490 M5 Pack for tenants

steps
1.as a tenant attempt to create a BAM server profile configuration in 490 M5 pack.

Note: for 481 the option is shown as per the attached screenshots



 Comments   
Comment by Shavantha Weerasinghe [ 10/Feb/15 ]

Other options missing are

1.Cloud gateway agent
2.Mediation data publisher

Comment by Malaka Silva [ 26/Apr/15 ]

https://github.com/wso2/carbon-mediation/commit/29a135ce0c30ab0497600ea2e3bc70c5404c6ba1





[ESBJAVA-3117] The bind-address feature was not implemented for Pass-through transport Created: 07/Feb/14  Updated: 25/Apr/15  Resolved: 25/Apr/15

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

Type: Bug Priority: Highest
Reporter: Marc Kelderman Assignee: Priyadarssini Kishokumar
Resolution: Fixed Votes: 1
Labels: passthru-transport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Issue was found on Suse

Linux l2-wsofonapp02 3.0.93-0.5-default #1 SMP Tue Aug 27 08:17:02 UTC 2013 (925d406) x86_64 x86_64 x86_64 GNU/Linux


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

 Description   

On a server that listen on multiple IP address, you are not able to bind it to a single IP address. It always listen to 0.0.0.0/<port>. This means all app addresses. In the file $WSO2_API_HOME//repository/conf/axis2/axis2.xml you can set de bind address, but it is not working, for example:

<transportReceiver name="http" class="org.apache.synapse.transport.passthru.PassThroughHttpListener">
<parameter name="bind-address" locked="false">172.29.4.97</parameter>
<parameter name="WSDLEPRPrefix" locked="false">http://hpx-nxt-fon-app.nl.rsg</parameter>
<parameter name="port" locked="false">8280</parameter>
<parameter name="non-blocking" locked="false">true</parameter>
<parameter name="httpGetProcessor" locked="false">org.wso2.carbon.transport.nhttp.api.PassThroughNHttpGetProcessor</parameter>
</transportReceiver>



 Comments   
Comment by Marc Kelderman [ 07/Feb/14 ]

Based on question from http://stackoverflow.com/questions/21601792/wso2-api-manager-how-to-listen-passthroughhttplistener-on-single-ip-address?noredirect=1#comment32665537_21601792

Comment by shafreen anfar [ 27/Mar/15 ]

Please find the pull request for this issue.

https://github.com/wso2/wso2-synapse/pull/114

Comment by shafreen anfar [ 25/Apr/15 ]

Pull request has been merged.





[ESBJAVA-3545] NPE thrown when processing vfs file transfer using inbound endpoints Created: 11/Feb/15  Updated: 24/Apr/15  Resolved: 24/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: Inbound Endpoints
Affects Version/s: 4.9.0
Fix Version/s: 4.9.0 - M8

Type: Bug Priority: High
Reporter: Shavantha Weerasinghe Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux
Java Version/Java VM : JDK1.6.0_37
Packs : wso2besb-490
DBMS: h2
Browser : Firefox 27.0
Set up :Stand alone fresh pack


Attachments: XML File fileProcess.xml    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

NPE thrown when processing vfs file transfer using inbound endpoints

preconditions
1. three folders named in, ot and failure should be created
steps
1.deploy the attached config
2.add a file to the path of the in folder

Below log is printed
[2015-02-11 17:17:16,267] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:16,269] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:16,269] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:16,270] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:16,270] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:16,271] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:16,271] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:16,272] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:16,272] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:18,268] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:18,268] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:18,269] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:18,269] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:18,270] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:18,270] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:18,272] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:18,272] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:18,273] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:18,273] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:19,267] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:19,268] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:19,269] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:19,269] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:19,270] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:19,270] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:19,272] ERROR - FileInjectHandler Error while processing the file/folder
[2015-02-11 17:17:19,272] ERROR - FileInjectHandler java.lang.NullPointerException
[2015-02-11 17:17:19,273] ERROR - FileInjectHandler Error while processing the file/folder



 Comments   
Comment by Shavantha Weerasinghe [ 12/Feb/15 ]

In this scenario the sequence named "request" does not exist

Comment by Shavantha Weerasinghe [ 12/Feb/15 ]

Ideally if the sequence mentioned in the InboundEndpoint does not exist then the InboundEndpoint should be marked as an inactive endpoint. This will help prevent

Comment by Malaka Silva [ 24/Apr/15 ]

This is fixed and currently a warning is given. Anyway if the inbound is added via UI sequence is mandatory





[ESBJAVA-3596] Script mediator does not format JSON payload correctly Created: 06/Mar/15  Updated: 24/Apr/15  Resolved: 24/Apr/15

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

Type: Bug Priority: High
Reporter: Madusanka Premaratne Assignee: Malaka Silva
Resolution: Cannot Reproduce 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 giving json payload to the script mediator it formats json object in a wrong way.
For example the following payload should return

{"success" : true}

, but it returns {"jsonObject":{"success":"true"}}

mc.setProperty('CONTENT_TYPE', 'application/json');
mc.setPayloadJSON('

{"success" : true}

');

Expected Output :

{"success" : true}

Current Output : {"jsonObject":{"success":"true"}}



 Comments   
Comment by Malaka Silva [ 24/Apr/15 ]

Tested with following and seems to be working in ESB 4.9.0 M7

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="json"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<script language="js">mc.setPayloadJSON('

{"success" : true}

');</script>
<property name="messageType"
value="application/json"
scope="axis2"
type="STRING"/>
<respond/>
</inSequence>
</target>
<description/>
</proxy>





[ESBJAVA-3623] ESB not processing some of the responses received from back end service Created: 25/Mar/15  Updated: 24/Apr/15  Resolved: 24/Apr/15

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

Type: Bug Priority: High
Reporter: Asitha Nanayakkara Assignee: Malaka Silva
Resolution: Cannot Reproduce Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 6.6
Oracle jdk 1.7.0_75
4GB RAM
2vCPU
10GB drive
Run within VirtualBox


Attachments: Zip Archive configs.zip    
Severity: Major
Estimated Complexity: Advanced
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   

Setup

There is a service in DSS fronted by an ESB proxy service . When a request is sent from ESB proxy to DSS, response is received. But on some occasions ESB timeouts, not receiving the response from DSS in time. When we check the wire logs on ESB, response is not received from DSS. When we look at the packets through Wireshark we observe that the actual response was sent from DSS in time. But in ESB transport level the response in not processed. This happens intermittently in the given environment with the attached configurations.



 Comments   
Comment by Malaka Silva [ 24/Apr/15 ]

Hi Asitha,

There can be couple of reasons for those. Network issue between ESB and DSS can cause this. It's hard to reproduce and fix this type of issues via jira. Please start a mail thread in [1]

[1] dev@wso2.org

Best Regards,
Malaka





[ESBJAVA-3624] JSON response being generated is not putting numbers in double quotes e.g. 1234 should be "1234". But it puts the numbers starting with 0 in double quotes e.g. "025". String "true" and "false" appear as true and false keywords without double quotes. Created: 27/Mar/15  Updated: 24/Apr/15  Resolved: 24/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 4.8.0
Fix Version/s: 4.9.0 - M8

Type: Bug Priority: High
Reporter: Gagandeep S Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: ESB
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day
Environment:

Windows 7


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
Affects Docs:
Yes

 Comments   
Comment by Gagandeep S [ 27/Mar/15 ]

{"profile": {
"indicator": false,
"deliveryZipDetails": {"deliveryZipDetail": [

{ "zip": 51010 }

,

{ "zip": "01234" }]}

,
"telephoneDetails": {"telephoneDetail": [

{ "type": "dayPhone", "number": 2344232342 }

,

{ "type": "eveningPhone", "number": 2222222222 }

]}
}}

Comment by Malaka Silva [ 24/Apr/15 ]

Can be done with the latest release with the following added to synapse.properties

synapse.commons.json.json.output.autoPrimitive=false





[ESBJAVA-3662] ERROR White spaces are required between publicId and systemId Created: 23/Apr/15  Updated: 24/Apr/15  Resolved: 24/Apr/15

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

Type: Bug Priority: High
Reporter: Pablo Estades Assignee: Malaka Silva
Resolution: Not a bug Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Core:
Linux DG20ESBW1 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux

Java Version:
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)

Patches Appliying:

  • 0000
  • 0001
  • 0002
  • 0003
  • 0004
  • 0005
  • 0180

Severity: Major
Estimated Complexity: Moderate

 Description   

We are working with WSO2 ESB 4.8.1 with JAVA 1.7.0_55. Always, when we start the ESB and make the first request we receive this error:

TID: [0] [ESB] [2015-04-22 10:51:31,067] ERROR {org.apache.synapse.transport.passthru.util.RelayUtils} -  Error while building Passthrough stream {org.apache.synapse.transport.passthru.util.RelayUtils}
org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62]
Message: White spaces are required between publicId and systemId.
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
                at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
                at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:129)
                at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107)
                at org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:82)
                at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:68)
                at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
                at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
                at org.apache.synapse.rest.Resource.process(Resource.java:297)
                at org.apache.synapse.rest.API.process(API.java:298)
                at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76)
                at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:50)
                at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220)
                at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488)
                at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
                at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
                at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225)
                at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
                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)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62]
Message: White spaces are required between publicId and systemId.
                at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:598)
                at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
                at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
                at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
                at org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
                ... 22 more
TID: [0] [ESB] [2015-04-22 10:51:31,073] ERROR {org.apache.synapse.mediators.base.SequenceMediator} -  Error while building message {org.apache.synapse.mediators.base.SequenceMediator}
org.apache.axis2.AxisFault: Error while building Passthrough stream
                at org.apache.synapse.transport.passthru.util.RelayUtils.handleException(RelayUtils.java:236)
                at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:111)
                at org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:82)
                at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:68)
                at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
                at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
                at org.apache.synapse.rest.Resource.process(Resource.java:297)
                at org.apache.synapse.rest.API.process(API.java:298)
                at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76)
                at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:50)
                at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220)
                at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488)
                at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
                at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
                at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225)
                at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
                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)
Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62]
Message: White spaces are required between publicId and systemId.
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
                at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
                at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:129)
                at org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107)
                ... 17 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62]
Message: White spaces are required between publicId and systemId.
                at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:598)
                at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
                at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
                at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
                at org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
                at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
                ... 22 more

After this, we make same request and all works fine...

Any suggestion in order to avoid this error?



 Comments   
Comment by Pablo Estades [ 23/Apr/15 ]

More informattion:

The request are sending to an API mediator.
Request is: POST

{"name":"John"}


Content-Type is application/json

Comment by Malaka Silva [ 24/Apr/15 ]

Hi Pablo,

Seems like this is something to do with the configuration.

Please start a mail thread in [1]. More info can be found in [2]

[1] dev@wso2.org
[2] http://wso2.com/mail/





[ESBJAVA-3356] Issue with handling erroneous messages having '&' in payload Created: 07/Oct/14  Updated: 24/Apr/15  Resolved: 24/Apr/15

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

Type: Patch Priority: Highest
Reporter: Dinesh Bandara Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

Unable to process the messages with XML having "&" character.

The entity name must immediately follow the '&' in the entity reference.
at org.apache.synapse.mediators.AbstractMediator.handleException(AbstractMediator.java:273)
at org.apache.synapse.mediators.builtin.LogMediator.getFullLogMessage(LogMediator.java:197)
at org.apache.synapse.mediators.builtin.LogMediator.getLogMessage(LogMediator.java:125)
at org.apache.synapse.mediators.builtin.LogMediator.mediate(LogMediator.java:93)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:78)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at org.apache.synapse.rest.Resource.process(Resource.java:297)
at org.apache.synapse.rest.API.process(API.java:341)
at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:76)
at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:63)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220)
at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:344)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:385)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
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)



 Comments   
Comment by Dinesh Bandara [ 07/Oct/14 ]

Please merge the PR
https://github.com/wso2-dev/wso2-synapse/pull/145

Comment by Dinesh Bandara [ 14/Oct/14 ]

This fix also applicable for the issue of unable to catch NullPointerException in validate mediator by API's fault sequence when passing an empty response body

Comment by Manula Thantriwatte [ 22/Dec/14 ]

Please ignore the above pull request. Because code is not honoring the code standards. Please find the new pull request in [1].

[1] https://github.com/wso2-dev/wso2-synapse/pull/179

Comment by Manula Thantriwatte [ 28/Jan/15 ]

Please find the new pull request for wso2 repo in [1]

[1] https://github.com/wso2/wso2-synapse/pull/62

Comment by Buddhima Wijeweera [ 12/Mar/15 ]

Hi,
Also need following change to handle this situation with long messages:
https://github.com/wso2/wso2-synapse/pull/103

Comment by Malaka Silva [ 24/Apr/15 ]

https://github.com/wso2/wso2-synapse/commit/3793ab6d61c719b0b27a219d09181670faf68a31





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

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

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

 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.

Comment by Malaka Silva [ 23/Apr/15 ]

https://github.com/wso2/wso2-synapse/commit/f30f8e39399b7c5d9d45339f19dd38a95b52c736





[ESBJAVA-1881] VFS url change in servicemetafiles when restarted ESB Created: 17/Apr/13  Updated: 23/Apr/15  Resolved: 23/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: Core Engine
Affects Version/s: 4.5.1, 4.6.0, 4.7.0, 4.8.1
Fix Version/s: 4.7.0 Beta, 4.9.0 - M8

Type: Bug Priority: Highest
Reporter: Geeth Munasinghe Assignee: Vijitha Ekanayake
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive AxiomTest.zip     File ESBJAVA-1881.diff     Text File vfsTransportListner.patch    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

1. Proxy is added to move files to FTPS server
2. Following parameter are used to set up the proxy

<parameter name="transport.vfs.ActionAfterFailure" type="1">MOVE</parameter>
<parameter name="transport.vfs.ActionAfterProcess" type="1">MOVE</parameter>
<parameter name="transport.vfs.FileURI" type="1">vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/in?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.p
rotection=P</parameter>
<parameter name="transport.vfs.MoveAfterFailure" type="1">vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/err?vfs.passive=true&amp;vfs.implicit=true
&vfs.protection=P</parameter>
<parameter name="transport.vfs.FileNamePattern" type="1">.*.xml</parameter>
<parameter name="transport.vfs.MoveAfterProcess" type="1">vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/done?vfs.passive=true&amp;vfs.implicit=tru
e&vfs.protection=P</parameter>
<parameter name="serviceType" type="1">proxy</parameter>

3. At the first restart above parameters are changed as following which makes FileURI, MoveAfterFailure and MoveAfterProcess parameters wrong in the servicemetafiles created for the proxy.

<parameter name="transport.vfs.ActionAfterFailure" type="1">MOVE</parameter>
<parameter name="transport.vfs.ActionAfterProcess" type="1">MOVE</parameter>
<parameter name="transport.vfs.FileURI" type="1">&vfs.implicit=true&vfs.protection=Pvfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/in?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.p
rotection=P</parameter>
<parameter name="transport.vfs.MoveAfterFailure" type="1">&vfs.implicit=true&vfs.protection=Pvfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/err?vfs.passive=true&amp;vfs.implicit=true
&vfs.protection=P</parameter>
<parameter name="transport.vfs.FileNamePattern" type="1">.*.xml</parameter>
<parameter name="transport.vfs.MoveAfterProcess" type="1">&vfs.implicit=true&vfs.protection=Pvfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/done?vfs.passive=true&amp;vfs.implicit=tru
e&vfs.protection=P</parameter>
<parameter name="serviceType" type="1">proxy</parameter>

4. At the next restart parameters reset as in the 2nd step
5. At the next restart parameters reset again as in 3rd step
6. This continues to happen sequentially at every restart.

When investigated further this happens when url has path separated by "/" like in vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/done.
If /esb/done is removed it does not happen.



 Comments   
Comment by Ravi Undupitiya [ 13/May/13 ]

The change in vfs URI from:
vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/in?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.protection=P

to:
&vfs.implicit=true&vfs.protection=Pvfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/in?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.protection=P

is coming from a service persistence manager inside carbon core which is responsible for updating servicemetafiles. This is causing axis2-kernel Parameter objects to return an incorrect URI and this problem is propagated to synapse.

Comment by Ravi Undupitiya [ 14/May/13 ]

Investigated and found out that this issue is coming from org.wso2.carbon.core.PersistenceUtils.getResourceDocumentElement() - which is called by org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.getAll() - could not reproduce the error by isolating the Axiom code in getResourceDocumentElement(). I have attached a maven project that isolates getResourceDocumentElement() code.

Comment by Ravi Undupitiya [ 03/Jun/13 ]

Find below the proxy service config used to reproduce the issue.

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="StockQuoteProxy1"
transports="vfs"
startOnLoad="true"
trace="disable">
<description/>
<target>
<inSequence>
<log level="full"/>
<drop/>
</inSequence>
</target>
<parameter name="transport.PollInterval">5</parameter>
<parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
<parameter name="transport.vfs.FileURI">vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/in?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.protection=P</parameter>
<parameter name="transport.vfs.MoveAfterProcess">vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/done?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.protection=P</parameter>
<parameter name="transport.vfs.MoveAfterFailure">vfs:ftps://ftpuser:wso2123@10.100.3.43:990/esb/err?vfs.passive=true&amp;vfs.implicit=true&amp;vfs.protection=P</parameter>
<parameter name="transport.vfs.FileNamePattern">.*.xml</parameter>
<parameter name="transport.vfs.ContentType">application/xml</parameter>
<parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
</proxy>

Comment by Nalin Chamara [ 03/Jun/13 ]

A patch (vfsTransportListner.patch) with a workaround to fix the issue is attached.

Comment by Ravi Undupitiya [ 03/Jun/13 ]

Workaround fix committed to r173728.

Comment by Ravi Undupitiya [ 09/Oct/14 ]

This solution breaks if we send a FileURI as follows:
'vfs:ftp://vfs:password@vfs.example.com/somepath/somefile.xml'

Comment by Vijitha Ekanayake [ 21/Apr/15 ]

This is because, when reading the transport.vfs.FileURI parameter from servicemetafile providing xpath expression, It breaks the string value by & sign and creates siblingNode with '&' and creates the rest of the string as subsequent siblings.

So as a fix following change has done in AbstractPersistenceManager[1] class, which correctly update servicemetafiles when configuration contains ampersand (&).

-                        paramElementFromMeta.setText(serviceParameter.getValue().toString());
+	                    if(paramElementFromMeta.getText().contains("&")){
+		                    paramElementFromMeta.discard();
+		                    paramElementFromMeta = serviceParameter.getParameterElement().cloneOMElement();
+	                    }else {
+		                    paramElementFromMeta.setText(serviceParameter.getValue().toString());
+	                    }

A diff (ESBJAVA-1881.diff) to fix the issue is attached.

[1].https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0010/core/org.wso2.carbon.core/4.2.0/src/main/java/org/wso2/carbon/core/persistence/AbstractPersistenceManager.java

Comment by Vijitha Ekanayake [ 23/Apr/15 ]

servicemetafiles are removed from ESB 4.9.0. hence the issue no longer persists with ESB 4.9.0 versions. For the older versions of ESB fix is already Committed to kernel patch0010 with r212219. hence resolving the issue.





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

Status: Resolved
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: Not a bug 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: No

 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.



 Comments   
Comment by Malaka Silva [ 23/Apr/15 ]

Hi Sajini,

I checked your configuration. You have set the headers incorrectly.

<property name="username"
expression="get-property('registry', 'conf:/custom/username')"
scope="default"
type="STRING"/>
<property name="password"
expression="get-property('registry', 'conf:/custom/password')"
scope="default"
type="STRING"/>
If we are setting the transport headers scope has to be "transport" not "default"

I checked with a sample configuration and it worked without a problem for me





[ESBJAVA-3478] Explicitly build OM element when assigning via property mediator Created: 31/Dec/14  Updated: 23/Apr/15  Resolved: 23/Apr/15

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

Type: Bug Priority: Highest
Reporter: dushan abeyruwan Assignee: Ishan Jayawardena
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   

We have an XML local entry which contains some business data.

In a sequence in the IN flow we read that XML local entry as an OM element via a property mediator and set the value in the operation context.

<property name="foo.xx.errorEntries" expression="get-property('CUSTOM_ERROR_CODES')" scope="operation" type="OM"/>

Then we have a clone mediator which has three branches.

In those branches a template is called based on an error scenario. In the template we access the OM element in the operation context and perform an XPath query.

<template xmlns="http://ws.apache.org/ns/synapse" name="xxCollectorTemplate_V1">
.
.
<property name="errorMessage" expression="get-property('operation','foo.common.errorEntries')//sysMsg[code=$func:argErrorCode]/message/text()" scope="default" type="STRING" description="ErrorMsgEntry"/>
.
.
</template>

When we invoke the API, time to time we get the following exception saying that the XML say syntax error. (But the XML is a valid XML)

org.apache.synapse.SynapseException: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException: Unbalanced close tag </>; no open start tag.
at [row,col

{unknown-source}]: [54,14]
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:85)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:44)
at org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:77)
at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:44)
at org.apache.synapse.config.xml.AnonymousListMediator.mediate(AnonymousListMediator.java:30)
at org.apache.synapse.mediators.filters.FilterMediator.mediate(FilterMediator.java:197)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:44)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:196)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:44)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at org.apache.synapse.mediators.MediatorWorker.run(MediatorWorker.java:69)
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)
Caused by: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException: Unbalanced close tag </>; no open start tag.
at [row,col {unknown-source}

]: [54,14]
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:336)
at org.apache.axiom.om.impl.traverse.OMChildrenIterator.getNextNode(OMChildrenIterator.java:36)
at org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:58)
at org.jaxen.util.DescendantAxisIterator.hasNext(DescendantAxisIterator.java:101)
at org.jaxen.expr.DefaultStep.evaluate(DefaultStep.java:152)
at org.jaxen.expr.DefaultLocationPath.evaluate(DefaultLocationPath.java:140)
at org.jaxen.expr.DefaultPathExpr.evaluate(DefaultPathExpr.java:142)
at org.jaxen.expr.DefaultXPathExpr.asList(DefaultXPathExpr.java:102)
at org.jaxen.BaseXPath.selectNodesForContext(BaseXPath.java:674)
at org.jaxen.BaseXPath.selectNodes(BaseXPath.java:213)
at org.jaxen.BaseXPath.evaluate(BaseXPath.java:172)
at org.apache.synapse.util.xpath.SynapseXPath.stringValueOf(SynapseXPath.java:297)
at org.apache.synapse.mediators.builtin.PropertyMediator.getResultValue(PropertyMediator.java:302)
at org.apache.synapse.mediators.builtin.PropertyMediator.mediate(PropertyMediator.java:96)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
... 19 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Unbalanced close tag </>; no open start tag.
at [row,col

{unknown-source}

]: [54,14]
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:606)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:479)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:464)
at com.ctc.wstx.sr.BasicStreamReader.reportExtraEndElem(BasicStreamReader.java:3256)
at com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3156)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2829)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1072)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
... 34 more

NOTE : I could reproduce something similar by setting an OM element in the operation context and accessing it in parallel and could fix it by explicitly building the OM element just after setting it . My guess was that this happens because one thread is accessing the XML elements while the other thread is still building the element.



 Comments   
Comment by dushan abeyruwan [ 31/Dec/14 ]

Workaround is to build OM element assigned to property but ideally its not practice as this not documented, thus it should be fixed in "stringToOM", please verify the proposed solution and fix for the next release.

PropertyMediator

case OM : return SynapseConfigUtils.stringToOM(value);

public static OMElement stringToOM(String xml) {
try

{ return AXIOMUtil.stringToOM(xml).buildWithAttachments(); // Just wrap to add logging for any errors }

catch (XMLStreamException e)

{ handleException("Unable to convert a string to OM Node as the string " + "is malformed , String : " + xml, e); }

ret

Comment by Malaka Silva [ 23/Apr/15 ]

Fixed with following by Ishan

https://github.com/wso2/wso2-synapse/commit/7c469232bbd6090d54084a65aeba857deebb381d#diff-5c5f30fd9fe6b94023f63db1291d07e6





[ESBJAVA-3390] Need to verify MB Integration with ESB Inbound Transport (for Multi-tenancy stories) Created: 17/Oct/14  Updated: 23/Apr/15  Resolved: 23/Apr/15

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

Type: Task Priority: Highest
Reporter: dushan abeyruwan Assignee: Malaka Silva
Resolution: Not a bug Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu


Attachments: File jndi1.properties    
Severity: Blocker
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

We should test, WSO2 MB integration with ESB for newly designed Inbound endpoints,

i.e

1.create queue/topic in multi-tenancy mode and connect via super user defined ESB Inbound transport

2. create queue/topic in multi-tenancy mode and integrate with multi-tenancy mode queues via ESB inbound transport with (with ESB multi-tenancy mode)

Also update ESB JMS-Usecases with above scenario.

Then From MB point of view.

if we defined Inbound Transport as

<inboundEndpoint xmlns="http://ws.apache.org/ns/synapse"
                 name="MyJMSListenerEP"
                 sequence="testSequence"
                 onError="errorSequnce"
                 protocol="jms"
                 suspend="false">
   <parameters>

      <parameter name="interval">10000</parameter>
      <parameter name="transport.jms.Destination">dushan.org/foo</parameter>
      <parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
      <parameter name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
      <parameter name="java.naming.provider.url">repository/conf/jndi.properties</parameter>
      <parameter name="transport.jms.SessionAcknowledgement">AUTO_ACKNOWLEDGE</parameter>
      <parameter name="transport.jms.SessionTransacted">false</parameter>
      <parameter name="transport.jms.SubscriptionDurable">false</parameter>
      <parameter name="transport.jms.ConnectionFactoryType">queue</parameter>
   </parameters>
</inboundEndpoint>

we need to finalize the user story for in the context of how to define following property

      <parameter name="java.naming.provider.url">repository/conf/jndi.properties</parameter>

for multi-tenant usecases loading file from jndi.properties will not work as only 1 user will able connect given time, so this must be generalize properly in order to test above scenario



 Comments   
Comment by Malaka Silva [ 23/Apr/15 ]

Default jndi.properties file provides configuration required to connect to Super Tenant. If there is a requirement to connect to multi tenant queue/topic need a have a separate file specif for the tenant.

Sample is attached for wso2.com domain. (jndi1.properties)





[ESBJAVA-3402] NO_ENTITY_BODY property does't remove the body of the response Created: 24/Oct/14  Updated: 23/Apr/15  Resolved: 23/Apr/15

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

Type: Bug Priority: Normal
Reporter: isuru ranawaka 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

 Comments   
Comment by isuru ranawaka [ 24/Oct/14 ]

https://github.com/wso2-dev/product-esb/pull/66

Comment by isuru ranawaka [ 23/Apr/15 ]

https://github.com/wso2/product-esb/pull/120





[ESBJAVA-3334] Removing proxy persistance when enabling and disabling SOAP Tracer for CApps deployment Created: 29/Sep/14  Updated: 23/Apr/15  Resolved: 23/Apr/15

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

Type: Bug Priority: Normal
Reporter: isuru ranawaka 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   

Proxies deployed via CApps get persist when enabling and disabling SOAP Tracer.



 Comments   
Comment by isuru ranawaka [ 01/Oct/14 ]

https://github.com/wso2-dev/carbon-mediation/pull/56

Comment by isuru ranawaka [ 23/Apr/15 ]

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





[ESBJAVA-3613] HTTPS support Inbound Endpoint Created: 20/Mar/15  Updated: 22/Apr/15  Resolved: 22/Apr/15

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

Type: New Feature Priority: Normal
Reporter: isuru ranawaka 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

 Comments   
Comment by isuru ranawaka [ 20/Mar/15 ]

https://github.com/wso2/wso2-synapse/pull/106
https://github.com/wso2/carbon-mediation/pull/84





[ESBJAVA-3656] MessageProcessor will only process messages processed by MessageStores on the same server Created: 21/Apr/15  Updated: 22/Apr/15  Resolved: 22/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: 4.9.0 - M8

Type: Bug Priority: Highest
Reporter: Sandamal Weerasinghe Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB Clustered environment


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
Affects Docs:
Yes

 Description   

Setup:
Cluster 2 ESB instances (ESB-1 and ESB-2)

Both will have a proxy (proxyA) that uses a MessageStore to store messages.
There is a MessageProcessor pinned to ESB-1. The MessageProcessor will not be able to process any messages that go through ProxyA in ESB-2



 Comments   
Comment by Malaka Silva [ 22/Apr/15 ]

https://github.com/wso2/wso2-synapse/commit/4d1816fe3809b9ba7cfe77a50f29d7a62c1eab6e





[ESBJAVA-3655] Endpoint url is not set properly in Service chaining scenarios when Http Endpoint is used Created: 21/Apr/15  Updated: 22/Apr/15  Resolved: 22/Apr/15

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

Type: Patch 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

Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Request always goes to the first endpoint url in following proxy

<proxy name="testCall"
          transports="https http"
          startOnLoad="true"
          trace="disable">
      <description/>
      <target>
         <inSequence>
            <send>
               <endpoint>
                  <http method="POST" uri-template="http://localhost:8080/test/resourceOne"/>
               </endpoint>
            </send>
         </inSequence>
         <outSequence>
            <call>
               <endpoint>
                  <address uri="http://localhost:8080/test/resourceTwo"/>
               </endpoint>
            </call>
            <call>
               <endpoint>
                  <address uri="http://localhost:8080/test/resourceThree"/>
               </endpoint>
            </call>
            <respond/>
         </outSequence>
      </target>
   </proxy>



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

Fixed with following PRs

https://github.com/wso2/wso2-synapse/pull/150
https://github.com/wso2/wso2-synapse/pull/151





[ESBJAVA-3525] References to ESB 4.8.1 in ESB 4.9.0 Created: 05/Feb/15  Updated: 22/Apr/15  Resolved: 22/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.9.0 - M5
Fix Version/s: 4.9.0 - M8

Type: Bug Priority: Highest
Reporter: Asanthi Kulasinghe Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB 4.9.0


Severity: Major
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

The following in ESB 4.9.0 M5 pack still refer to ESB 4.8.1

-Start up console
-Docs are still pointed to 4.8.1
-Release note



 Comments   
Comment by Malaka Silva [ 22/Apr/15 ]

https://github.com/wso2/product-esb/commit/56d8cccc2b5b7e703aeb09fc476466cfdf2967bd





[ESBJAVA-3621] Custom Profile is not being picked when it is configured for a different keystore. Created: 24/Mar/15  Updated: 22/Apr/15  Resolved: 22/Apr/15

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

Type: Bug Priority: Highest
Reporter: Ushani Balasooriya Assignee: Ushani Balasooriya
Resolution: Not a bug Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive config.zip    
Severity: Blocker
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   

Steps :

Configure backend :
------------------------------

1. Use app server as backend
2. Create a new keystore in App server in <Appserver_Home>/repository/resources/security
keytool -genkey -alias appserver -keyalg RSA -keysize 1024 -keypass password -keystore appserver.jks -storepass password
3. Export in to a pem file by following command
keytool -export -alias appserver -keystore appserver.jks -storepass password -file appserver.pem
4. Edit the carbon.xml in appserver as below :
<KeyStore>
<!-- Keystore file location-->
<Location>$

{carbon.home}

/repository/resources/security/appserver.jks</Location>
<!-- Keystore type (JKS/PKCS12 etc.)-->
<Type>JKS</Type>
<!-- Keystore password-->
<Password>password</Password>
<!-- Private Key alias-->
<KeyAlias>appserver</KeyAlias>
<!-- Private Key password-->
<KeyPassword>password</KeyPassword>
</KeyStore>

============
Configure ESB :
1. Created a new keystore.

keytool -genkey -alias esb -keyalg RSA -keysize 1024 -keypass password -keystore esb.jks -storepass password

2. Copy and paste appserver.pem in to the <ESB_HOME>repository/resources/security folder Import appserver.pem in to esb.jks by following command

keytool -import -alias appservernewesb -file appserver.pem -keystore esb.jks -storepass password

3. Configure esb for custom profile in axis2.xml as below.

<parameter name="customSSLProfiles">
<profile>
<servers>10.100.0.31:9443</servers>
<TrustStore>
<Location>repository/resources/security/esb.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
</TrustStore>
</profile>
</parameter>

================
Invoke :

1. restart Appserver (offset=0) and ESB (offset = 10) as side when you start the server as " sh wso2server.sh -Djavax.net.debug=ssl:handshake "
2. Create the below proxy in ESB :

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="SecureHello"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<outSequence>
<send/>
</outSequence>
<endpoint>
<address uri="https://10.100.0.31:9443/services/HelloService/"/>
</endpoint>
</target>
<publishWSDL uri="http://10.100.0.31:9763/services/HelloService?wsdl"/>
<description/>
</proxy>

3. Invoke it as below :

<body>
<p:greet xmlns="http://www.wso2.org/types">
<!-0 to 1 occurrence->
<name>ushani</name>
</p:greet>
</body>

==================

Exception :
------------------

Below exception can be seen in ESB
---------------------------------------------------------

Using SSLEngineImpl.
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256
%% No cached client session

      • ClientHello, TLSv1
        RandomCookie: GMT: 1427197226 bytes = { 152, 200, 123, 233, 167, 31, 129, 76, 82, 13, 145, 239, 158, 144, 110, 253, 174, 148, 53, 111, 86, 120, 38, 184, 94, 0, 51, 34 }
        Session ID: {}
        Cipher Suites: [TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA]
        Compression Methods: { 0 }
        Extension elliptic_curves, curve names: {secp256r1, sect163k1, sect163r2, secp192r1, secp224r1, sect233k1, sect233r1, sect283k1, sect283r1, secp384r1, sect409k1, sect409r1, secp521r1, sect571k1, sect571r1, secp160k1, secp160r1, secp160r2, sect163r1, secp192k1, sect193r1, sect193r2, secp224k1, sect239k1, secp256k1}
        Extension ec_point_formats, formats: [uncompressed]
        ***
        HTTPS-Sender I/O dispatcher-2, WRITE: TLSv1 Handshake, length = 149
        HTTPS-Sender I/O dispatcher-2, READ: TLSv1 Handshake, length = 1149
        *** ServerHello, TLSv1
        RandomCookie: GMT: 1427197226 bytes = { 58, 230, 164, 1, 220, 59, 167, 254, 37, 195, 248, 220, 108, 106, 149, 183, 201, 202, 40, 1, 161, 37, 162, 247, 250, 246, 238, 26 }
        Session ID: {85, 17, 77, 42, 195, 36, 191, 173, 96, 207, 5, 28, 32, 184, 47, 90, 64, 142, 56, 55, 44, 86, 77, 7, 77, 183, 116, 113, 145, 199, 153, 196}
        Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
        Compression Method: 0
        Extension renegotiation_info, renegotiated_connection: <empty>
        ***
        %% Initialized: [Session-4, TLS_DHE_RSA_WITH_AES_128_CBC_SHA]
        ** TLS_DHE_RSA_WITH_AES_128_CBC_SHA
        *** Certificate chain
        chain [0] = [
        [
        Version: V3
        Subject: CN=Ushani Balasooriya, OU=QA, O=WSO2, L=Colombo, ST=Western, C=LK
        Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11

        Key: Sun RSA public key, 1024 bits
        modulus: 94467678938843222479909920872749857904763022228511131018085612761491032927936523994083038059229116044499166098518925481421715807802001202098363173572948510046379625214769177194173189020654979628005032509743025446710870667728988513485560033032968907568579629861624193066871277683587840188665595128959870590457
        public exponent: 65537
        Validity: [From: Tue Mar 24 16:32:11 IST 2015,
        To: Mon Jun 22 16:32:11 IST 2015]
        Issuer: CN=Ushani Balasooriya, OU=QA, O=WSO2, L=Colombo, ST=Western, C=LK
        SerialNumber: [ 6d928a1e]

        Certificate Extensions: 1
        [1]: ObjectId: 2.5.29.14 Criticality=false
        SubjectKeyIdentifier [
        KeyIdentifier [
        0000: B3 CD 4D C8 34 5C D4 57 30 FD 97 81 87 61 8C 7E ..M.4\.W0....a..
        0010: E7 B8 0C EE ....
        ]
        ]

        ]
        Algorithm: [SHA256withRSA]
        Signature:
        0000: 3E CC FF D0 14 22 0C 72 D7 EB DD 43 4B 16 40 D0 >....".r...CK.@.
        0010: 1F 3E 41 4A A8 4D D9 0A 89 59 89 D8 49 84 2F 66 .>AJ.M...Y..I./f
        0020: FD 02 82 CC 66 92 50 75 ED 9F 18 D8 DF 5E B7 E0 ....f.Pu.....^..
        0030: 38 E4 84 93 F6 06 83 FF 73 F1 FB 15 EA D0 0E 2D 8.......s......-
        0040: E7 01 72 B4 BB CA 77 D5 63 EA F7 CB F3 75 9A 23 ..r...w.c....u.#
        0050: B1 16 91 28 56 90 C6 D6 ED 15 ED F1 0F 51 AE A3 ...(V........Q..
        0060: 61 75 13 B9 B5 31 10 66 D8 B6 71 F9 C4 B6 7E 21 au...1.f..q....!
        0070: 15 8A 48 0A 30 12 4A 23 F6 6D BA 56 94 B6 40 04 ..H.0.J#.m.V..@.

        ]
        ***
        HTTPS-Sender I/O dispatcher-2, fatal error: 46: General SSLEngine problem
        sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        %% Invalidated: [Session-4, TLS_DHE_RSA_WITH_AES_128_CBC_SHA]
        HTTPS-Sender I/O dispatcher-2, SEND TLSv1 ALERT: fatal, description = certificate_unknown
        HTTPS-Sender I/O dispatcher-2, WRITE: TLSv1 Alert, length = 2
        HTTPS-Sender I/O dispatcher-2, fatal: engine already closed. Rethrowing javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        [2015-03-24 17:10:27,011] ERROR - TargetHandler I/O error: General SSLEngine problem
        javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1364)
        at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:508)
        at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1189)
        at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1161)
        at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:220)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:254)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:380)
        at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:160)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
        at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
        at java.lang.Thread.run(Thread.java:722)
        Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
        at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1669)
        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:278)
        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1337)
        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:154)
        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
        at sun.security.ssl.Handshaker$1.run(Handshaker.java:808)
        at sun.security.ssl.Handshaker$1.run(Handshaker.java:806)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1301)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:238)
        at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:270)
        ... 9 more
        Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
        at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
        at sun.security.validator.Validator.validate(Validator.java:260)
        at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:283)
        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:138)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1324)
        ... 17 more
        Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
        at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
        at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380)
        ... 23 more
        [2015-03-24 17:10:27,015] WARN - EndpointContext Endpoint : AnonymousEndpoint will be marked SUSPENDED as it failed
        [2015-03-24 17:10:27,015] WARN - EndpointContext Suspending endpoint : AnonymousEndpoint - last suspend duration was : 30000ms and current suspend duration is : 30000ms - Next retry after : Tue Mar 24 17:10:57 IST 2015


        In Appserver backend :
        --------------------------------

        Using SSLEngineImpl.
        Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
        Allow unsafe renegotiation: false
        Allow legacy hello messages: true
        Is initial handshake: true
        Is secure renegotiation: false
        http-nio-9443-exec-12, READ: TLSv1 Handshake, length = 149
        *** ClientHello, TLSv1
        RandomCookie: GMT: 1427197226 bytes = { 152, 200, 123, 233, 167, 31, 129, 76, 82, 13, 145, 239, 158, 144, 110, 253, 174, 148, 53, 111, 86, 120, 38, 184, 94, 0, 51, 34 }

        Session ID: {}
        Cipher Suites: [TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA]
        Compression Methods:

        { 0 }

        Extension elliptic_curves, curve names:

        {secp256r1, sect163k1, sect163r2, secp192r1, secp224r1, sect233k1, sect233r1, sect283k1, sect283r1, secp384r1, sect409k1, sect409r1, secp521r1, sect571k1, sect571r1, secp160k1, secp160r1, secp160r2, sect163r1, secp192k1, sect193r1, sect193r2, secp224k1, sect239k1, secp256k1}

        Extension ec_point_formats, formats: [uncompressed]
        ***
        %% Initialized: [Session-5, SSL_NULL_WITH_NULL_NULL]
        %% Negotiating: [Session-5, TLS_DHE_RSA_WITH_AES_128_CBC_SHA]

      • ServerHello, TLSv1
        RandomCookie: GMT: 1427197226 bytes = { 58, 230, 164, 1, 220, 59, 167, 254, 37, 195, 248, 220, 108, 106, 149, 183, 201, 202, 40, 1, 161, 37, 162, 247, 250, 246, 238, 26 }

        Session ID:

        {85, 17, 77, 42, 195, 36, 191, 173, 96, 207, 5, 28, 32, 184, 47, 90, 64, 142, 56, 55, 44, 86, 77, 7, 77, 183, 116, 113, 145, 199, 153, 196}

        Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
        Compression Method: 0
        Extension renegotiation_info, renegotiated_connection: <empty>
        ***
        Cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA

      • Certificate chain
        chain [0] = [
        [
        Version: V3
        Subject: CN=Ushani Balasooriya, OU=QA, O=WSO2, L=Colombo, ST=Western, C=LK
        Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11

Key: Sun RSA public key, 1024 bits
modulus: 94467678938843222479909920872749857904763022228511131018085612761491032927936523994083038059229116044499166098518925481421715807802001202098363173572948510046379625214769177194173189020654979628005032509743025446710870667728988513485560033032968907568579629861624193066871277683587840188665595128959870590457
public exponent: 65537
Validity: [From: Tue Mar 24 16:32:11 IST 2015,
To: Mon Jun 22 16:32:11 IST 2015]
Issuer: CN=Ushani Balasooriya, OU=QA, O=WSO2, L=Colombo, ST=Western, C=LK
SerialNumber: [ 6d928a1e]

Certificate Extensions: 1
[1]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: B3 CD 4D C8 34 5C D4 57 30 FD 97 81 87 61 8C 7E ..M.4\.W0....a..
0010: E7 B8 0C EE ....
]
]

]
Algorithm: [SHA256withRSA]
Signature:
0000: 3E CC FF D0 14 22 0C 72 D7 EB DD 43 4B 16 40 D0 >....".r...CK.@.
0010: 1F 3E 41 4A A8 4D D9 0A 89 59 89 D8 49 84 2F 66 .>AJ.M...Y..I./f
0020: FD 02 82 CC 66 92 50 75 ED 9F 18 D8 DF 5E B7 E0 ....f.Pu.....^..
0030: 38 E4 84 93 F6 06 83 FF 73 F1 FB 15 EA D0 0E 2D 8.......s......-
0040: E7 01 72 B4 BB CA 77 D5 63 EA F7 CB F3 75 9A 23 ..r...w.c....u.#
0050: B1 16 91 28 56 90 C6 D6 ED 15 ED F1 0F 51 AE A3 ...(V........Q..
0060: 61 75 13 B9 B5 31 10 66 D8 B6 71 F9 C4 B6 7E 21 au...1.f..q....!
0070: 15 8A 48 0A 30 12 4A 23 F6 6D BA 56 94 B6 40 04 ..H.0.J#.m.V..@.

]
***

      • Diffie-Hellman ServerKeyExchange
        DH Modulus: { 233, 230, 66, 89, 157, 53, 95, 55, 201, 127, 253, 53, 103, 18, 11, 142, 37, 201, 205, 67, 233, 39, 179, 169, 103, 15, 190, 197, 216, 144, 20, 25, 34, 210, 195, 179, 173, 36, 128, 9, 55, 153, 134, 157, 30, 132, 106, 171, 73, 250, 176, 173, 38, 210, 206, 106, 34, 33, 157, 71, 11, 206, 125, 119, 125, 74, 33, 251, 233, 194, 112, 181, 127, 96, 112, 2, 243, 206, 248, 57, 54, 148, 207, 69, 238, 54, 136, 193, 26, 140, 86, 171, 18, 122, 61, 175 }

        DH Base:

        { 48, 71, 10, 213, 160, 5, 251, 20, 206, 45, 157, 205, 135, 227, 139, 199, 209, 177, 197, 250, 203, 174, 203, 233, 95, 25, 10, 167, 163, 29, 35, 196, 219, 188, 190, 6, 23, 69, 68, 64, 26, 91, 44, 2, 9, 101, 216, 194, 189, 33, 113, 211, 102, 132, 69, 119, 31, 116, 186, 8, 77, 32, 41, 216, 60, 28, 21, 133, 71, 243, 169, 241, 162, 113, 91, 226, 61, 81, 174, 77, 62, 90, 31, 106, 112, 100, 243, 22, 147, 58, 52, 109, 63, 82, 146, 82 }

        Server DH Public Key:

        { 186, 179, 248, 54, 254, 189, 146, 110, 85, 116, 131, 166, 79, 208, 65, 79, 127, 15, 190, 71, 92, 26, 45, 145, 238, 104, 135, 181, 42, 115, 61, 231, 74, 156, 86, 221, 247, 73, 167, 111, 243, 191, 219, 154, 181, 213, 175, 6, 153, 191, 164, 50, 14, 246, 165, 93, 233, 207, 234, 175, 21, 185, 42, 198, 240, 217, 170, 93, 179, 233, 181, 152, 6, 201, 229, 212, 243, 34, 166, 99, 25, 66, 22, 211, 118, 165, 9, 131, 193, 75, 108, 8, 18, 97, 209, 233 }

        Signed with a DSA or RSA public key

      • ServerHelloDone
        http-nio-9443-exec-12, WRITE: TLSv1 Handshake, length = 1149
        http-nio-9443-exec-13, called closeOutbound()
        http-nio-9443-exec-13, closeOutboundInternal()
        http-nio-9443-exec-13, SEND TLSv1 ALERT: warning, description = close_notify
        http-nio-9443-exec-13, WRITE: TLSv1 Alert, length = 2


 Comments   
Comment by Ushani Balasooriya [ 25/Mar/15 ]

When you provide the keystore defined (esb.jks) as the default truststore, it works. Therefore it seems it doesnt pick custom profile tag

E.g.,
<parameter name="truststore" locked="false">
<TrustStore>
<Location>repository/resources/security/esb.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
</TrustStore>
</parameter-->

Comment by Ushani Balasooriya [ 08/Apr/15 ]

Pls find the configs attached,. Exception received for the attached configs.

http-nio-9443-exec-22, WRITE: TLSv1.2 Application Data, length = 7795
http-nio-9443-exec-32, WRITE: TLSv1.2 Application Data, length = 6325
Using SSLEngineImpl.
http-nio-9443-exec-48, WRITE: TLSv1.2 Application Data, length = 94
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
http-nio-9443-exec-27, WRITE: TLSv1.2 Application Data, length = 3637
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
http-nio-9443-exec-2, READ: TLSv1 Handshake, length = 203

      • ClientHello, TLSv1.2
        RandomCookie: GMT: 172224099 bytes = { 81, 226, 199, 204, 138, 132, 108, 252, 82, 185, 173, 207, 159, 209, 188, 188, 122, 12, 223, 135, 143, 131, 84, 188, 100, 31, 204, 114 }

        Session ID:

        {85, 37, 12, 81, 118, 142, 40, 41, 40, 203, 73, 150, 94, 74, 205, 91, 6, 202, 204, 12, 137, 35, 49, 95, 93, 185, 239, 108, 209, 171, 35, 192}
        Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_MD5]
        Compression Methods: { 0 }
        Extension renegotiation_info, renegotiated_connection: <empty>
        Extension elliptic_curves, curve names: {secp256r1, secp384r1, secp521r1}
        Extension ec_point_formats, formats: [uncompressed]
        Unsupported extension type_35, data:
        Unsupported extension type_13172, data:
        Unsupported extension type_16, data: 00:12:08:73:70:64:79:2f:33:2e:31:08:68:74:74:70:2f:31:2e:31
        Unsupported extension status_request, data: 01:00:00:00:00
        Unsupported extension type_18, data:
        Extension signature_algorithms, signature_algorithms: SHA256withRSA, SHA384withRSA, SHA1withRSA, SHA256withECDSA, SHA384withECDSA, SHA1withECDSA, Unknown (hash:0x4, signature:0x2), SHA1withDSA
        ***
        %% Resuming [Session-4, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA]
        *** ServerHello, TLSv1.2
        RandomCookie: GMT: 1428491533 bytes = { 243, 105, 143, 2, 243, 102, 194, 156, 78, 62, 151, 232, 185, 50, 7, 137, 161, 95, 154, 125, 87, 75, 98, 254, 40, 61, 90, 22 }
        Session ID: {85, 37, 12, 81, 118, 142, 40, 41, 40, 203, 73, 150, 94, 74, 205, 91, 6, 202, 204, 12, 137, 35, 49, 95, 93, 185, 239, 108, 209, 171, 35, 192}

        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
        Compression Method: 0
        Extension renegotiation_info, renegotiated_connection: <empty>
        ***
        Cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
        CONNECTION KEYGEN:
        Client Nonce:
        0000: 0A 44 EE 63 51 E2 C7 CC 8A 84 6C FC 52 B9 AD CF .D.cQ.....l.R...
        0010: 9F D1 BC BC 7A 0C DF 87 8F 83 54 BC 64 1F CC 72 ....z.....T.d..r
        Server Nonce:
        0000: 55 25 0D 0D F3 69 8F 02 F3 66 C2 9C 4E 3E 97 E8 U%...i...f..N>..
        0010: B9 32 07 89 A1 5F 9A 7D 57 4B 62 FE 28 3D 5A 16 .2..._..WKb.(=Z.
        Master Secret:
        0000: 46 EC 0E 6E 43 26 5B B5 B5 5E 10 DF 24 96 15 A0 F..nC&[..^..$...
        0010: C2 BD 1D 59 F9 85 0D 23 71 48 D0 33 10 64 62 5D ...Y...#qH.3.db]
        0020: CA 9A 25 B7 19 55 03 4E D8 3F DE 9E 83 08 AB 24 ..%..U.N.?.....$
        Client MAC write Secret:
        0000: FD F0 B6 57 BE 4F 33 F0 97 62 F6 5E 38 84 C1 14 ...W.O3..b.^8...
        0010: B9 CD B8 E8 ....
        Server MAC write Secret:
        0000: 35 B4 54 18 8D 4C 29 2D 5C 94 5D DA 3F 8E DE 31 5.T..L)-\.].?..1
        0010: 95 54 19 7C .T..
        Client write key:
        0000: B2 3B 25 89 AD F6 BA 49 A4 27 08 4A D2 FC B7 88 .;%....I.'.J....
        Server write key:
        0000: 4F E1 D3 B5 40 BB 81 07 8B 27 BF CB 3E 00 D0 0D O...@....'..>...
        ... no IV derived for this protocol
        http-nio-9443-exec-2, WRITE: TLSv1.2 Handshake, length = 81
        http-nio-9443-exec-2, WRITE: TLSv1.2 Change Cipher Spec, length = 1

      • Finished
        verify_data: { 147, 159, 235, 154, 180, 163, 73, 83, 216, 35, 81, 171 }

        ***
        http-nio-9443-exec-2, WRITE: TLSv1.2 Handshake, length = 64
        http-nio-9443-exec-15, READ: TLSv1.2 Change Cipher Spec, length = 1
        http-nio-9443-exec-15, READ: TLSv1.2 Handshake, length = 64

      • Finished
        verify_data: { 63, 24, 118, 5, 215, 100, 142, 8, 67, 56, 244, 21 }

        ***
        http-nio-9443-exec-15, called closeOutbound()
        http-nio-9443-exec-15, closeOutboundInternal()
        http-nio-9443-exec-15, SEND TLSv1.2 ALERT: warning, description = close_notify
        http-nio-9443-exec-15, WRITE: TLSv1.2 Alert, length = 48
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 16384
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 532
        http-nio-9443-exec-21, WRITE: TLSv1.2 Application Data, length = 13185
        http-nio-9443-exec-44, WRITE: TLSv1.2 Application Data, length = 16384
        http-nio-9443-exec-44, WRITE: TLSv1.2 Application Data, length = 532
        http-nio-9443-exec-46, WRITE: TLSv1.2 Application Data, length = 16384
        http-nio-9443-exec-46, WRITE: TLSv1.2 Application Data, length = 532
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 16384
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 532
        http-nio-9443-exec-46, WRITE: TLSv1.2 Application Data, length = 13663
        http-nio-9443-exec-44, WRITE: TLSv1.2 Application Data, length = 13967
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 16384
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 532
        http-nio-9443-exec-34, WRITE: TLSv1.2 Application Data, length = 2334
        http-nio-9443-exec-20, WRITE: TLSv1.2 Application Data, length = 7090
        http-nio-9443-exec-28, WRITE: TLSv1.2 Application Data, length = 3120
        http-nio-9443-exec-38, WRITE: TLSv1.2 Application Data, length = 225
        http-nio-9443-exec-5, WRITE: TLSv1.2 Application Data, length = 218
        http-nio-9443-exec-33, WRITE: TLSv1.2 Application Data, length = 834
        http-nio-9443-exec-5, WRITE: TLSv1.2 Application Data, length = 1025
        http-nio-9443-exec-38, WRITE: TLSv1.2 Application Data, length = 1318
        http-nio-9443-exec-10, WRITE: TLSv1.2 Application Data, length = 1432
        http-nio-9443-exec-47, WRITE: TLSv1.2 Application Data, length = 1661
        http-nio-9443-exec-45, WRITE: TLSv1.2 Application Data, length = 1226
        Using SSLEngineImpl.
        Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
        Allow unsafe renegotiation: false
        Allow legacy hello messages: true
        Is initial handshake: true
        Is secure renegotiation: false
        http-nio-9443-exec-49, WRITE: TLSv1.2 Application Data, length = 1198
        http-nio-9443-exec-16, WRITE: TLSv1.2 Application Data, length = 335
        http-nio-9443-exec-49, WRITE: TLSv1.2 Application Data, length = 186
        http-nio-9443-exec-1, WRITE: TLSv1.2 Application Data, length = 342
        http-nio-9443-exec-16, WRITE: TLSv1.2 Application Data, length = 319
        http-nio-9443-exec-30, READ: TLSv1 Handshake, length = 203

      • ClientHello, TLSv1.2
        RandomCookie: GMT: -112177254 bytes = { 89, 191, 165, 192, 200, 85, 28, 140, 29, 98, 225, 126, 24, 173, 71, 176, 49, 25, 255, 78, 129, 68, 202, 151, 118, 207, 230, 105 }

        Session ID:

        {85, 37, 12, 81, 118, 142, 40, 41, 40, 203, 73, 150, 94, 74, 205, 91, 6, 202, 204, 12, 137, 35, 49, 95, 93, 185, 239, 108, 209, 171, 35, 192}
        Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_MD5]
        Compression Methods: { 0 }
        Extension renegotiation_info, renegotiated_connection: <empty>
        Extension elliptic_curves, curve names: {secp256r1, secp384r1, secp521r1}
        Extension ec_point_formats, formats: [uncompressed]
        Unsupported extension type_35, data:
        Unsupported extension type_13172, data:
        Unsupported extension type_16, data: 00:12:08:73:70:64:79:2f:33:2e:31:08:68:74:74:70:2f:31:2e:31
        Unsupported extension status_request, data: 01:00:00:00:00
        Unsupported extension type_18, data:
        Extension signature_algorithms, signature_algorithms: SHA256withRSA, SHA384withRSA, SHA1withRSA, SHA256withECDSA, SHA384withECDSA, SHA1withECDSA, Unknown (hash:0x4, signature:0x2), SHA1withDSA
        ***
        %% Resuming [Session-4, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA]
        *** ServerHello, TLSv1.2
        RandomCookie: GMT: 1428491533 bytes = { 89, 78, 103, 116, 158, 85, 142, 197, 139, 251, 200, 16, 133, 226, 80, 201, 247, 252, 119, 232, 85, 135, 226, 251, 201, 28, 170, 104 }
        Session ID: {85, 37, 12, 81, 118, 142, 40, 41, 40, 203, 73, 150, 94, 74, 205, 91, 6, 202, 204, 12, 137, 35, 49, 95, 93, 185, 239, 108, 209, 171, 35, 192}

        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
        Compression Method: 0
        Extension renegotiation_info, renegotiated_connection: <empty>
        ***
        Cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
        CONNECTION KEYGEN:
        Client Nonce:
        0000: F9 50 50 9A 59 BF A5 C0 C8 55 1C 8C 1D 62 E1 7E .PP.Y....U...b..
        0010: 18 AD 47 B0 31 19 FF 4E 81 44 CA 97 76 CF E6 69 ..G.1..N.D..v..i
        Server Nonce:
        0000: 55 25 0D 0D 59 4E 67 74 9E 55 8E C5 8B FB C8 10 U%..YNgt.U......
        0010: 85 E2 50 C9 F7 FC 77 E8 55 87 E2 FB C9 1C AA 68 ..P...w.U......h
        Master Secret:
        0000: 46 EC 0E 6E 43 26 5B B5 B5 5E 10 DF 24 96 15 A0 F..nC&[..^..$...
        0010: C2 BD 1D 59 F9 85 0D 23 71 48 D0 33 10 64 62 5D ...Y...#qH.3.db]
        0020: CA 9A 25 B7 19 55 03 4E D8 3F DE 9E 83 08 AB 24 ..%..U.N.?.....$
        Client MAC write Secret:
        0000: 90 B9 BD C1 F9 55 88 73 3D 45 C1 37 E7 0A 55 9B .....U.s=E.7..U.
        0010: BF 12 6D 8B ..m.
        Server MAC write Secret:
        0000: DA FB 3F AA 40 33 2C 6A 09 EE 4D 13 73 9F 3C 3F ..?.@3,j..M.s.<?
        0010: 3B 5D 44 8A ;]D.
        Client write key:
        0000: DD 05 27 2D 4A 52 E3 50 AE 5E A6 FC 18 76 D4 A4 ..'-JR.P.^...v..
        Server write key:
        0000: DA EA 36 39 85 E1 61 44 0A D5 DA BE 85 53 C6 C9 ..69..aD.....S..
        ... no IV derived for this protocol
        http-nio-9443-exec-30, WRITE: TLSv1.2 Handshake, length = 81
        http-nio-9443-exec-30, WRITE: TLSv1.2 Change Cipher Spec, length = 1

      • Finished
        verify_data: { 58, 186, 191, 2, 14, 188, 211, 84, 28, 96, 155, 114 }

        ***
        http-nio-9443-exec-30, WRITE: TLSv1.2 Handshake, length = 64
        Using SSLEngineImpl.
        http-nio-9443-exec-50, WRITE: TLSv1.2 Application Data, length = 318
        Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
        Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
        Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
        Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
        Allow unsafe renegotiation: false
        Allow legacy hello messages: true
        Is initial handshake: true
        Is secure renegotiation: false
        http-nio-9443-exec-42, WRITE: TLSv1.2 Application Data, length = 400
        http-nio-9443-exec-17, WRITE: TLSv1.2 Application Data, length = 312
        http-nio-9443-exec-14, WRITE: TLSv1.2 Application Data, length = 313
        http-nio-9443-exec-42, WRITE: TLSv1.2 Application Data, length = 1095
        http-nio-9443-exec-50, READ: TLSv1.2 Change Cipher Spec, length = 1
        http-nio-9443-exec-8, WRITE: TLSv1.2 Application Data, length = 246
        http-nio-9443-exec-9, WRITE: TLSv1.2 Application Data, length = 401
        http-nio-9443-exec-31, READ: TLSv1 Handshake, length = 203

      • ClientHello, TLSv1.2
        RandomCookie: GMT: 196672793 bytes = { 142, 234, 69, 130, 131, 175, 154, 248, 238, 87, 8, 61, 216, 165, 66, 28, 221, 165, 65, 137, 43, 224, 150, 237, 126, 201, 17, 176 }

        Session ID:

        {85, 37, 12, 81, 118, 142, 40, 41, 40, 203, 73, 150, 94, 74, 205, 91, 6, 202, 204, 12, 137, 35, 49, 95, 93, 185, 239, 108, 209, 171, 35, 192}
        Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_MD5]
        Compression Methods: { 0 }
        Extension renegotiation_info, renegotiated_connection: <empty>
        http-nio-9443-exec-23, WRITE: TLSv1.2 Application Data, length = 439
        Extension elliptic_curves, curve names: {secp256r1, secp384r1, secp521r1}
        Extension ec_point_formats, formats: [uncompressed]
        Unsupported extension type_35, data:
        Unsupported extension type_13172, data:
        Unsupported extension type_16, data: 00:12:08:73:70:64:79:2f:33:2e:31:08:68:74:74:70:2f:31:2e:31
        Unsupported extension status_request, data: 01:00:00:00:00
        Unsupported extension type_18, data:
        Extension signature_algorithms, signature_algorithms: SHA256withRSA, SHA384withRSA, SHA1withRSA, SHA256withECDSA, SHA384withECDSA, SHA1withECDSA, Unknown (hash:0x4, signature:0x2), SHA1withDSA
        ***
        http-nio-9443-exec-50, READ: TLSv1.2 Handshake, length = 64
        http-nio-9443-exec-23, WRITE: TLSv1.2 Application Data, length = 222
        *** Finished
        verify_data: { 77, 145, 211, 29, 114, 86, 166, 150, 155, 147, 153, 85 }
        ***
        %% Resuming [Session-4, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA]
        *** ServerHello, TLSv1.2
        RandomCookie: GMT: 1428491533 bytes = { 251, 91, 24, 75, 179, 7, 164, 139http-nio-9443-exec-50, called closeOutbound() , 79, 15, 232, 31, 23, 75, 159, 204, 163, 29, 76, 34, 18, 229, 180, 38, 120, 235, 121, 101 }
        Session ID: http-nio-9443-exec-50, closeOutboundInternal(){85, 37, 12, 81, 118, 142, 40, 41, 40, 203, 73, 150, 94, 74, 205, 91, 6, 202, 204, 12, 137, 35, 49, 95, 93, 185, 239, 108, 209, 171, 35, 192}

        http-nio-9443-exec-50Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
        Compression Method: 0
        , SEND TLSv1.2 ALERT: warning, description = close_notify
        Extension renegotiation_info, renegotiated_connection: <empty>
        ***
        Cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
        http-nio-9443-exec-50, WRITE: TLSv1.2 Alert, length = 48
        CONNECTION KEYGEN:
        Client Nonce:
        0000: 0C B9 FD 19 8E EA 45 82 83 AF 9A F8 EE 57 08 3D ......E......W.=
        0010: D8 A5 42 1C DD A5 41 89 2B E0 96 ED 7E C9 11 B0 ..B...A.+.......
        Server Nonce:
        0000: 55 25 0D 0D FB 5B 18 4B B3 07 A4 8B 4F 0F E8 1F U%...[.K....O...
        0010: 17 4B 9F CC A3 1D 4C 22 12 E5 B4 26 78 EB 79 65 .K....L"...&x.ye
        Master Secret:
        0000: 46 EC 0E 6E 43 26 5B B5 B5 5E 10 DF 24 96 15 A0 F..nC&[..^..$...
        0010: C2 BD 1D 59 F9 85 0D 23 71 48 D0 33 10 64 62 5D ...Y...#qH.3.db]
        0020: CA 9A 25 B7 19 55 03 4E D8 3F DE 9E 83 08 AB 24 ..%..U.N.?.....$
        Client MAC write Secret:
        0000: 39 85 F0 F0 50 BE A0 C5 9E 08 5D AF 92 6A F8 F7 9...P.....]..j..
        0010: E7 99 68 EE ..h.
        Server MAC write Secret:
        0000: 5C 2E E7 7D 3D 60 05 4B 32 B1 86 21 3F AE D3 B9 \...=`.K2..!?...
        0010: 6F 9C 6A B9 o.j.
        Client write key:
        0000: 7C 84 D8 B5 DD BB 26 35 D7 56 61 DB 45 C0 2F B5 ......&5.Va.E./.
        Server write key:
        0000: 72 BC 03 B9 5D E1 2F 5F E8 70 A0 55 41 CF 07 6C r...]./_.p.UA..l
        ... no IV derived for this protocol
        http-nio-9443-exec-31, WRITE: TLSv1.2 Handshake, length = 81
        http-nio-9443-exec-31, WRITE: TLSv1.2 Change Cipher Spec, length = 1

      • Finished
        verify_data: { 193, 211, 15, 198, 226, 56, 102, 12, 146, 126, 7, 161 }

        ***
        http-nio-9443-exec-31, WRITE: TLSv1.2 Handshake, length = 64
        http-nio-9443-exec-13, READ: TLSv1.2 Change Cipher Spec, length = 1
        http-nio-9443-exec-13, READ: TLSv1.2 Handshake, length = 64

      • Finished
        verify_data: { 100, 200, 251, 21, 130, 227, 92, 135, 96, 30, 161, 1 }

        ***
        http-nio-9443-exec-13, called closeOutbound()
        http-nio-9443-exec-13, closeOutboundInternal()
        http-nio-9443-exec-13, SEND TLSv1.2 ALERT: warning, description = close_notify
        http-nio-9443-exec-13, WRITE: TLSv1.2 Alert, length = 48
        http-nio-9443-exec-29, WRITE: TLSv1.2 Application Data, length = 1226
        http-nio-9443-exec-6, WRITE: TLSv1.2 Application Data, length = 1226
        http-nio-9443-exec-26, WRITE: TLSv1.2 Application Data, length = 5154
        http-nio-9443-exec-40, WRITE: TLSv1.2 Application Data, length = 357

Comment by Ushani Balasooriya [ 17/Apr/15 ]

This issue was resolved when you used localhost instead of IP in custom profile configuration and proxy configuration.

Comment by Jagath Ariyarathne [ 22/Apr/15 ]

Issue is with /etc/hosts file where it contains an entry with host name as "localhost" for the IP 10.100.0.31. Since the SSL connection is created using host name, above configured profile will not be applied to the connection (connection has "localhost" and profile configured for "10.100.0.31").

Profile configuration should be done for localhost.

Comment by Jagath Ariyarathne [ 22/Apr/15 ]

Custom profile should be configured with correct host name defined in /etc/hosts file.





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

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

Type: Improvement Priority: Highest
Reporter: Isuru Wimalasundera Assignee: Ravi Undupitiya
Resolution: Fixed 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

Comment by Ravi Undupitiya [ 21/Apr/15 ]

ESB 4.9.0 is released with httpcore-nio v4.3.3 which already includes this fix.





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

Status: Resolved
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: Malaka Silva
Resolution: Fixed 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.



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

https://github.com/wso2/wso2-synapse/commit/4f27358ddabbe35f0a2c7e1b3339d4466f02e8db





[ESBJAVA-3519] Error when adding an inbound HTTP endpoint Created: 01/Feb/15  Updated: 21/Apr/15  Resolved: 21/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.9.0 - M5
Fix Version/s: 4.9.0 - M8

Type: Bug Priority: Highest
Reporter: Asanthi Kulasinghe Assignee: Kasun Indrasiri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System :Ubuntu 13.04
Java Version : 1.7.0
ESB 490 M5 (26 /01/2015) - (md5sum : 8229d296d28f94b8099fe224860f57eb)


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

 Description   

[2] is logged when you add an http endpoint
[1] is logged on start up

[2]

[2015-02-01 20:40:11,780] INFO - InboundEndpoint Initializing Inbound Endpoint: HttpListenerEP1
[2015-02-01 20:40:11,782] ERROR - InboundEndpoint Inbound Request processor not found for Inbound EP : HttpListenerEP1 Protocol: http Classnull
[2015-02-01 20:40:11,782] ERROR - SynapseConfiguration Error in initializing inbound endpoint [HttpListenerEP1] Inbound Request processor not found for Inbound EP : HttpListenerEP1 Protocol: http Classnull
[2015-02-01 20:40:11,783] INFO - InboundEndpoint Initializing Inbound Endpoint: test
[2015-02-01 20:40:11,783] ERROR - InboundEndpoint Inbound Request processor not found for Inbound EP : test Protocol: http Classnull
[2015-02-01 20:40:11,783] ERROR - SynapseConfiguration Error in initializing inbound endpoint [test] Inbound Request processor not found for Inbound EP : test Protocol: http Classnull

[1]

[2015-02-01 20:37:59,719] INFO - InboundEndpoint Initializing Inbound Endpoint: HttpListenerEP1
[2015-02-01 20:37:59,721] ERROR - InboundEndpoint Inbound Request processor not found for Inbound EP : HttpListenerEP1 Protocol: http Classnull
[2015-02-01 20:37:59,721] ERROR - RPCInOnlyMessageReceiver Inbound Request processor not found for Inbound EP : HttpListenerEP1 Protocol: http Classnull
org.apache.synapse.SynapseException: Inbound Request processor not found for Inbound EP : HttpListenerEP1 Protocol: http Classnull
at org.apache.synapse.inbound.InboundEndpoint.init(InboundEndpoint.java:63)
at org.wso2.carbon.inbound.CarbonInboundManagementService.addInboundEndpoint(CarbonInboundManagementService.java:89)
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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
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.inbound.stub.InboundAdminStub.addInboundEndpoint(InboundAdminStub.java:372)
at org.wso2.carbon.inbound.ui.internal.InboundManagementClient.addInboundEndpoint(InboundManagementClient.java:127)
at org.apache.jsp.inbound.saveInbound_jsp._jspService(saveInbound_jsp.java:172)
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:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
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.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
at org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_005finsertAttribute_005f7(template_jsp.java:634)
at org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:356)
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:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:411)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
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:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:183)
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:146)
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:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
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:744)
org.apache.axis2.AxisFault: Inbound Request processor not found for Inbound EP : HttpListenerEP1 Protocol: http Classnull
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
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.inbound.stub.InboundAdminStub.addInboundEndpoint(InboundAdminStub.java:372)
at org.wso2.carbon.inbound.ui.internal.InboundManagementClient.addInboundEndpoint(InboundManagementClient.java:127)
at org.apache.jsp.inbound.saveInbound_jsp._jspService(saveInbound_jsp.java:172)
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:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
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.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
at org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_005finsertAttribute_005f7(template_jsp.java:634)
at org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:356)
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:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:411)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
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:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:183)
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:146)
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:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
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:744)



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

Fix in M8





[ESBJAVA-3304] ESB server is not getting started correctly if the jms enpoints are down Created: 11/Sep/14  Updated: 21/Apr/15  Resolved: 21/Apr/15

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

Type: Bug Priority: Highest
Reporter: Aparna Karunarathna Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack: ESB481
Setup: Standalone
Java: jdk1.7.0_51
OS: Ubuntu 14.04


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

 Description   

ESB server is not getting started if the jms endpoints (broke down) are down, it gets hanged till the endpoints are getting up. if the broker is started, then ESB is getting started and can be accessed to the ESB Mgt console

Steps to reproduce
1. Create a JMS proxy service that's listened to a brocker
2. Stop the broker
3. Restart the ESB and server gets hanged till the jms endpoints are getting up



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

This is the expected behavior of axis2 transports. As a solution use JMS inbound transport instead of JMS axis2 transport.





[ESBJAVA-3642] Out of Memory error when using JSON formatter with a malformed xml Created: 10/Apr/15  Updated: 21/Apr/15  Resolved: 21/Apr/15

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: 4.9.0 - M8

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

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

 Description   

When using the JSON formatter and a malformed xml message is sent the server goes out of memory under a high load.



 Comments   
Comment by Sandamal Weerasinghe [ 21/Apr/15 ]

Fixed with commit
https://github.com/wso2/wso2-synapse/commit/9caef997543070a2c1a52c797afbc6afb4ba932e





[ESBJAVA-3518] HEAD method invocation for APIs fail in tenant mode Created: 01/Feb/15  Updated: 21/Apr/15  Resolved: 21/Apr/15

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

Type: Bug Priority: Highest
Reporter: Asanthi Kulasinghe Assignee: Ravi Undupitiya
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System :Ubuntu 13.04
Java Version : 1.7.0
ESB 490 M5 (26 /01/2015) - (md5sum : 8229d296d28f94b8099fe224860f57eb)


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

 Description   

Deploy an API in tenant mode.
Invoke the head method.

curl -v -H "Content-Type:application/xml" -X GET http://172.20.10.2:8280/t/kaushie.com/testAPI_ESB976/customerservice/customers/123
curl: /usr/local/lib/libldap_r-2.4.so.2: no version information available (required by /usr/lib/x86_64-linux-gnu/libcurl.so.4)
curl: /usr/local/lib/liblber-2.4.so.2: no version information available (required by /usr/lib/x86_64-linux-gnu/libcurl.so.4)

  • About to connect() to 172.20.10.2 port 8280 (#0)
  • Trying 172.20.10.2...
  • Connected to 172.20.10.2 (172.20.10.2) port 8280 (#0)
    > GET /t/kaushie.com/testAPI_ESB976/customerservice/customers/123 HTTP/1.1
    > User-Agent: curl/7.29.0
    > Host: 172.20.10.2:8280
    > Accept: /
    > Content-Type:application/xml
    >
    < HTTP/1.1 200 OK
    < Content-Type: application/xml
    < Date: Sun, 01 Feb 2015 14:49:58 GMT
    < Transfer-Encoding: chunked
    <
  • Connection #0 to host 172.20.10.2 left intact
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Customer><id>123</id><name>John</name></Customer>kaushie@kaushie-ThinkPad-T530:~$
    kaushie@kaushie-ThinkPad-T530:~$ curl -v -H "Content-Type:application/xml" -X HEAD http://172.20.10.2:8280/t/kaushie.com/testAPI_ESB976/customerservice/customers/123
    curl: /usr/local/lib/libldap_r-2.4.so.2: no version information available (required by /usr/lib/x86_64-linux-gnu/libcurl.so.4)
    curl: /usr/local/lib/liblber-2.4.so.2: no version information available (required by /usr/lib/x86_64-linux-gnu/libcurl.so.4)
  • About to connect() to 172.20.10.2 port 8280 (#0)
  • Trying 172.20.10.2...
  • Connected to 172.20.10.2 (172.20.10.2) port 8280 (#0)
    > HEAD /t/kaushie.com/testAPI_ESB976/customerservice/customers/123 HTTP/1.1
    > User-Agent: curl/7.29.0
    > Host: 172.20.10.2:8280
    > Accept: /
    > Content-Type:application/xml
    >
  • Empty reply from server
  • Connection #0 to host 172.20.10.2 left intact
    curl: (52) Empty reply from server

API:

<api name="headTestAPI_ESB976" context="/t/kaushie.com/testAPI_ESB976">
<resource methods="OPTIONS HEAD GET" uri-template="*">
<inSequence>
<send>
<endpoint>
<address uri="http://localhost:9773/jaxrs_basic/services/customers/"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</resource>
</api>



 Comments   
Comment by Ravi Undupitiya [ 21/Apr/15 ]

This is a duplicate of https://wso2.org/jira/browse/ESBJAVA-3594 - the fix in that is in kernel, however ESB pack won't have the fix till kernel is released.





[ESBJAVA-3581] User transaction not get commit or rollback Created: 25/Feb/15  Updated: 21/Apr/15  Resolved: 21/Apr/15

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

Type: Bug Priority: Normal
Reporter: dhanuka ranasinghe Assignee: Malaka Silva
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File ESBJAVA-3581.patch     File JMSTestPlan-PointtoPoint.jmx     File Proxy-JMS    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Even though use XA and non-XA datasource within a transaction context , transaction not get commit or rollback. I have attached sample ESB proxy service and datasource configuration here with.



 Comments   
Comment by dhanuka ranasinghe [ 30/Mar/15 ]

Data source configuration:

<datasource>
<name>PGDB</name>
<jndiConfig>
<name>jdbc/PGDB</name>
</jndiConfig>
<definition type="RDBMS">
<configuration>
<dataSourceClassName>org.postgresql.xa.PGXADataSource</dataSourceClassName>
<defaultAutoCommit>false</defaultAutoCommit>
<maxActive>150</maxActive>
<InitialSize>100</InitialSize>
<maxWait>60000</maxWait>
<validationQuery>select 1 </validationQuery>
<validationInterval>30000</validationInterval>
<testWhileIdle>true</testWhileIdle>
<maxIdle>25</maxIdle>
<minIdle>20</minIdle>
<removeAbandonedTimeout>60</removeAbandonedTimeout>
<removeAbandoned>true</removeAbandoned>
<logAbandoned>true</logAbandoned>
<testOnBorrow>true</testOnBorrow>
<accessToUnderlyingConnectionAllowed>true</accessToUnderlyingConnectionAllowed>
<dataSourceProps>
<property name="serverName">localhost</property>
<property name="portNumber">5432</property>
<property name="databaseName">db1</property>
<property name="user">postgres</property>
<property name="password">postgres</property>
</dataSourceProps>
</configuration>
</definition>
</datasource>

Comment by dhanuka ranasinghe [ 02/Apr/15 ]

JMeter script for test

Comment by Malaka Silva [ 20/Apr/15 ]

https://github.com/wso2/wso2-synapse/pull/143

Comment by Malaka Silva [ 21/Apr/15 ]

https://github.com/wso2/wso2-synapse/commit/4551b66a69907a4cc9ed7306c76486c105fb96ae





[ESBJAVA-3644] Couldn't establish the connection with endpoint using desired transport level security(TLS) for PassThroughHttpSSLSender Created: 10/Apr/15  Updated: 21/Apr/15  Resolved: 21/Apr/15

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

Type: Bug Priority: High
Reporter: Rajeevan Aiyadurai Assignee: Kasun Indrasiri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB 4.8.1
JDK 1.7_60


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   

We couldn't establish the connection with end point using a specific TLS version( TLSv1/TLSv1.1/TLSv1.2) which is defined in PassThroughHttpSender, rather it is using TLSv1 as default protocol. But this is working correctly in the Listener part configured in PassThroughHttpListener.
When we debug the code we found that PassThroughHttpListener and PassThroughHttpSender are using two different implementation logic. Ideally sender should support the configured protocol instead of using a default protocol.



 Comments   
Comment by Buddhima Wijeweera [ 20/Apr/15 ]

Hi,

Please refer following to fix this.
Diff : https://patch-diff.githubusercontent.com/raw/wso2/wso2-synapse/pull/144.diff
PR : https://github.com/wso2/wso2-synapse/pull/144

Thank you!





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

Status: Resolved
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: 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

 Comments   
Comment by isuru ranawaka [ 20/Apr/15 ]

https://github.com/wso2/wso2-synapse/pull/145





[ESBJAVA-3629] [Entitlement Mediator] Session reuse is not handled properly in Thrift client Created: 30/Mar/15  Updated: 20/Apr/15  Resolved: 20/Apr/15

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

Type: Bug Priority: Highest
Reporter: Omindu Rathnaweera Assignee: Omindu Rathnaweera
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

 Description   

Steps to reproduce:

  • Setup the entitlement mediator for an ESB proxy service
  • Invoke the proxy service once
  • Invoke the service for the second time after 30+ minutes (Session ID invalidates after 30 minutes idle time)
  • The following exception can be seen in ESB console

TID: [0] [ocessor-17] [ESB] [2015-03-25 18:15:56,778] ERROR

{org.wso2.carbon.identity.entitlement.mediator.EntitlementMediator}
  • Error occurred while evaluating the policy {org .wso2.carbon.identity.entitlement.mediator.EntitlementMediator}

    org.wso2.carbon.identity.entitlement.proxy.exception.EntitlementProxyException: Error while getting decision from PDP using ThriftEntitlementServiceClient
    at org.wso2.carbon.identity.entitlement.proxy.thrift.ThriftEntitlementServiceClient.getDecision(ThriftEntitlementServiceClient.java:130)
    at org.wso2.carbon.identity.entitlement.proxy.thrift.ThriftEntitlementServiceClient.getDecision(ThriftEntitlementServiceClient.java:64)
    at org.wso2.carbon.identity.entitlement.proxy.PEPProxy.getDecision(PEPProxy.java:83)
    at org.wso2.carbon.identity.entitlement.proxy.PEPProxy.getDecision(PEPProxy.java:54)
    at org.wso2.carbon.identity.entitlement.mediator.EntitlementMediator.mediate(EntitlementMediator.java:167)
    at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:74)
    at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:44)
    at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:135)
    at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:200)
    at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:74)
    at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:44)
    at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:135)
    at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
    at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
    at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
    at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
    at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
    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)
    Caused by: EntitlementException(message:Error occurred when invoking the Thrift based Entitlement Service.)
    at org.wso2.carbon.identity.entitlement.proxy.generatedCode.EntitlementThriftClient$getDecision_result.read(EntitlementThriftClient.java:882)
    at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
    at org.wso2.carbon.identity.entitlement.proxy.generatedCode.EntitlementThriftClient$Client.recv_getDecision(EntitlementThriftClient.java:63)
    at org.wso2.carbon.identity.entitlement.proxy.generatedCode.EntitlementThriftClient$Client.getDecision(EntitlementThriftClient.java:51)
    at org.wso2.carbon.identity.entitlement.proxy.thrift.ThriftEntitlementServiceClient.getDecision(ThriftEntitlementServiceClient.java:126)
    ... 19 more



 Comments   
Comment by Omindu Rathnaweera [ 30/Mar/15 ]

When the ThriftEntitlementServiceClient calls to IS to get the evaluation for a XACML request, the session ID for the authentication is passed along with the XACML request. If the time difference between 2 calls to the IS from ESB is more than 30 minutes, IS considers the particular session ID as invalid and throws an exception. The previously mentioned exception occurs when ThriftEntitlementServiceClient sends the XACML request with the expired session ID.

Comment by Omindu Rathnaweera [ 08/Apr/15 ]

PR for the fix: https://github.com/wso2/carbon-identity/pull/185

Comment by Omindu Rathnaweera [ 17/Apr/15 ]

Merged with: https://github.com/wso2/carbon-identity/commit/8e1b476c332119ab98d2b883d1ea38bca0f8c6fc





Generated at Mon Apr 27 09:33:30 IST 2015 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.