[ESBJAVA-4717] DOS Safety in ESB vfs transport Created: 30/Jun/16  Updated: 30/Jun/16  Resolved: 30/Jun/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0, 5.0.0-Pre-RC

Type: Improvement Priority: Normal
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
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   

assume there are 100.000 files in a directory. ESB scans every 5 seconds. With the start of the scan there is no way to stop VFS processing these 100.000 files



 Comments   
Comment by Rajith Vitharana [ 30/Jun/16 ]

Fixed with pull - https://github.com/wso2/wso2-synapse/pull/590
commit - 3dfa3cfd32cbccbc67b8d90c397b065c258cff21
to wso2-synapse

Fix is to check whether the proxy is deactivated or not before processing every file. So there are many files in the folder and if you need to stop the process in the middle, then what you have to do is simply deactivate the proxy service





[ESBJAVA-4718] Adding none action to VFS transport Created: 30/Jun/16  Updated: 30/Jun/16  Resolved: 30/Jun/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0, 5.0.0-Pre-RC

Type: Improvement Priority: Normal
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
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   

There is no NONE action in ESB vfs transport, Only possible values are DELETE and MOVE



 Comments   
Comment by Rajith Vitharana [ 30/Jun/16 ]

Fixed with git pull - https://github.com/wso2/wso2-synapse/pull/573/
commit - caab2ca176b718ca282fd53b284fc0ddbb822ba4





[ESBJAVA-4719] Max-Size-Filter for ESB vfs transport Created: 30/Jun/16  Updated: 30/Jun/16  Resolved: 30/Jun/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0, 5.0.0-Pre-RC

Type: Improvement Priority: Normal
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
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   

Process files only are smaller than given size



 Comments   
Comment by Rajith Vitharana [ 30/Jun/16 ]

Fixed with git pull - https://github.com/wso2/wso2-synapse/pull/573/
commit - caab2ca176b718ca282fd53b284fc0ddbb822ba4





[ESBJAVA-4669] Option to ignore processing sub folders in synapse-vfs-transport Created: 09/Jun/16  Updated: 30/Jun/16  Resolved: 30/Jun/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0, 5.0.0-Pre-RC

Type: Improvement Priority: Normal
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
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   

Current implementation also process subfolders as normal files, hence need to ignore subfolders when processing files.



 Comments   
Comment by Rajith Vitharana [ 30/Jun/16 ]

Fixed with git pull - https://github.com/wso2/wso2-synapse/pull/573/
commit - caab2ca176b718ca282fd53b284fc0ddbb822ba4





[ESBJAVA-4720] Skip processing sub folders in ESB vfs transport Created: 30/Jun/16  Updated: 30/Jun/16  Resolved: 30/Jun/16

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

Type: Improvement Priority: Normal
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

currently sub folders also gets processed in vfs transport, need to avoid that



 Comments   
Comment by Rajith Vitharana [ 30/Jun/16 ]

duplicate issue - https://wso2.org/jira/browse/ESBJAVA-4669





[ESBJAVA-4692] Message Processor does not invoke fault sequence for https endpoints Created: 21/Jun/16  Updated: 29/Jun/16  Resolved: 29/Jun/16

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

Type: Bug Priority: High
Reporter: Jagath Ariyarathne Assignee: Chanaka Fernando
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File patch.diff    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Scheduled Message Forwarding Processor does not invoke fault sequence when it received Soap Fault from back-end, when the back-end URL is configured as https. This works fine for http. To reproduce, FORCE_ERROR_ON_SOAP_FAULT is set to true before message is added to the message store.



 Comments   
Comment by Jagath Ariyarathne [ 21/Jun/16 ]

Can be fixed with attached diff.

Comment by Jagath Ariyarathne [ 29/Jun/16 ]

Fixed with https://github.com/wso2/wso2-synapse/pull/588/commits/767943c5ae26df656312d56386f8c267c0e08fb3





[ESBJAVA-4714] Multiple security vulnerabilities Created: 29/Jun/16  Updated: 29/Jun/16  Resolved: 29/Jun/16

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

Type: Bug Priority: Normal
Reporter: Marcin Suchocki Assignee: Chanaka Fernando
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   

I have discovered multiple security vulnerabilities in WSO2 ESB. Is there any specific way to disclose them? I'd like to avoid posting them to public bugtrac before they will be addressed.



 Comments   
Comment by Prabath Siriwardena [ 29/Jun/16 ]

Hi Marcin,

Please report the issue to security@wso2.com. The process of reporting security vulnerability are defined here: http://wso2.com/security.

Also - all the security patches issued so far are available at http://wso2.com/security-patch-releases.

Thanks & regards,
-Prabath





[ESBJAVA-4712] Setting message retained flag false by default in MQTT transport sender Created: 29/Jun/16  Updated: 29/Jun/16  Resolved: 29/Jun/16

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

Type: Bug Priority: Normal
Reporter: Eranda Rajapakshe Assignee: Eranda Rajapakshe
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 Eranda Rajapakshe [ 29/Jun/16 ]

This issue was fixed in this PR [1]

[1]. https://github.com/wso2/wso2-axis2-transports/pull/93/





[ESBJAVA-4702] Can't read any custom JMS properties with inbound endpoints Created: 22/Jun/16  Updated: 29/Jun/16  Resolved: 29/Jun/16

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

Type: Bug Priority: Highest
Reporter: Manu Perera Assignee: Nuwan Wimalasekara
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   

Can't read JMS property as follows

<property name="myVal" expression="get-property('transport', 'myProp')" scope="default" type="STRING"/>

[1] https://www.mail-archive.com/dev@wso2.org/msg59893.html



 Comments   
Comment by Nuwan Wimalasekara [ 29/Jun/16 ]

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





[ESBJAVA-4679] VFS transport passwords are visible in clear text, need a way to use encrypted passwords Created: 15/Jun/16  Updated: 28/Jun/16  Resolved: 28/Jun/16

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0, 5.0.0-Pre-RC

Type: Improvement Priority: Normal
Reporter: Rajith Vitharana Assignee: Chanaka Fernando
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Reference
relates to DEVTOOLESB-494 VFS transport passwords are visible i... Open
relates to DOCUMENTATION-3541 VFS transport passwords are visible i... Open
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Comments   
Comment by Rajith Vitharana [ 28/Jun/16 ]

This was fixed with [10] and [11]. [10] fixes the issue of securing vfs password, while [11] fixes an UI issue where we cannot see source view of the proxy after securing vfs password in that proxy.

This fix will add the improvement of securing vfs passwords in ESB proxy. For this improvement to work, you need to provide details required for password decryption in the "<ESB_HOME>/repository/conf/axis2/axis2.xml" file, vfs transport receiver element as in [1]. Then you need to encrypt "username:password" and provide that encrypted value in the proxy parameter as in[3](As you can see, you need to add "

{wso2:vault-decrypt('encryptedValue')}

" to add the encrypted username password)

To encrypt the "username:password" part you can use wso2 cipher tool as described in[5], under heading "Encrypting passwords manually", the same instructions are provided in link[6] as well. Or you can use custom tool which we developed[8] as well. Usage instructions are provided in the REAME file of the tool.

Note1 - as you can see passwords in the config [1] is in plain text, so if you need to secure them as well, you can use wso2 securevault for that[2][7] (This improvement include the fix to resolve those aliases as well). So securevault secured config would be like [4]
Note2 - Use same configs to do the encryption decryption both, for example, say you use BC(BouncyCastle) provider for encryption(in the custom tool[8] you need to add "security.provider=BC" to the properties file to use BC), then you need to mention that information in decryption security config[1] as well (you need to add parameter[9] to the config[1] to do that)

[1] - <transportReceiver class="org.apache.synapse.transport.vfs.VFSTransportListener" name="vfs">
<parameter locked="false" name="keystore.identity.location">repository/resources/security/wso2carbon.jks</parameter>
<parameter locked="false" name="keystore.identity.type">JKS</parameter>
<parameter locked="false" name="keystore.identity.store.password">wso2carbon</parameter>
<parameter locked="false" name="keystore.identity.key.password">wso2carbon</parameter>
<parameter locked="false" name="keystore.identity.alias">wso2carbon</parameter>
</transportReceiver>
[2] - https://docs.wso2.com/display/Carbon420/Carbon+Secure+Vault+Implementation
[3] - <parameter name="transport.vfs.FileURI">smb://

{wso2:vault-decrypt('encryptedValue')}

@smb.host/project2</parameter>
[4] - <transportReceiver class="org.apache.synapse.transport.vfs.VFSTransportListener" name="vfs">
<parameter locked="false" name="keystore.identity.location">repository/resources/security/wso2carbon.jks</parameter>
<parameter locked="false" name="keystore.identity.type">JKS</parameter>
<parameter locked="false" name="keystore.identity.store.password" svns:secretAlias="vfs.transport.keystore.password">password</parameter>
<parameter locked="false" name="keystore.identity.key.password" svns:secretAlias="vfs.transport.key.password">password</parameter>
<parameter locked="false" name="keystore.identity.alias">wso2carbon</parameter>
</transportReceiver>
[5] - https://docs.wso2.com/display/Carbon445/Encrypting+Passwords+with+Cipher+Tool
[6] - http://prabu-lk.blogspot.com/2016/04/enable-securevault-support-for.html
[7] - http://xacmlinfo.org/2012/08/12/secure-plain-text-passwords-in-wso2-carbon-configuration-files/
[8] - https://github.com/lankavitharana/SecureVaultEncryptUtil
[9] - <parameter locked="false" name="security.provider">BC</parameter>
[10] - wso2-synapse (public master) commit - 30f4df4b44480d4741469e1f2ad14e0c8292ab6d, pull - https://github.com/wso2/wso2-synapse/pull/585
[11] - carbon-mediation (public master) commit - 8f01cdaca7fdd5696d4538ae3b065d3ceda025e8

Comment by Rajith Vitharana [ 28/Jun/16 ]

Properties we can add in the axis2.xml vfs transport receiver are as below

keystore.identity.location
keystore.identity.store.username
keystore.identity.store.password
keystore.identity.alias
keystore.identity.type=(JKS etc)
keystore.identity.parameters=enableHostnameVerifier=false;keyStoreCertificateFilePath=/home/esb.cer
keystore.identity.key.username
keystore.identity.key.password
cipher.algorithm=defaults to RSA
cipher.type=('symmetric' or 'asymmetric')
security.provider=(BC etc)
input.encode.type=says whether input is in which encoding type, defaults to BASE64
output.encode.type=says output should be in which encoding type, defaults to null (no encoding)





[ESBJAVA-4695] Adding external property input support to data mapper mediator and engine Created: 21/Jun/16  Updated: 28/Jun/16  Resolved: 28/Jun/16

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

Type: Improvement Priority: Normal
Reporter: Eranda Rajapakshe Assignee: Eranda Rajapakshe
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   

External property input support is needed, in order to get properties from contexts like Synapse, Axis2, Transport etc..

Also this can be useful when using data mapper engine independently from the ESB



 Comments   
Comment by Eranda Rajapakshe [ 28/Jun/16 ]

This improvement was added with PR [1]

[1]. https://github.com/wso2/carbon-mediation/pull/668





[ESBJAVA-4680] Make ESB source view Read-Only Created: 15/Jun/16  Updated: 24/Jun/16  Resolved: 24/Jun/16

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

Type: Improvement Priority: High
Reporter: viraj senevirathne Assignee: viraj senevirathne
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 viraj senevirathne [ 15/Jun/16 ]

Solved with https://github.com/wso2/carbon-mediation/pull/655





[ESBJAVA-4704] ESB is not responding to the client when receiving response with Content-Length = 0 Created: 23/Jun/16  Updated: 24/Jun/16  Resolved: 24/Jun/16

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

Type: Bug Priority: Highest
Reporter: Chanaka Fernando Assignee: Chanaka Fernando
Resolution: Fixed Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0
Test cases added: No

 Description   

This issue has identified during the connector testing when there is a back end which is returning a 403 response with Content-Length = 0, ESB throws a parser error and trigger a fault instead of responding with the same response to the client.

[2016-06-23 09:41:11,775] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "POST /services/z HTTP/1.1[\r][\n]"
[2016-06-23 09:41:11,776] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Host: localhost:8280[\r][\n]"
[2016-06-23 09:41:11,777] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Connection: keep-alive[\r][\n]"
[2016-06-23 09:41:11,777] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Content-Length: 182[\r][\n]"
[2016-06-23 09:41:11,777] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Cache-Control: no-cache[\r][\n]"
[2016-06-23 09:41:11,778] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
[2016-06-23 09:41:11,778] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Content-Type: application/json[\r][\n]"
[2016-06-23 09:41:11,778] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36[\r][\n]"
[2016-06-23 09:41:11,779] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Postman-Token: 0d3f1280-5865-fcca-e3e5-123ab35d65f7[\r][\n]"
[2016-06-23 09:41:11,779] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Accept: */*[\r][\n]"
[2016-06-23 09:41:11,779] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Accept-Encoding: gzip, deflate[\r][\n]"
[2016-06-23 09:41:11,779] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "Accept-Language: en-US,en;q=0.8[\r][\n]"
[2016-06-23 09:41:11,779] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "[\r][\n]"
[2016-06-23 09:41:11,779] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "{[\n]"
[2016-06-23 09:41:11,780] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "  "apiUrl": "https://apisandbox-api.zuora.com/rest",[\n]"
[2016-06-23 09:41:11,780] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "  "apiVersion": "v1",[\n]"
[2016-06-23 09:41:11,780] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "  "apiAccessKeyId": "kesavany@wso2.com",[\n]"
[2016-06-23 09:41:11,780] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "  "apiSecretAccessKey": "Zuora@wso2",[\n]"
[2016-06-23 09:41:11,780] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "  "paymentMethodId" : ""[\n]"
[2016-06-23 09:41:11,780] DEBUG - wire HTTP-Listener I/O dispatcher-3 >> "}"
[2016-06-23 09:42:35,112] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "DELETE /rest/v1/payment-methods/ HTTP/1.1[\r][\n]"
[2016-06-23 09:42:35,113] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Authorization: Basic a2VzYXZhbnlAd3NvMi5jb206WnVvcmFAd3NvMg==[\r][\n]"
[2016-06-23 09:42:35,116] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
[2016-06-23 09:42:35,116] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Accept: */*[\r][\n]"
[2016-06-23 09:42:35,116] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Cache-Control: no-cache[\r][\n]"
[2016-06-23 09:42:35,116] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Postman-Token: 0d3f1280-5865-fcca-e3e5-123ab35d65f7[\r][\n]"
[2016-06-23 09:42:35,116] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Accept-Encoding: gzip, deflate[\r][\n]"
[2016-06-23 09:42:35,117] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Accept-Language: en-US,en;q=0.8[\r][\n]"
[2016-06-23 09:42:35,117] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Content-Type: application/json[\r][\n]"
[2016-06-23 09:42:35,117] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Host: apisandbox-api.zuora.com[\r][\n]"
[2016-06-23 09:42:35,117] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "Connection: Keep-Alive[\r][\n]"
[2016-06-23 09:42:35,117] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-23 09:42:35,117] DEBUG - wire HTTPS-Sender I/O dispatcher-3 << "[\r][\n]"
[2016-06-23 09:42:36,182] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "HTTP/1.1 403 Forbidden[\r][\n]"
[2016-06-23 09:42:36,182] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Server: Zuora App[\r][\n]"
[2016-06-23 09:42:36,182] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Access-Control-Allow-Credentials: true[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Access-Control-Allow-Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Content-Length: 0[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Expires: Thu, 23 Jun 2016 04:12:36 GMT[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Cache-Control: max-age=0, no-cache, no-store[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Pragma: no-cache[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Date: Thu, 23 Jun 2016 04:12:36 GMT[\r][\n]"
[2016-06-23 09:42:36,183] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "Connection: keep-alive[\r][\n]"
[2016-06-23 09:42:36,184] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "[\r][\n]"
[2016-06-23 09:43:02,539] ERROR - JsonUtil #writeAsJson. Payload could not be written as JSON. MessageID: urn:uuid:5cf26791-ef90-410a-9658-a4099f5fbc17
[2016-06-23 09:43:02,540] ERROR - PassThroughHttpSender Failed to submit the response
org.apache.axis2.AxisFault: Payload could not be written as JSON.
	at org.apache.synapse.commons.json.JsonUtil.writeAsJson(JsonUtil.java:260)
	at org.apache.synapse.commons.json.JsonStreamFormatter.writeTo(JsonStreamFormatter.java:61)
	at org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:555)
	at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:264)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
	at org.apache.synapse.mediators.builtin.RespondMediator.mediate(RespondMediator.java:35)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:87)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:292)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:774)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:282)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:546)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:179)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:255)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
[2016-06-23 09:43:02,541] ERROR - Axis2Sender Access-Control-Allow-Credentials:true,Access-Control-Allow-Origin:chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop,Cache-Control:max-age=0, no-cache, no-store,Expires:Thu, 23 Jun 2016 04:12:36 GMT,Pragma:no-cache,<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope> Unexpected error sending message back
org.apache.axis2.AxisFault: Failed to submit the response
	at org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:613)
	at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:266)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
	at org.apache.synapse.mediators.builtin.RespondMediator.mediate(RespondMediator.java:35)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:87)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:292)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:774)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:282)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:546)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:179)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:255)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.axis2.AxisFault: Payload could not be written as JSON.
	at org.apache.synapse.commons.json.JsonUtil.writeAsJson(JsonUtil.java:260)
	at org.apache.synapse.commons.json.JsonStreamFormatter.writeTo(JsonStreamFormatter.java:61)
	at org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:555)
	at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:264)
	... 15 more
[2016-06-23 09:43:03,973]  INFO - LogMediator To: , WSAction: , SOAPAction: , MessageID: urn:uuid:5cf26791-ef90-410a-9658-a4099f5fbc17, Direction: response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Access-Control-Allow-Credentials:true,Access-Control-Allow-Origin:chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop,Cache-Control:max-age=0, no-cache, no-store,Expires:Thu, 23 Jun 2016 04:12:36 GMT,Pragma:no-cache,<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope> Unexpected error sending message back, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope>



 Comments   
Comment by Chanaka Fernando [ 23/Jun/16 ]

This issue is fixed with following PR [1].

[1] https://github.com/wso2/wso2-synapse/commit/2776abf03789d7d9b7ee8fbe0f1c8c294ad7aa71





Generated at Thu Jun 30 19:26:31 IST 2016 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.