[ESBJAVA-3374] Message Forwarding Processor needs to activate manually after deactivation Created: 12/Oct/14  Updated: 22/Aug/16

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

Type: Improvement Priority: Highest
Reporter: Chanaka Fernando Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

During an error scenario, Message Processor get deactivate automatically. But it is not activating automatically when the BE is up and running. Need to setup a timer to check and reactivate the processor if the BE is working correctly.



 Comments   
Comment by Priyadarssini Kishokumar [ 29/Jan/15 ]

This is an enhancement, we'll be considering it in our future release.
Closing the issue since it is not a bug.





[ESBJAVA-4876] DataMapper: does not create the required output element with underscore Created: 30/Aug/16  Updated: 30/Aug/16

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

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

Attachments: XML File input.xml     XML File output.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When there's a underscore in the required output, it will only give the first word for the output mapping which drops the other words after the underscore.






[ESBJAVA-4873] Transport level information does not match with SOAP Message namespace URI Created: 26/Aug/16  Updated: 30/Aug/16

Status: Open
Project: WSO2 ESB
Component/s: Endpoints Management, Mediators, Transport
Affects Version/s: 4.8.1
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: Faisal Shaik Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 3 hours
Time Spent: Not Specified
Original Estimate: 3 hours
Environment:

solaries, wso2esb4.8.1


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

HI ,
This is very unusual behavior of wso2 esb.

We are receiving SOAP version errors when we invoking other webservices.

HTTP request headers:
=====================
POST /see/session HTTP/1.1
username: faisal
SOAPAction: ""
Accept-Encoding: gzip,deflate
Content-Type: text/xml
Transfer-Encoding: chunked
Host: *****8:80
Connection: Keep-Alive
User-Agent: Synapse-PT-HttpComponents-NIO

Response HTTP Headers:
=======================
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 550

Error in Wso2esb 4.8.1

2016-08-26 00:22:43 | ERROR | RelayUtils | Error while building Passthrough stream
org.apache.axiom.soap.SOAPProcessingException: Transport level information does not match with SOAP Message namespace URI
at org.apache.axis2.builder.BuilderUtil.validateSOAPVersion(BuilderUtil.java:745)
at org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:58)
at org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:118)
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.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:389)
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:744)
2016-08-26 00:22:43 | INFO | LogMediator | To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:d63f029a-13bc-4639-92c9-96a256f8322a, Direction: response, getSessionDetails-response-body = <soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"/>

SOAP request:
================
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header>

</soapenv:Header><soapenv:Body>
<prov:getSessionRequest xmlns:prov="http://schemas.myname.com/session/sioning">
<prov:queries>
<prov:query reference="Get Session">
<prov:id>
<prov:parameter name="USERNAME" value="**********"/>
</prov:id>
</prov:query>
</prov:queries>
</prov:getSessionRequest>
</soapenv:Body></soapenv:Envelope>

SOAP Response:
===============

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>

<ns2:getSessionResponse xmlns:ns2="http://schemas.myname.com/session/sioning"
xmlns:ns3="http://schemas.myname.com/common">
<ns2:result code="400" message="See details for more information." status="error"/>
<ns2:details>
<ns3:detail code="400" message="Can not find any session where User-Name = *******" status="error"/>
</ns2:details>
</ns2:getSessionResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

we have traced in network, Response is coming from clinet but wso2 not able to read and giving transport error.

Thanks in advance.



 Comments   
Comment by Faisal Shaik [ 30/Aug/16 ]

Any one have updates , Its like show stopper.





[ESBJAVA-4871] Wrong Tenant Domain getting printed when Content-Type Header is sent as null Created: 25/Aug/16  Updated: 25/Aug/16

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

Type: Bug Priority: Highest
Reporter: lakmali Baminiwatta Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

"Error while building message for REST_URL request" error is thrown if REST API requests are sent with empty content-type header.

In APIM 1.10.0, when it starts to print "Error while building message for REST_URL request " for a tenant, it first logs without any tenant domain (It shows as tenant id -1). After sometime only it starts to log the tenant domain. But in some logs it prints the wrong tenant domain correspond to another tenant who has been sending successful requests to the server in the same time.

However, I tested this in ESB 5.0.0, where it seems it doesn't log the tenant domain at all. I tested for sometime, and it always logs it without tenant domain. So it looks like there is a problem with getting the correct tenant set in the relevant synapse level flow in both synapse versions.

TID: [-1] [] [2016-08-19 13:49:35,552] ERROR

{org.apache.synapse.transport.passthru.ServerWorker} - Error while building message for REST_URL request {org.apache.synapse.transport.passthru.ServerWorker}

TID: [-1] [] [2016-08-19 13:49:35,553] ERROR

{org.apache.synapse.transport.passthru.ServerWorker} - Error while building message for REST_URL request {org.apache.synapse.transport.passthru.ServerWorker}

TID: [-1] [] [2016-08-19 13:49:35,741] ERROR

{org.apache.synapse.transport.passthru.ServerWorker} - Error while building message for REST_URL request {org.apache.synapse.transport.passthru.ServerWorker}

This issue makes it difficult to identify for which tenant the error is thrown.






[ESBJAVA-4902] Parsing Json in response Created: 22/Sep/16  Updated: 25/Sep/16

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

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

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

 Description   

When response has content type of "application/json" and body is one of:
true
false
null
"text"

there is an error with JsonUtil like this:
ERROR - JsonUtil #getNewJsonPayload. Could not save JSON payload. Invalid input stream found.
Error Code = 401002
Error Message = Payload is not a JSON string.

and it is treated as failure(but message is delivered, only response can`t be parsed). According to RFC 4627:

A JSON value MUST be an object, array, number, or string, or one of
the following three literal names:

false null true

Source

I think you expect only arrays or objects. It can be easily fixed with wrappers if you can`t deal with these values but don`t throw an error in this case.






[ESBJAVA-4909] ExpandingMessageFormatter Not getting engaged in NHTTP transport Created: 29/Sep/16  Updated: 29/Sep/16

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

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

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

 Description   

When we use binaryRelayBuilder to build multipart/related message, ExpandingMessageFormatter should be invoked to send decoded response back to the client. There seems to be an issue in NHTTP transport that the expanding message formatter not getting invoked in the above scenario.






[ESBJAVA-3361] Inconsistence fault handling for users and tenants Created: 30/Oct/12  Updated: 24/May/16

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

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

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

 Description   

same fault handling synapse configuration behave differently for users and tenant.

attached soap11_fault_code_Server_synapse.xml configuration make different fault messages for receiver. It works fine for users, but tenants It sees not.

Same configuration send fault message for users
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/">soap11Env:Server</faultcode>
<faultstring>Soap11FaultCodeServerTestCase</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

for tenants
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>Connection refused or failed for : localhost/127.0.0.1:9020, IO Exception occured : Connection refused</faultstring>
<detail>Connection refused or failed for : localhost/127.0.0.1:9020, IO Exception occured : Connection refused</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>



 Comments   
Comment by Kasun Indrasiri [ 09/Dec/12 ]

This is not a blocker, hence lowering the priority.





[ESBJAVA-3896] Sample 657 of distributed transaction management is not working properly Created: 13/Jul/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-ALPHA3 - 22.06.2015 pack
Java version : Oracle jdk 1.7.0
DB Version : embedded H2
OS : Ubuntu 14.04 LTS


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

 Description   

Steps to recreate :

1.Create two data sources using management console.
2.Create two derby databases.
3.Insert values into tables as transaction mediator example.(https://docs.wso2.com/display/ESB490/Transaction+Mediator+Example)

4.Since there was no 657 synapse config file, copy the given synapse config to synapse.xml file in ESB_HOME/repository/samples/ location.

5.Invoke the clients as stated in document.

But when we invoke client using commands stated in document, nothing happening to values of database tables as stated.

The successful scenario and failure scenario are not effecting to any of the database table values we have created.






[ESBJAVA-4435] Unable to execute EDI to database insertion with smooks mediator Created: 23/Feb/16  Updated: 09/Jun/16

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

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

OS: Ubuntu 14.04
JDK: 1.8.0


Attachments: XML File Smooks6.xml     File edi.edi     XML File edimapping.xml     XML File smooks_edi_db_config.xml    
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   

Using the given configuration files, and using [1] as the guide line i have tried in executing this using WSO2 ESB, but failed with the following error

[2016-02-23 18:14:50,191] ERROR - SequenceMediator Failed to set paramater configuration value on 'org.milyn.db.DirectDataSource#driver'.
org.milyn.cdr.SmooksConfigurationException: Failed to set paramater configuration value on 'org.milyn.db.DirectDataSource#driver'.
	at org.milyn.cdr.annotation.Configurator.applyConfigParam(Configurator.java:336)
	at org.milyn.cdr.annotation.Configurator.processFieldConfigParamAnnotations(Configurator.java:146)
	at org.milyn.cdr.annotation.Configurator.processFieldConfigAnnotations(Configurator.java:126)
	at org.milyn.cdr.annotation.Configurator.configure(Configurator.java:82)
	at org.milyn.cdr.annotation.Configurator.configure(Configurator.java:66)
	at org.milyn.delivery.JavaContentHandlerFactory.create(JavaContentHandlerFactory.java:69)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$ContentHandlerExtractionStrategy.addCDU(ContentDeliveryConfigBuilder.java:642)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$ContentHandlerExtractionStrategy.applyCDUStrategy(ContentDeliveryConfigBuilder.java:568)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$ContentHandlerExtractionStrategy.applyStrategy(ContentDeliveryConfigBuilder.java:556)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$SmooksResourceConfigurationTableIterator.iterate(ContentDeliveryConfigBuilder.java:730)
	at org.milyn.delivery.ContentDeliveryConfigBuilder$SmooksResourceConfigurationTableIterator.access$300(ContentDeliveryConfigBuilder.java:709)
	at org.milyn.delivery.ContentDeliveryConfigBuilder.extractContentHandlers(ContentDeliveryConfigBuilder.java:494)
	at org.milyn.delivery.ContentDeliveryConfigBuilder.load(ContentDeliveryConfigBuilder.java:356)
	at org.milyn.delivery.ContentDeliveryConfigBuilder.getConfig(ContentDeliveryConfigBuilder.java:147)
	at org.milyn.container.standalone.StandaloneExecutionContext.<init>(StandaloneExecutionContext.java:91)
	at org.milyn.container.standalone.StandaloneExecutionContext.<init>(StandaloneExecutionContext.java:65)
	at org.milyn.Smooks.createExecutionContext(Smooks.java:418)
	at org.milyn.Smooks.createExecutionContext(Smooks.java:376)
	at org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:115)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:86)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:163)
	at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:211)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328)
	at org.apache.synapse.transport.vfs.VFSTransportListener.processFile(VFSTransportListener.java:753)
	at org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:407)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:177)
	at org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:124)
	at org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
	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.milyn.javabean.DataDecodeException: Failed to decode 'com.mysql.jdbc.Driver' as a Java Class.
	at org.milyn.javabean.decoders.ClassDecoder.decode(ClassDecoder.java:36)
	at org.milyn.cdr.annotation.Configurator.applyConfigParam(Configurator.java:334)
	... 33 more
Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:348)
	at org.milyn.util.ClassUtil.forName(ClassUtil.java:95)
	at org.milyn.javabean.decoders.ClassDecoder.decode(ClassDecoder.java:34)
	... 34 more
[2016-02-23 18:14:50,208]  INFO - LogMediator To: , WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:66E5DBEE35D675C51B1456231489841, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Failed to set paramater configuration value on 'org.milyn.db.DirectDataSource#driver'., Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">MLS*Wed Nov 15 13:45:28 EST 2006
HDR*1*0*59.97*64.92*4.95
CUS*user1*Harry^Fletcher*SD
ORD*1*1*364*HarryPorter*28.98
ORD*2*1*299*Pulp Fiction*30.99
HDR*2*0*81.30*91.06*9.76
CUS*user2*George^Hook*SD
ORD*3*2*983*Gone with The Wind*25.80
ORD*4*3*299*Lethal Weapon 2*55.50
</text></soapenv:Body></soapenv:Envelope>

Followed [2] to get the namespaces for smooks 1.5.

[1] https://github.com/smooks/smooks/blob/v1.5.1/smooks-examples/db-extract-transform-load/smooks-configs/datasources.xml
[2] http://www.smooks.org/mediawiki/index.php?title=V1.5:Smooks_v1.5_User_Guide_c6_c11



 Comments   
Comment by Isuru Udana Loku Narangoda [ 08/Jun/16 ]

Can you please explain the issue in detail.

From the error log it seems it fails to find mysql driver.

Comment by Chathurika De Silva [ 08/Jun/16 ]

Hi Isuru

I have the mysql connector in <Product_Home>/repository/components/lib. There is no WSO2 ESB documentation to follow in this as well.
If you have such a sample documented, please be kind enough to point it to me, so I can verify my configs.

Thank You
Erandi





[ESBJAVA-4552] Call mediator does not return the body for 202 response Created: 10/Apr/16  Updated: 08/Jun/16

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

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

OS: Ubuntu 14.04; JDK 1.7.0_51


Attachments: XML File MyMockProxy.xml     XML File test4.xml    
Severity: Major
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0

 Description   

Call mediator (Non blocking) is not sending the response body to the client when the backend sends a 202 response with body. Attached the two proxy services, test4 proxy (In ESB instance with offset 0) is called by the client and MyMockProxy (in ESB instance with offset 1) is the backend which returns 202 with response.

[2016-04-08 10:52:41,048] DEBUG - wire >> "POST /services/test4 HTTP/1.1[\r][\n]"
[2016-04-08 10:52:41,048] DEBUG - wire >> "User-Agent: curl/7.35.0[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Host: localhost:8243[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Content-Type: application/xml[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "Content-Length: 12[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "[\r][\n]"
[2016-04-08 10:52:41,049] DEBUG - wire >> "<x>hello</x>"
[2016-04-08 10:52:41,051]  INFO - LogMediator To: /services/test4, MessageID: urn:uuid:3ab84305-2bda-465d-b60d-2cf13fa54e51, Direction: request
[2016-04-08 10:52:41,054] DEBUG - wire << "POST /services/MyMockProxy HTTP/1.1[\r][\n]"
[2016-04-08 10:52:41,054] DEBUG - wire << "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Host: localhost:8281[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-04-08 10:52:41,055] DEBUG - wire << "[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "c[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "<x>hello</x>[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "0[\r][\n]"
[2016-04-08 10:52:41,056] DEBUG - wire << "[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "HTTP/1.1 202 Accepted[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "Host: localhost:8281[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2016-04-08 10:52:41,058] DEBUG - wire >> "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "Date: Fri, 08 Apr 2016 05:22:41 GMT[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "Transfer-Encoding: chunked[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
[2016-04-08 10:52:41,059] DEBUG - wire >> "[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "10[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "<hello>s</hello>[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "0[\r][\n]"
[2016-04-08 10:52:41,060] DEBUG - wire >> "[\r][\n]"
[2016-04-08 10:52:41,062]  INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:6514f496-88f6-4ca2-bd38-9ad8b22f236f, Direction: request, HTTP_Status = 202, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope>
[2016-04-08 10:52:41,064] DEBUG - wire << "HTTP/1.1 202 Accepted[\r][\n]"
[2016-04-08 10:52:41,064] DEBUG - wire << "Host: localhost:8281[\r][\n]"
[2016-04-08 10:52:41,064] DEBUG - wire << "Content-Type: application/xml; charset=UTF-8; charset=UTF-8[\r][\n]"
[2016-04-08 10:52:41,064] DEBUG - wire << "Accept: application/xml[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "Date: Fri, 08 Apr 2016 05:22:41 GMT[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "0[\r][\n]"
[2016-04-08 10:52:41,065] DEBUG - wire << "[\r][\n]"


 Comments   
Comment by prabath ariyarathna [ 10/Apr/16 ]

According to my observations, This only happens when we have content aware mediators in our sequence. Inside the RelayUtils we are checking status code equal to the 202[1] and ignore build the response body. So we need to verify this behaviour.

[1] https://github.com/wso2/wso2-synapse/blob/Apache-Synapse-2.1.3-wso2v11/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/util/RelayUtils.java#L92-L96





[ESBJAVA-4606] JMS Sender level cache is not working properly with the stale connections. Created: 09/May/16  Updated: 27/Jul/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.9.0, 5.0.0-M1
Fix Version/s: None

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

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

 Description   

JMS Sender level cache is not working properly with the stale connections.
We need to check this for the session and producer cache levels.
We can reproduce this issue easily with setup JMS broker as the backend and send some requests to fill the JMS connection factory. Then need to restart the JMS broker. You can see the failures in the next subsequent requests.



 Comments   
Comment by Jagath Ariyarathne [ 27/Jul/16 ]

This is fixed for connection caching with following PR. Need to do the same for session and producer caching.

https://github.com/wso2/wso2-axis2-transports/commit/1b738f0e2d2d6dd8d7b48fe326c4d517b6346f1b





[ESBJAVA-4392] PassThroughMessageProcessor threads on waiting state Created: 27/Jan/16  Updated: 09/Aug/16

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

Type: Bug Priority: High
Reporter: Vijitha Ekanayake Assignee: Vijitha Ekanayake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Following can be observed in thread dump

"PassThroughMessageProcessor-2" prio=10 tid=0x00007f0204010800 nid=0x91c4 waiting on condition [0x00007f025dedc000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)

  • parking to wait for <0x000000074e72c888> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
    at org.apache.synapse.transport.passthru.Pipe$ByteBufferOutputStream.flushContent(Pipe.java:477)
    at org.apache.synapse.transport.passthru.Pipe$ByteBufferOutputStream.write(Pipe.java:433)
    at com.sun.xml.internal.stream.writers.UTF8OutputStreamWriter.write(UTF8OutputStreamWriter.java:92)
    at com.sun.xml.internal.stream.writers.UTF8OutputStreamWriter.write(UTF8OutputStreamWriter.java:133)
    at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeXMLContent(XMLStreamWriterImpl.java:1486)
    at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeXMLContent(XMLStreamWriterImpl.java:1409)
    at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeCharacters(XMLStreamWriterImpl.java:690)
    at org.apache.axiom.util.stax.wrapper.XMLStreamWriterWrapper.writeCharacters(XMLStreamWriterWrapper.java:100)
    at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeCharacters(MTOMXMLStreamWriter.java:289)
    at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeText(StreamingOMSerializer.java:443)
    at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:173)
    at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:107)
    at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:76)
    at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:547)
    at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:878)
    at org.apache.axiom.om.impl.llom.OMSerializableImpl.serializeAndConsume(OMSerializableImpl.java:193)
    at org.apache.axis2.transport.http.ApplicationXMLFormatter.writeTo(ApplicationXMLFormatter.java:143)
    at org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:511)
    at org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:257)
    at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
    at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:163)
    at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:321)
    at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:94)
    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.rest.Resource.process(Resource.java:313)
    at org.apache.synapse.rest.API.process(API.java:297)
    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:486)
    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:229)
    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 Isuru Udana Loku Narangoda [ 08/Jun/16 ]

Can you please explain the issue bit more ? Description doesn't give any idea of the issue.

Comment by viraj senevirathne [ 03/Aug/16 ]

Reopening due a similar issue in customers issue





[ESBJAVA-3837] RequestSecurityTokenTemplate from IssuedToken policy isn't used Created: 22/Jun/15  Updated: 06/Aug/16

Status: Open
Project: WSO2 ESB
Component/s: Core Engine, Registry
Affects Version/s: 4.8.1
Fix Version/s: None

Type: Bug Priority: High
Reporter: Alexey Smirnov Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB, IS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RedHat Linux


Attachments: File STS.rar     XML File STSPolicy.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

We use STS in WSO2 IS to secure echo service on WSO2ESB. We use non-secure NewTestSTS proxy (attached in archive STS.rar) to access this secured service. STSPolicy.xml (attached) is used to secure echo service. It's stored in configuration registry (or can be stored in governance registry).
First attempt of service call works fine, STS is being got from WSO2IS and is sent to echo service. But all the following attempts end with error "Requested KeyType is missing" on the IS side.
In debug log of ESB we see this message:
[2015-06-22 17:02:12,051] DEBUG - Using RSTTemplate: <spn:RequestSecurityTokenTemplate xmlns:spn="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:t="http://schemas.xmlsoap.org/ws/2005/02/trust">

</spn:RequestSecurityTokenTemplate>

{org.apache.rahas.client.STSClient}

After re-saving of policy, service call can be performed again






[ESBJAVA-3719] Issue in STSClient while requesting token from MS ADFS Created: 27/May/15  Updated: 06/Aug/16

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

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

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

 Description   

Hi,
We have started to WSO2 ESB project in our company.
We are implementing security part of the project.
Our backend services require SAML authentication through Microsoft ADFS.
Currently, we use WSO2 ESB 4.8.1, rampart-1.6.2 and addressing-1.6.2 modules and ADFS 2.0.
While requesting token from ADFS, I'm getting below exception on ESB:

ERROR - STSClient errorInObtainingToken
org.apache.axis2.AxisFault: The input stream for an incoming message is null.
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:93)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:68)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:348)
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.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:165)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:182)
at org.apache.rampart.util.RampartUtil.getToken(RampartUtil.java:766)
at org.apache.rampart.util.RampartUtil.getIssuedToken(RampartUtil.java:675)
at org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:379)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:420)
at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
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.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)
[2015-04-10 10:41:38,607] ERROR - Axis2Sender Unexpected error during sending message out org.apache.axis2.AxisFault: Error in obtaining a token
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:76)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:426)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:97)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
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.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: org.apache.rampart.RampartException: Error in obtaining a token
at org.apache.rampart.util.RampartUtil.getToken(RampartUtil.java:779)
at org.apache.rampart.util.RampartUtil.getIssuedToken(RampartUtil.java:675)
at org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:379)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:420)
at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:97)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
... 24 more
Caused by: org.apache.rahas.TrustException: Error in obtaining token from : "https://XXXX:443/adfs/services/trust/13/usernamemixed"
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:174)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:182)
at org.apache.rampart.util.RampartUtil.getToken(RampartUtil.java:766)
... 30 more
Caused by: org.apache.axis2.AxisFault: The input stream for an incoming message is null.
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:93)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:68)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:348)
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.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
at org.apache.rahas.client.STSClient.requestSecurityToken(STSClient.java:165)
-----------------------------------------------------------------------------------------------------

When I investigated I noticed that WS-Addressing and WS-Trust namespaces at the token request prepared by apache rampart are different than expectation of ADFS.

The addressing module (addressing-1.6.2) supports the WS-Addressing Submission version (2004/08).
The apache rampart module(rampart-1.6.2) supports WS-Trust version 1.2.
ADFS has 2 kinds of endpoint; version 1.3 and version 2005.
I have tried both of them as endpoint while requesting SAML token from ADFS.
Although the ADFS endpoint with version 2005 supports WS-Trust version 1.2, still needed to change WS-Addressing namespace as "Final".

When I change below items in apache rampart, I'm able to obtain a token from ADFS..

  • Version of WS-Trust from 1.2 to 1.3
  • WS-Addressing namespace from Submission to Final

Is it a known bug?
Are there a version of apache rampart/rahas which is compatible with MS ADFS?
Thanks a lot.



 Comments   
Comment by Asela Pathberiya [ 21/Sep/15 ]

Hi Dilfuruz,

Rampart/Rahas supports up to WS-Trust 1.4 as STS (Security Token Service).

But; STSClient (just client side implementation which can use to generate RST and validates them) of the rahas is only supported to generate RST which is compatible with WS-Trust 1.2 version. It does not support for 1.3/1.4. Therefore it is addressing header is set for submission version.

According to the WS-Trust 1.2 specification, It must be the submission version

 wsa  : http://schemas.xmlsoap.org/ws/2004/08/addressing 

Therefore we do not see any bug in this. So; Please correct us, if we have missed something.

Yes. We agree that it is better to update the STS client RST version to 1.3 and addressing version to Final. We can do this improvement for future release. If you like to contribute, it is highly appreciated. Please attach the source diff in to this ticket. Then team can verify and fix it for future release.

[1] http://specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf

Thanks,
Asela.





[ESBJAVA-3688] Clean up Enrich Mediator Created: 08/May/15  Updated: 24/May/16

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

Type: Improvement Priority: High
Reporter: Srinath Perera Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

I think we can get rid of most of the redundant attributes and support them through xpath only. For instance most of the operations that you do with enrich can be done using xpath attribute in both source and target. So, we will fully verify and fix these use cases while keeping support for existing syntax for backward compatibility.

<!--payload to property -->
<enrich>
<source xpath="//m0:getQuote/m0:request/m0:symbol/text()"
xmlns:m0="http://services.samples"/>
<target xpath="$ctx:PropName"/>
</enrich>

<!-- property to payload -->
<enrich>
<source xpath="$ctx:PropName"
xmlns:m0="http://services.samples"/>
<target xpath="//m0:Foo/"/>
</enrich>

See the thread "ESB Feedback: Improve Payload Factory and Improving Enrich" at arch@ for more info/






[ESBJAVA-2914] wso2ESB 4.8.0 not working for transactions Created: 16/Jan/14  Updated: 24/May/16

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.8.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: faisal shaik Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu,wso2dss3.0.1 ,wso2esb4.8.0


Attachments: File Transaction.dbs     XML File TransactionProxy.xml     PNG File ibx4q.png    
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
Affects Docs:
Yes

 Description   

Hi
I am using wso2esb4.8.0 and wso2dss3.0.1.My issue is i wish to insert the data into 2 tables its working nicely but i wish to applay transaction for my tables both table exist in same DB.If my 2nd table going fail on any moment that time my 1 st table should be rollback for that my DSS data source configuration is
and my dataservice is like this and i enabled boxcar for transaction

<data disableStreaming="true" enableBoxcarring="true" name="Transaction" serviceNamespace="http://ws.wso2.org/dataservice">
<config id="default">
<property name="carbon_datasource_name">USCProduction</property>
</config>
<query id="insertinto_mclient" useConfig="default">
<sql>insert into mclient(clientcode,clientname,createdbyid,modifiedbyid) values(?,?,?,?)</sql>
<param name="clientcode" ordinal="1" sqlType="STRING"/>
<param name="clientname" ordinal="2" sqlType="STRING"/>
<param name="createdbyid" ordinal="3" sqlType="BIGINT"/>
<param name="modifiedbyid" ordinal="4" sqlType="BIGINT"/>
</query>
<query id="insertinto_mcompany" useConfig="default">
<sql>insert into mcompany(companycode,companyname,createdbyid,modifiedbyid,clientid) values(?,?,?,?,?)</sql>
<param name="companycode" ordinal="1" sqlType="STRING"/>
<param name="comapnyname" ordinal="2" sqlType="STRING"/>
<param name="createdbyid" ordinal="3" sqlType="BIGINT"/>
<param name="modifiedbyid" ordinal="4" sqlType="BIGINT"/>
<param name="clientid" ordinal="5" sqlType="BIGINT"/>
</query>
<operation disableStreaming="true" name="insertinto_mclient_OP" returnRequestStatus="true">
<call-query href="insertinto_mclient">
<with-param name="clientcode" query-param="clientcode"/>
<with-param name="clientname" query-param="clientname"/>
<with-param name="createdbyid" query-param="createdbyid"/>
<with-param name="modifiedbyid" query-param="modifiedbyid"/>
</call-query>
</operation>
<operation disableStreaming="true" name="insertinto_mcompany_OP" returnRequestStatus="true">
<call-query href="insertinto_mcompany">
<with-param name="companycode" query-param="companycode"/>
<with-param name="comapnyname" query-param="comapnyname"/>
<with-param name="createdbyid" query-param="createdbyid"/>
<with-param name="modifiedbyid" query-param="modifiedbyid"/>
<with-param name="clientid" query-param="clientid"/>
</call-query>
</operation>
</data>
and my proxy service is
<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="TransactionProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log level="full">
<property name="M1" value="************HITTING Transaction PROXY************"/>
</log>
<property name="OUT_ONLY" value="true"/>
<property name="companycode" expression="//companycode/text()"/>
<property name="companyname" expression="//companyname/text()"/>
<property name="clientcode" expression="//clientcode/text()"/>
<property name="clientname" expression="//clientname/text()"/>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body/>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="full">
<property name="M2" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:begin_boxcar"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/begin_boxcar"
action="urn:begin_boxcar">
<source type="envelope"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<payloadFactory media-type="xml">
<format>
<p:insertinto_mclient_OP xmlns="http://ws.wso2.org/dataservice">
<xs:clientcode xmlns:xs="http://ws.wso2.org/dataservice">$1</xs:clientcode>
<xs:clientname xmlns:xs="http://ws.wso2.org/dataservice">$2</xs:clientname>
<xs:createdbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:createdbyid>
<xs:modifiedbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:modifiedbyid>
</p:insertinto_mclient_OP>
</format>
<args>
<arg evaluator="xml" expression="get-property('clientcode')"/>
<arg evaluator="xml" expression="get-property('clientname')"/>
</args>
</payloadFactory>
<header name="Action" value="urn:insertinto_mclient_OP"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/"
action="urn:insertinto_mclient_OP">
<source xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<payloadFactory media-type="xml">
<format>
<p:insertinto_mcompany_OP xmlns="http://ws.wso2.org/dataservice">
<xs:companycode xmlns:xs="http://ws.wso2.org/dataservice">$1</xs:companycode>
<xs:comapnyname xmlns:xs="http://ws.wso2.org/dataservice">$2</xs:comapnyname>
<xs:createdbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:createdbyid>
<xs:modifiedbyid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:modifiedbyid>
<xs:clientid xmlns:xs="http://ws.wso2.org/dataservice">-1</xs:clientid>
</p:insertinto_mcompany_OP>
</format>
<args>
<arg evaluator="xml" expression="get-property('companycode')"/>
<arg evaluator="xml" expression="get-property('companyname')"/>
</args>
</payloadFactory>
<log level="full">
<property name="M5" value="*************hitting2nd dss****"/>
</log>
<header name="Action" value="urn:insertinto_mcompany_OP"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/"
action="urn:insertinto_mcompany_OP">
<source xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body/>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="full">
<property name="M3" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:end_boxcar"/>
<callout serviceURL="http://192.168.1.201:9764/services/Transaction/end_boxcar"
action="urn:end_boxcar">
<source type="envelope"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<log level="full">
<property name="M4" value="************HITTING Transaction PROXY************"/>
</log>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<description/>
</proxy>
box_carying is working in wso2dss but not in wso2esb is there any session management is there
i started with begin_boxcar and end with end_boxcar.BUt while i am doing this with dss if i start with begin_boxcar then 1st insert after that i checked the table but ther is no data insertion if i insert into 2nd table and end with end_boxcar then only data inserting into 2 tables.Where as i checked with proxy service configuration like above strted with begin_boxcar and inserted 1st table and checked the table dat is there means with out end_boxcar also data inserted properly
and
how can i get DSS session into proxy.what is this JSESSIONID



 Comments   
Comment by faisal shaik [ 17/Jan/14 ]

how to get the boxcarying session id in to proxy?

Comment by faisal shaik [ 20/Jan/14 ]

wso2esb support for transactions are not.

<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body/>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="full">
<property name="M2" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:begin_boxcar"/>
<property name="setCookieHeader"
expression="$trp:Set-Cookie"
scope="default"
type="STRING"/>
<callout serviceURL="http://1localhost:9764/services/Transaction/begin_boxcar"
action="urn:begin_boxcar">
<source type="envelope"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::[fn:position()=1] | s12:Body/child::[fn:position()=1]"/>
</callout>
<property name="setCookieHeader5" expression="$trp:JSESSIONID"/>
<log level="full">
<property name="JSession" expression="get-property('setCookieHeader')"/>
</log>

how to get dss JSESSIONID in to wso2esb proxy





[ESBJAVA-4283] wso2esb is unable to create xa datasource for postgressql Created: 22/Jan/14  Updated: 24/May/16

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

Type: Bug Priority: High
Reporter: faisal shaik Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu,wso2esb4.8.0


Attachments: XML File master-datasources.xml    
Severity: Critical
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0
Test cases added: Yes
Affects Docs:
Yes

 Description   

Hi
I am working with wso2esb 4.8.0 and postgressql9.1
I wish to do a simple transaction based insert in wso2esb .If we want to do a transaction need to use xa data source but wso2esb and dss default using non xa data source.So i created a xa data source but its showing errors even i tried wso2dss box carring but no result we are unable maintain a same JSESSONID in to proxy so now i am trying with DBLOOKUP and DB REPORT for that i am trying create xa datasource using below
configuration in repository/config/master-datasource.xmll
<datasource>
<name>DS2</name>
<jndiConfig>
<name>DS2</name>
</jndiConfig>
<definition type="RDBMS">
<configuration>
<dataSourceClassName>com.atomikos.jdbc.AtomikosDataSourceBean</dataSourceClassName>
<dataSourceProps>
<property name="xaDataSourceClassName">org.postgresql.xa.PGXADataSource</property>
<property name="uniqueResourceName">TXUSCProduction</property>
<property name="xaProperties.user">youtilitydba</property>
<property name="xaProperties.password">Youtility11</property>
<property name="xaProperties.URL">jdbc:postgresql://localhost:5432/USCProduction</property>
<property name="poolSize">10</property>
</dataSourceProps>
</configuration>
</definition>
</datasource>
its creating and showing in UI also when i am trying with DBREPORT giving pool errors are AtomikosDataSourceBean errors
really fed up with wso2 no proper docs are no proper example even no reply for any question



 Comments   
Comment by faisal shaik [ 20/Feb/14 ]

is it bug in wso2.

Comment by dushan abeyruwan [ 27/Jun/14 ]

This should be a bug related to carbon components.





[ESBJAVA-2867] Inconsistency in filter mediator Created: 06/Jan/14  Updated: 09/Jul/15

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

Type: Bug Priority: High
Reporter: Chandana Napagoda Assignee: Jagath Ariyarathne
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.xml    
Severity: Critical
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Filter mediator shows an inconsistent behavior after messages passed via message store processor. Please refer below synapse config. With out store processor it prints below log[1] and with store processor it prints log[2]

[1]. RESULT = Found a SOAP fault, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</faultcode><faultstring>java.io.IOException Message being parsed: </faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>

[2]. RESULT = All is well, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</faultcode><faultstring>java.io.IOException Message being parsed: </faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>



 Comments   
Comment by Kasun Indrasiri [ 23/Jan/14 ]

Lowering the priority as this is not a L1.





[ESBJAVA-2753] [EntitlementMediator] Once did some change in esb side, it took nearly 15min to update and execute the correct result for a XACML policy Created: 26/Nov/13  Updated: 25/Jul/15

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

Type: Improvement Priority: High
Reporter: Suneth Ranasinghe Assignee: madhuranga bandara
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

I have changed the XACML policy (role) and try to invoke the given service which should not be permitted for the given user. But its allowing the user to access the service for nearly like 15mins.






[ESBJAVA-2441] Unable to enable custom module in proxy configuration Created: 10/Sep/13  Updated: 20/Jul/15

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.5.1, 4.6.0, 4.7.0
Fix Version/s: None

Type: Improvement Priority: High
Reporter: Thijs Volders Assignee: Isuru Udana Loku Narangoda
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

The synapse proxy configuration does not allow to specify which custom modules should be engaged upon deployment.

This introduces several challenges:
1) One cannot change the synapse configuration or a deploy a proxy service through the filesystem without manually engaging the module on the proxy through the admin-console.
2) When a CAR (with proxy service) is (re-)deployed manual actions are necessary through the console to engage the module on the proxy(ies).
3) When Carbon decides to undeploy a service and redeploy it later then the engaged module is no longer engaged thus messages are no longer properly processed. Again manual engagement is necessary.

This latter issue is rather problematic as I have seen situations where Carbon decided to undeploy the proxy under high load en redeploy it moments later. Unfortunately the module was gone after this redeployment thus causing invalid messages to go through as the module did not stop them...






[ESBJAVA-2467] [MSMP] Add JMS Message Store Username / Passwords Plain text ? Created: 20/Sep/13  Updated: 09/Jul/15  Due: 20/Sep/13

Status: Open
Project: WSO2 ESB
Component/s: Message Stores
Affects Version/s: 4.8.0 M2
Fix Version/s: None

Type: Improvement Priority: High
Reporter: dushan abeyruwan Assignee: shafreen anfar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

need expressions thus we can use mediation security component to secure passwords






[ESBJAVA-4848] Unable to remotely deploy CApps from Dev Studio due to CSRF Guard Created: 16/Aug/16  Updated: 18/Aug/16

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

Type: Bug Priority: High
Reporter: Joseph Fonseka Assignee: Dulanja Liyanage
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Hi

I created a CApp with a esb config containing a simple proxy server. then I added ESB as a remote server and tried to deploy the CApp using maven deploy plugin.

CApp deployment fails with WSB printing a warning informing about a CSRF attack. IMO This is a generic problem with the OWASP CSRF Guard filter which will prevent any service calls made with 3rd party apps.

Possible suggestions use double submit cookies which will only apply CSRF for browser based requests.

Thanks
Jo

Ps. Following is the warning.
WARN - JavaLogger potential cross-site request forgery (CSRF) attack thwarted (user:<anonymous>, ip:127.0.0.1, method:POST, uri://services/CarbonAppUploader, error:required token is missing from the request)



 Comments   
Comment by Dulanja Liyanage [ 18/Aug/16 ]

Hi Jo,

Could you please check whether following entry is there in Owasp.CsrfGuard.Carbon.properties?

org.owasp.csrfguard.unprotected.Services=%servletContext%/services/*

Thanks,
Dulanja





[ESBJAVA-4843] ESB build the message as text/plain when the jms header content-type in not there in the incoming JMS message Created: 11/Aug/16  Updated: 11/Aug/16

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

Type: Task Priority: High
Reporter: Randika Perera Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

ESB build the message as text/plain when the jms header content-type in not there in the incoming JMS message. There is no configuration to select the particular builder at the moment. We encountered this scenario in JMS dual channel when the third party application publish messages to the reply queue without the content type header.






[ESBJAVA-4834] Error with a large script in script mediator when processing large payloads Created: 08/Aug/16  Updated: 13/Aug/16

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

Type: Bug Priority: High
Reporter: Vinuri Perera Assignee: Nuwan Wimalasekara
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tested in the 5.0.0 Beta pack


Attachments: XML File SendOutSequence3Changed.xml     XML File sendSequence.xml     XML File testApi.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Backend response which has 93509 lines ( 3.3MB ) and with a large script mediator file. Script will go through all the lines in the response and modify the payload(Script mediator contain few parseInt which converts the string values to integer). After modifying it will use the SetPayloadJson[1] to set the payload. when trying to set the payload it give the bellow error[2].

Please note this worked with a small script mediator which only contain one parseInt function but failed for the large script file.

[1]
mc.setPayloadJSON(payLoad.testOutParams);

[2]
==================Error Log =========================
ERROR

{org.apache.synapse.mediators.bsf.ScriptMediator} - The script engine returned an error executing the inlined js script function mediate {org.apache.synapse.mediators.bsf.ScriptMediator}

com.sun.phobos.script.util.ExtendedScriptException: org.mozilla.javascript.WrappedException: Wrapped java.lang.IllegalArgumentException: out of range index (<Unknown Source>#43) in <Unknown Source> at line number 43
at com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:68)
at javax.script.CompiledScript.eval(CompiledScript.java:92)
at org.apache.synapse.mediators.bsf.ScriptMediator.mediateForInlineScript(ScriptMediator.java:333)
at org.apache.synapse.mediators.bsf.ScriptMediator.invokeScript(ScriptMediator.java:265)
at org.apache.synapse.mediators.bsf.ScriptMediator.mediate(ScriptMediator.java:233)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:95)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:57)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at org.apache.synapse.rest.Resource.process(Resource.java:338)
at org.apache.synapse.rest.API.process(API.java:338)
at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:125)
at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101)
at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:56)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:300)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
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:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.mozilla.javascript.WrappedException: Wrapped java.lang.IllegalArgumentException: out of range index (<Unknown Source>#43)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at org.mozilla.javascript.gen.Unknown_Source_38._c_script_0(<Unknown Source>:43)
at org.mozilla.javascript.gen.Unknown_Source_38.call(<Unknown Source>)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at org.mozilla.javascript.gen.Unknown_Source_38.call(<Unknown Source>)
at org.mozilla.javascript.gen.Unknown_Source_38.exec(<Unknown Source>)
at com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:55)
... 21 more
Caused by: java.lang.IllegalArgumentException: out of range index
at org.mozilla.classfile.ClassFileWriter.add(ClassFileWriter.java:579)
at org.mozilla.classfile.ClassFileWriter.addLoadConstant(ClassFileWriter.java:647)
at org.mozilla.classfile.ClassFileWriter.addPush(ClassFileWriter.java:884)
at org.mozilla.javascript.optimizer.Codegen.emitConstantDudeInitializers(Codegen.java:1038)
at org.mozilla.javascript.optimizer.Codegen.generateCode(Codegen.java:321)
at org.mozilla.javascript.optimizer.Codegen.compileToClassFile(Codegen.java:166)
at org.mozilla.javascript.optimizer.Codegen.compile(Codegen.java:75)
at org.mozilla.javascript.Context.compileImpl(Context.java:2377)
at org.mozilla.javascript.Context.compileReader(Context.java:1296)
at org.mozilla.javascript.Context.compileReader(Context.java:1268)
at org.mozilla.javascript.Context.evaluateReader(Context.java:1107)
at com.sun.phobos.script.javascript.RhinoScriptEngine.eval(RhinoScriptEngine.java:172)
at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:249)
at org.apache.synapse.mediators.bsf.ScriptMessageContext.setPayloadJSON(ScriptMessageContext.java:724)
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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 30 more
TID: [-1234] [] [2016-08-04 19:25:36,964] ERROR

{API_LOGGER.testApi} - The script engine returned an error executing the inlined js script function mediate {API_LOGGER.testApi}

com.sun.phobos.script.util.ExtendedScriptException: org.mozilla.javascript.WrappedException: Wrapped java.lang.IllegalArgumentException: out of range index (<Unknown Source>#43) in <Unknown Source> at line number 43
at com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:68)
at javax.script.CompiledScript.eval(CompiledScript.java:92)
at org.apache.synapse.mediators.bsf.ScriptMediator.mediateForInlineScript(ScriptMediator.java:333)
at org.apache.synapse.mediators.bsf.ScriptMediator.invokeScript(ScriptMediator.java:265)
at org.apache.synapse.mediators.bsf.ScriptMediator.mediate(ScriptMediator.java:233)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:95)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:57)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at org.apache.synapse.rest.Resource.process(Resource.java:338)
at org.apache.synapse.rest.API.process(API.java:338)
at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:125)
at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101)
at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:56)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:300)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
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:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.mozilla.javascript.WrappedException: Wrapped java.lang.IllegalArgumentException: out of range index (<Unknown Source>#43)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at org.mozilla.javascript.gen.Unknown_Source_38._c_script_0(<Unknown Source>:43)
at org.mozilla.javascript.gen.Unknown_Source_38.call(<Unknown Source>)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at org.mozilla.javascript.gen.Unknown_Source_38.call(<Unknown Source>)
at org.mozilla.javascript.gen.Unknown_Source_38.exec(<Unknown Source>)
at com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:55)
... 21 more
Caused by: java.lang.IllegalArgumentException: out of range index
at org.mozilla.classfile.ClassFileWriter.add(ClassFileWriter.java:579)
at org.mozilla.classfile.ClassFileWriter.addLoadConstant(ClassFileWriter.java:647)
at org.mozilla.classfile.ClassFileWriter.addPush(ClassFileWriter.java:884)
at org.mozilla.javascript.optimizer.Codegen.emitConstantDudeInitializers(Codegen.java:1038)
at org.mozilla.javascript.optimizer.Codegen.generateCode(Codegen.java:321)
at org.mozilla.javascript.optimizer.Codegen.compileToClassFile(Codegen.java:166)
at org.mozilla.javascript.optimizer.Codegen.compile(Codegen.java:75)
at org.mozilla.javascript.Context.compileImpl(Context.java:2377)
at org.mozilla.javascript.Context.compileReader(Context.java:1296)
at org.mozilla.javascript.Context.compileReader(Context.java:1268)
at org.mozilla.javascript.Context.evaluateReader(Context.java:1107)
at com.sun.phobos.script.javascript.RhinoScriptEngine.eval(RhinoScriptEngine.java:172)
at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:249)
at org.apache.synapse.mediators.bsf.ScriptMessageContext.setPayloadJSON(ScriptMessageContext.java:724)
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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 30 more



 Comments   
Comment by Vinuri Perera [ 08/Aug/16 ]

Added the API Which used for testing and the Payload





[ESBJAVA-4844] Kerberos implementaion to secure Rest Proxies Created: 12/Aug/16  Updated: 12/Aug/16

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

Type: New Feature Priority: High
Reporter: Iranga Muthuthanthri Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Support Kerberos implementation to secure Rest Proxies.






[ESBJAVA-4837] [VFS] NPE when sending message out Created: 10/Aug/16  Updated: 10/Aug/16

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

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

Ubuntu 14.04, JDK1.8, mysql5.5.50, OpenSSH ftp server


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

 Description   

Steps to Recreate:
1. Enable VFdS transport in axis2.xml
2. Add a proxy service[1] in which vfs transport enabled.
3. Keep it running for couple of hours.(this depends; first time, noticed after like 2 hours and next time it was after like 8 hours from the start)
[1]

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="StockQuoteProxy"
       transports="vfs"
       statistics="enable"
       trace="disable"
       startOnLoad="true">
   <target>
      <outSequence>
         <property name="transport.vfs.ReplyFileName"
                   expression="fn:concat(fn:substring-after(get-property('MessageID'), 'urn:uuid:'), '.xml')"
                   scope="transport"/>
         <property name="OUT_ONLY" value="true"/>
         <property name="ClientApiNonBlocking"
                   value="true"
                   scope="axis2"
                   action="remove"/>
         <send>
            <endpoint>
               <address uri="vfs:file:///home/chaminda/Documents/Testing/ESB/5.0.0/vfs/out"/>
            </endpoint>
         </send>
      </outSequence>
      <endpoint>
         <address uri="http://localhost:9000/services/SimpleStockQuoteService"
                  format="soap12"/>
      </endpoint>
   </target>
   <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
   <parameter name="transport.PollInterval">15</parameter>
   <parameter name="transport.vfs.FileSizeLimit">399</parameter>
   <parameter name="transport.vfs.FileURI">sftp://smbuser:*****@10.100.x.xx/home/chaminda/Documents/Testing/ESB/5.0.0/vfs/original</parameter>
   <parameter name="transport.vfs.ContentType">text/xml</parameter>
   <parameter name="transport.vfs.ActionAfterProcess">NONE</parameter>
   <parameter name="transport.vfs.MoveAfterFailure">file:///home/chaminda/Documents/Testing/ESB/5.0.0/vfs/fail</parameter>
   <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
   <parameter name="transport.vfs.ClusterAware">false</parameter>
   <parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter>
   <parameter name="transport.vfs.MoveAfterProcess">file:///home/chaminda/Documents/Testing/ESB/5.0.0/vfs/original</parameter>
   <description/>
</proxy>

[2]

[2016-08-10 05:53:48,876] ERROR - Axis2Sender Unexpected error during sending message out
java.lang.NullPointerException
	at org.apache.synapse.transport.vfs.VFSTransportSender.writeFile(VFSTransportSender.java:335)
	at org.apache.synapse.transport.vfs.VFSTransportSender.sendMessage(VFSTransportSender.java:194)
	at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:581)
	at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:78)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:512)
	at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:382)
	at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
	at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:121)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:337)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261)
	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-08-10 05:53:48,888]  WARN - EndpointContext Endpoint : AnonymousEndpoint with address vfs:file:///home/chaminda/Documents/Testing/ESB/5.0.0/vfs/out will be marked SUSPENDED as it failed
[2016-08-10 05:53:48,889]  WARN - EndpointContext Suspending endpoint : AnonymousEndpoint with address vfs:file:///home/chaminda/Documents/Testing/ESB/5.0.0/vfs/out - current suspend duration is : 30000ms - Next retry after : Wed Aug 10 05:54:18 IST 2016
[2016-08-10 05:53:48,889]  INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:7b4cc39f-1cf4-42f4-9822-a470412a5eb3, Direction: response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Unexpected error during sending message out, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns:getQuoteResponse xmlns:ns="http://services.samples"><ns:return xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax21:GetQuoteResponse"><ax21:change>-2.645794876268378</ax21:change><ax21:earnings>13.257597618613044</ax21:earnings><ax21:high>-96.89377869565995</ax21:high><ax21:last>98.4280480204015</ax21:last><ax21:lastTradeTimestamp>Wed Aug 10 05:53:48 IST 2016</ax21:lastTradeTimestamp><ax21:low>103.17276510667655</ax21:low><ax21:marketCap>-7922672.550319873</ax21:marketCap><ax21:name>IBM Company</ax21:name><ax21:open>102.69918128860253</ax21:open><ax21:peRatio>23.01709919105754</ax21:peRatio><ax21:percentageChange>2.699629403019614</ax21:percentageChange><ax21:prevClose>-98.00585492619761</ax21:prevClose><ax21:symbol>IBM</ax21:symbol><ax21:volume>19456</ax21:volume></ns:return></ns:getQuoteResponse></soapenv:Body></soapenv:Envelope>


 Comments   
Comment by Chaminda Jayawardena [ 10/Aug/16 ]

Also tried with a remote ftp server and it's giving below exception after a moment. In this case endpoint also pointed to a ftp location other than file system.

            <endpoint>
               <address uri="vfs:sftp://ftpuser:ftpuser@192.168.70.xx/home/ubuntu/vfs/out"/>
            </endpoint>
[2016-08-10 12:08:04,767] ERROR - VFSTransportSender Couldn't send the message to file : sftp://ftpuser":***@"192.168.70.135/home/ubuntu/vfs/out/dc1c7739-c119-48a3-9400-d77f65c9c7da.xml, unable to acquire the lock even after 4 retries
[2016-08-10 12:08:04,772] ERROR - Axis2Sender Unexpected error during sending message out
org.apache.axis2.AxisFault: Couldn't send the message to file : sftp://ftpuser":***@"192.168.70.135/home/ubuntu/vfs/out/dc1c7739-c119-48a3-9400-d77f65c9c7da.xml, unable to acquire the lock even after 4 retries
	at org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:231)
	at org.apache.synapse.transport.vfs.VFSTransportSender.acquireLockForSending(VFSTransportSender.java:418)
	at org.apache.synapse.transport.vfs.VFSTransportSender.writeFile(VFSTransportSender.java:284)
	at org.apache.synapse.transport.vfs.VFSTransportSender.sendMessage(VFSTransportSender.java:194)
	at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:581)
	at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:78)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:512)
	at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:382)
	at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65)
	at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:121)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:337)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261)
	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-08-10 12:08:04,779]  WARN - EndpointContext Endpoint : AnonymousEndpoint with address vfs:sftp://ftpuser":***@"192.168.70.135/home/ubuntu/vfs/out will be marked SUSPENDED as it failed
[2016-08-10 12:08:04,779]  WARN - EndpointContext Suspending endpoint : AnonymousEndpoint with address vfs:sftp://ftpuser":***@"192.168.70.135/home/ubuntu/vfs/out - last suspend duration was : 30000ms and current suspend duration is : 30000ms - Next retry after : Wed Aug 10 12:08:34 IST 2016
[2016-08-10 12:08:04,780]  INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:dc1c7739-c119-48a3-9400-d77f65c9c7da, Direction: response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Unexpected error during sending message out, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns:getQuoteResponse xmlns:ns="http://services.samples"><ns:return xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax21:GetQuoteResponse"><ax21:change>-2.607164377663238</ax21:change><ax21:earnings>12.205210456190672</ax21:earnings><ax21:high>-80.26120885057587</ax21:high><ax21:last>81.14232231234595</ax21:last><ax21:lastTradeTimestamp>Wed Aug 10 12:06:34 IST 2016</ax21:lastTradeTimestamp><ax21:low>-79.99857130651138</ax21:low><ax21:marketCap>1.363738586590527E7</ax21:marketCap><ax21:name>IBM Company</ax21:name><ax21:open>-80.99985852980087</ax21:open><ax21:peRatio>25.559094022968516</ax21:peRatio><ax21:percentageChange>-2.9201029882484035</ax21:percentageChange><ax21:prevClose>89.28330227240106</ax21:prevClose><ax21:symbol>IBM</ax21:symbol><ax21:volume>5323</ax21:volume></ns:return></ns:getQuoteResponse></soapenv:Body></soapenv:Envelope>
[2016-08-10 12:08:04,817]  INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:61f81e9d-9654-498d-af09-3df3ada63211, Direction: response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 303001, ERROR_MESSAGE = Currently , Address endpoint : [ Name : AnonymousEndpoint ] [ State : SUSPENDED ], Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns:getQuoteResponse xmlns:ns="http://services.samples"><ns:return xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax21:GetQuoteResponse"><ax21:change>-2.720141663723826</ax21:change><ax21:earnings>13.787077868995912</ax21:earnings><ax21:high>-95.92642108811141</ax21:high><ax21:last>98.16009247148352</ax21:last><ax21:lastTradeTimestamp>Wed Aug 10 12:08:04 IST 2016</ax21:lastTradeTimestamp><ax21:low>100.95097308171991</ax21:low><ax21:marketCap>5.791502634167565E7</ax21:marketCap><ax21:name>IBM Company</ax21:name><ax21:open>-96.47074302245997</ax21:open><ax21:peRatio>-17.090050740196098</ax21:peRatio><ax21:percentageChange>2.969300959839346</ax21:percentageChange><ax21:prevClose>
Comment by Chanaka Fernando [ 10/Aug/16 ]

The initial NPE is harmless since it occurs after the files are processed and when the TransportSender is trying to close the file system. But the problem with the existing code is that, this NPE is throwing an AxisFault and hence suspending the endpoint. This can cause message losses. To handle this, we have captured the exception and print a warn log to the user. This fix is included in [1].

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

Comment by Chanaka Fernando [ 10/Aug/16 ]

File locking issue is not harmful in terms of message exchange. Can you try with disabling the File locking parameter?

<parameter name="transport.vfs.Locking">disable</parameter>





[ESBJAVA-4836] Rampart exception when response from secured backend service returns HTTP 500 Created: 09/Aug/16  Updated: 13/Sep/16

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

Type: Bug Priority: High
Reporter: undefined undefined Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB, rampart
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File FaceDigitalSignature.xml     XML File Face_PS.xml     XML File FacturaSSPP2.xml    
Severity: Blocker
Estimated Complexity: Moderate
Test cases added: No

 Description   

When trying a security scenario (like scenario number 100) in which the backend service is secured by signing the body, but we want the client not to use security, if the backend service returns an HTTP 500 without any soap message, the Rampart produces an exception, that don't returns the process neither to out-sequence nor the fault-sequence, so the client is waiting the response until time-out is produced.

Stack-trace

[2016-08-09 12:00:17,486] ERROR - AxisEngine Missing wsse:Security header in request
org.apache.axis2.AxisFault: Missing wsse:Security header in request
at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
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.rampart.RampartException: Missing wsse:Security header in request
at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 9 more
[2016-08-09 12:00:17,488] ERROR - ClientWorker Fault processing response message through Axis2
org.apache.axis2.AxisFault: Missing wsse:Security header in request
at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
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.rampart.RampartException: Missing wsse:Security header in request
at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 9 more



 Comments   
Comment by Chanaka Fernando [ 09/Aug/16 ]

Did you define the fault handler in your synapse configuration? If possible, please attach the synapse configuration which you have tried.

Comment by undefined undefined [ 09/Aug/16 ]

Attached proxy-service, endpoint and policy configurations.

I also have a PasswordCallback to get the key password. The message is generated correctoly and send to the backend, but if the backend sends an empty HTTP 500, the exception is produced

Thank you

Comment by undefined undefined [ 12/Aug/16 ]

Debugging the code, I can give more information about the case. The received response from the server has a SoapFault:

<?xml version='1.0' encoding='utf-8'?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>Call to a member function load() on null</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

The policy indicates that a security header is required in the response (at least timestamp), so the RampartEngine.process method produces a RampartExcemption with "missingSecurityHeader".

The problem is that the exception is not propagated to the proxyservice's out-sequence, neither fault-sequence, so it is not possible to notify the client with any message

Comment by undefined undefined [ 13/Sep/16 ]

Debugging the code I saw that Rampart stops processing (with the exception) if the response doesn't satisfy the security policy. I have added a timeout to the endpoint, but i think it could be interesting to return an error to the proxy-service





[ESBJAVA-4234] The Throttle Mediator doesn't work correctly when using Respond Mediator without sending message out to an endpoint Created: 24/Sep/15  Updated: 06/Aug/16

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

Type: Bug Priority: High
Reporter: shmily wen Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: 8 hours
Time Spent: Not Specified
Original Estimate: 8 hours
Environment:

windows7 64bit, Developer Studio 3.7.1, JDK 8


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

 Description   

The Throttle Mediator doesn't treats the Respond Mediator as a response, so that the count for concurrent access number is not increase after Respond Mediator send message back to client. When digging into the code, I found ThrottleMediator.java has decrease the rest count for concurrent access number in line 129,
if (concurrentAccessController != null)

{ canAccess = doThrottleByConcurrency(isResponse, synLog); }

and only when SynapseCallbackReceiver.java line 501 is called,
int available = concurrentAccessController.incrementAndGet();
the number will be added back.

But when I use Respond Mediator, it doesn't involve SynapseCallbackReceiver since it doesn't send request to real service, so it doesn't add the number back. After a few invocation, all my request will fail.



 Comments   
Comment by Chanaka Fernando [ 06/Aug/16 ]

This needs a major revamp in the throttle mediator. Hence postponing for future release.





[ESBJAVA-4355] Required Transaction support for the RabbitMQ transport Created: 08/Dec/15  Updated: 06/Aug/16

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

Type: New Feature Priority: High
Reporter: Krishan Malan Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB, RabbitMQ, Transaction
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

In JMS, it is possible to do transactions with the following parameters, but in Rabbitmq transport couldn't find anything similar to this.
<parameter name="transport.jms.SessionTransacted">true</parameter>
<parameter name="transport.jms.SessionAcknowledgement" locked="true">CLIENT_ACKNOWLEDGE</parameter>

Also couldn't find any OOTB solution to do transaction sessions.

Please consider this in future development.






[ESBJAVA-4897] VFS InboundEndpoint onError/Exception Created: 15/Sep/16  Updated: 15/Sep/16

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

Type: Improvement Priority: High
Reporter: Malaka Silva Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Hi,
We are using an inbound endpoint to pull from a sftp location.
We have set the attributes 'sequence' and 'onError' to point at different sequences.
We have specified the Content-Type as application/xml.
When something is successfully pulled from the file location, we expect the `sequence` sequence to be used, when a failure occurs, we expect the `onError` sequence to be used.
When adding xml to the sftp, the inbound endpoint passes the payload to `sequence` but if we add something else (eg. json or malformed xml) to the location, we see an exception thrown on the ESB but the `onError` sequence is not used. This also results in us losing the message entirely.
Could you tell my why the onError sequence isn't used when this failure occurs and so that we can capture and deal with this kind of fault.
I have attached the inbound-endpoint and the exception from esb.

Thanks,
Malaka






[ESBJAVA-4874] Unable to recover Local Registry in Script Mediator Created: 30/Aug/16  Updated: 30/Aug/16

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

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

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

 Description   

Scenario: carbonContext.getRegistry(RegistryType.LOCAL_REPOSITORY) returns null.

I've a sequence with the following script code:

<sequence name="scenario-sequence" trace="disable" xmlns="http://ws.apache.org/ns/synapse">
<script language="js"><![CDATA[
importPackage(Packages.org.wso2.carbon.context);
importPackage(Packages.org.wso2.carbon.registry.api);

var carbonContext = CarbonContext.getThreadLocalCarbonContext();
var registry = carbonContext.getRegistry(RegistryType.LOCAL_REPOSITORY);

if (registry == null)
mc.getServiceLog().info("+++++ Fail! Unable to recover Local Registry in Script Mediator ");
else
mc.getServiceLog().info("+++++ Success! I love WSO2 ESB! ");
]]></script>
</sequence>

The problem is that depending on "who" is calling the scenario sequence, getRegistry returns a null instance.
Through a service proxy, it's all good:
<proxy name="file-listener-test-proxy"
startOnLoad="true" trace="disable" transports="vfs" xmlns="http://ws.apache.org/ns/synapse">
<target>
<inSequence>
<sequence key="scenario-sequence"/>
</inSequence>
<outSequence/>
<faultSequence/>
</target>
<parameter name="transport.vfs.FileURI">file:///C:/TEMP/WSO2/integrator/in</parameter>
<parameter name="transport.vfs.ContentType">application/xml</parameter>
<parameter name="transport.vfs.FileNamePattern">.*\.xml</parameter>
</proxy>

Through a service proxy, it's not ok:
<messageProcessor
class="org.apache.synapse.message.processor.impl.sampler.SamplingProcessor"
messageStore="request-msg-store"
name="request-msg-processor" xmlns="http://ws.apache.org/ns/synapse">
<parameter name="sequence">scenario-sequence</parameter>
<parameter name="interval">1</parameter>
<parameter name="is.active">true</parameter>
<parameter name="concurrency">1</parameter>
</messageProcessor>



 Comments   
Comment by Joao Melo [ 30/Aug/16 ]

typo at description:
Through a message processor, it's not ok:





[ESBJAVA-4866] WSO2ESB js script mediator error on big payload Created: 23/Aug/16  Updated: 23/Aug/16

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

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

win


Severity: Major
Estimated Complexity: Moderate

 Description   

have a seq (WSO2ESb 4.9) calls REST and receives JSON. Then I map JSON to XML via script mediator (JS), here is my configuration:

<case regex="urn:mta:navigation:getMarshes">
<property xmlns:ns="http://ws.apache.org/ns/synapse" name="uri.var.service"
value="getMarshes" scope="default" type="STRING" />
<call>
<endpoint key="adapter.navigation.asu.GetData.Endpoint" />
</call>
<script language="js"><![CDATA[
var array = mc.getPayloadJSON();
var payload = <getMarshesRS/>;

for (i = 0; i < array.length; ++i) {
var elem = array[i];
payload.Marshes += <marsh id=

{elem.mr_id}

num=

{elem.mr_num}

title=

{elem.mr_title}

note=

{elem.mr_note}

mt_id=

{elem.mrt_id}

/>
}
mc.setPayloadXML(payload);
]]></script>
</case>
If I receive not much objects from REST service (10 for example), it works fine. But if I receive 1280 objects, I have an exception

[2016-08-23 16:31:35,799] ERROR - Uncaught exception

{org.apache.axis2.transport.base.threads.NativeWorkerPool}

java.lang.ClassFormatError: Invalid method Code length 186472 in class file org/mozilla/javascript/gen/c187 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at org.mozilla.javascript.DefiningClassLoader.defineClass(DefiningClassLoader.java:62) at org.mozilla.javascript.optimizer.Codegen.defineClass(Codegen.java:126) at org.mozilla.javascript.optimizer.Codegen.createScriptObject(Codegen.java:81) at org.mozilla.javascript.Context.compileImpl(Context.java:2361) at org.mozilla.javascript.Context.compileReader(Context.java:1310) at org.mozilla.javascript.Context.compileReader(Context.java:1282) at org.mozilla.javascript.Context.evaluateReader(Context.java:1224) at com.sun.phobos.script.javascript.RhinoScriptEngine.eval(RhinoScriptEngine.java:172) at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:249) at org.apache.synapse.mediators.bsf.ScriptMediator.processJSONPayload(ScriptMediator.java:322) at org.apache.synapse.mediators.bsf.ScriptMediator.mediateForInlineScript(ScriptMediator.java:294) at org.apache.synapse.mediators.bsf.ScriptMediator.invokeScript(ScriptMediator.java:239) at org.apache.synapse.mediators.bsf.ScriptMediator.mediate(ScriptMediator.java:207) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81) at org.apache.synapse.mediators.filters.SwitchMediator.mediate(SwitchMediator.java:178) at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:267) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:679) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:244) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247) 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)






[ESBJAVA-4889] Issue In Sending Message through HAPi Test Panel Created: 09/Sep/16  Updated: 09/Sep/16

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

Type: Bug Priority: High
Reporter: Amutheezan Sivagnanam Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


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   

When I tried to send Messages using HAPi Test Panel, It shows following error
[2016-09-09 09:22:46,573] ERROR - ApplicationRouterImpl Attempting to send error message to remote system.
ca.uhn.hl7v2.HL7Exception: java.lang.NoClassDefFoundError: org/wso2/carbon/bam/data/publisher/util/PublisherUtil
at ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl.processMessage(ApplicationRouterImpl.java:157)
at ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl.processMessage(ApplicationRouterImpl.java:79)
at ca.uhn.hl7v2.app.Responder.processMessage(Responder.java:90)
at ca.uhn.hl7v2.app.Receiver$Grunt.run(Receiver.java:121)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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: java.lang.NoClassDefFoundError: org/wso2/carbon/bam/data/publisher/util/PublisherUtil
at org.wso2.carbon.business.messaging.hl7.common.data.conf.HL7MessagePublisherConfig.createMessage(HL7MessagePublisherConfig.java:55)
at org.wso2.carbon.business.messaging.hl7.common.HL7ProcessingContext.publishMessage(HL7ProcessingContext.java:315)
at org.wso2.carbon.business.messaging.hl7.common.HL7ProcessingContext.initMessageContext(HL7ProcessingContext.java:302)
at org.wso2.carbon.business.messaging.hl7.transport.utils.HL7MessageProcessor.processMessage(HL7MessageProcessor.java:96)
at ca.uhn.hl7v2.protocol.impl.AppWrapper.processMessage(AppWrapper.java:40)
at ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl.processMessage(ApplicationRouterImpl.java:146)
... 8 more
Caused by: java.lang.ClassNotFoundException: org.wso2.carbon.bam.data.publisher.util.PublisherUtil cannot be found by org.wso2.carbon.business.messaging.hl7.common_4.6.6
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 14 more

[2016-09-09 09:25:30,237] ERROR - ApplicationRouterImpl Attempting to send error message to remote system.
ca.uhn.hl7v2.HL7Exception: java.lang.NoClassDefFoundError: org/wso2/carbon/bam/data/publisher/util/PublisherUtil
at ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl.processMessage(ApplicationRouterImpl.java:157)
at ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl.processMessage(ApplicationRouterImpl.java:79)
at ca.uhn.hl7v2.app.Responder.processMessage(Responder.java:90)
at ca.uhn.hl7v2.app.Receiver$Grunt.run(Receiver.java:121)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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: java.lang.NoClassDefFoundError: org/wso2/carbon/bam/data/publisher/util/PublisherUtil
at org.wso2.carbon.business.messaging.hl7.common.data.conf.HL7MessagePublisherConfig.createMessage(HL7MessagePublisherConfig.java:55)
at org.wso2.carbon.business.messaging.hl7.common.HL7ProcessingContext.publishMessage(HL7ProcessingContext.java:315)
at org.wso2.carbon.business.messaging.hl7.common.HL7ProcessingContext.initMessageContext(HL7ProcessingContext.java:302)
at org.wso2.carbon.business.messaging.hl7.transport.utils.HL7MessageProcessor.processMessage(HL7MessageProcessor.java:96)
at ca.uhn.hl7v2.protocol.impl.AppWrapper.processMessage(AppWrapper.java:40)
at ca.uhn.hl7v2.protocol.impl.ApplicationRouterImpl.processMessage(ApplicationRouterImpl.java:146)
... 8 more



 Comments   
Comment by Amutheezan Sivagnanam [ 09/Sep/16 ]

It worked sucessfully when,
1. Clone the repository https://github.com/wso2/carbon-mediation/tree/v4.6.6
2. Go to <dir>/component/business-adaptors/hl7/org.wso2.carbon.business.messaging.hl7.common/main/java/org/wso2/carbon/business/messaging/hl7/common/data/conf/ and edit HL7MessagePublisherConfig.java file, by replacing bam by das
that is include import org.wso2.carbon.das.data.publisher.util.PublisherUtil; instead of import org.wso2.carbon.bam.data.publisher.util.PublisherUtil;
then edit the pom.xml related to <dir>/component/business-adaptors/hl7/org.wso2.carbon.business.messaging.hl7.common/
by adding dependency for das
<dependency>
<groupId>org.wso2.carbon.mediation</groupId>
<artifactId>org.wso2.carbon.das.data.publisher.util</artifactId>
</dependency>
instead of
<dependency>
<groupId>org.wso2.carbon</groupId>
<artifactId>org.wso2.carbon.bam.data.publisher.util</artifactId>
</dependency>
3. Then build the total project and get the required jar file for the patch, and added patch to your downloaded ESB directory and restart the ESB Server.





[ESBJAVA-4881] Error trying to consume message from message store Created: 01/Sep/16  Updated: 01/Sep/16

Status: Open
Project: WSO2 ESB
Component/s: Message Processors, Message Stores
Affects Version/s: 5.0.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Joao Melo Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB, MB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

I'm using WSO2 ESB 5.0 with MB as a feature, on the same instance.

I'm getting an error StorableMessage cannot be found:

[2016-09-01 14:35:38,739] ERROR - SourceHandler I/O error: Foi forçado o cancelamento de uma conexão existente pelo host remoto
java.io.IOException: Foi forçado o cancelamento de uma conexão existente pelo host remoto
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225)
at sun.nio.ch.IOUtil.read(IOUtil.java:198)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:359)
at org.apache.http.impl.nio.reactor.SessionInputBufferImpl.fill(SessionInputBufferImpl.java:164)
at org.apache.http.impl.nio.codecs.AbstractMessageParser.fillBuffer(AbstractMessageParser.java:136)
at org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection$LoggingNHttpMessageParser.fillBuffer(LoggingNHttpServerConnection.java:379)
at org.apache.http.impl.nio.DefaultNHttpServerConnection.consumeInput(DefaultNHttpServerConnection.java:261)
at org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.consumeInput(LoggingNHttpServerConnection.java:112)
at org.apache.synapse.transport.passthru.ServerIODispatch.onInputReady(ServerIODispatch.java:82)
at org.apache.synapse.transport.passthru.ServerIODispatch.onInputReady(ServerIODispatch.java:39)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
at java.lang.Thread.run(Thread.java:722)
[2016-09-01 14:35:41,794] ERROR - JmsConsumer [msg-store-C-1] cannot receive message from store. Error:Could not deserialize message: java.lang.ClassNotFoundException: org.apache.synapse.message.store.impl.commons.StorableMessage cannot be found by andes_3.1.1
[2016-09-01 14:35:41,796] INFO - ChannelCloseHandler Received channel close for id 1 citing class 0 and method 0

Probably It's missing some .jar on lib, or it has wrong version, but I have no idea which is.






[ESBJAVA-4271] [MB] ESB becomes inaccessible when a user tries to subscribe to a queue without permission Created: 16/Oct/15  Updated: 30/May/16

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.9.0
Fix Version/s: None

Type: Bug Priority: High
Reporter: Dilini Gunatilake Assignee: Dilini Gunatilake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Ubuntu 14.04
JDK: 1.7.0_79
Database : H2
Browser : Firefox 40.0
Setup : Standalone


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

 Description   

Steps to reproduce
--------------------------------------------------------------------------------------------------------
1. Login as the admin user (admin/admin)
2. Create a queue - test
3. Create another user in MB with only login, queue and topic permissions.
4. Create a JMS Proxy to consume messages from test queue by the user created at step 3

Issue
--------------------------------------------------------------------------------------------------------
Exception is logged continuously as follows mentioning permission is denied. Also, Management console will not be accessible and need to restart ESB to work again.

[2015-10-16 11:10:18,256]  INFO - ProxyService Successfully created the Axis2 service for Proxy service : SimpleStockTopicSub2
[2015-10-16 11:10:20,772]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:20,773]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:20,773]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:21,212]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:21,214]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-32
[2015-10-16 11:10:21,214] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:21,215] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:10:21,215] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:10:21,215] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:10:21,217]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:10:25,775] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:10:26,218]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:26,218]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:26,219]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:26,571]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:26,572]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-36
[2015-10-16 11:10:26,572] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:26,573] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:10:26,574] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:10:26,573] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:10:26,575]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:10:31,220] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:10:31,576]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:31,577]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:31,577]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:31,821]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:31,822]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-40
[2015-10-16 11:10:31,823] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:31,824] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:10:31,824] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:10:31,824] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:10:31,825]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:10:36,579] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:10:36,827]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:10:36,827]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:10:36,828]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:10:37,116]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:10:37,117]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-37
[2015-10-16 11:10:37,118] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:10:37,118] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]

[2015-10-16 11:11:18,960] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:11:18,959] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:11:18,961]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:11:23,676] ERROR - ServiceTaskManager Reconnection attempt : 2 for service : SimpleStockTopicSub2 failed. Next retry in 40 seconds
[2015-10-16 11:11:23,962]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:11:23,963]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:11:23,963]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:11:24,405]  INFO - ConnectionCloseMethodHandler ConnectionClose frame received
[2015-10-16 11:11:24,406]  INFO - ConnectionCloseMethodHandler Error :403: access refused:Thread-33
[2015-10-16 11:11:24,406] ERROR - AMQStateManager No Waiters for error saving as last error:org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused]
[2015-10-16 11:11:24,407] ERROR - ServiceTaskManager Error creating JMS consumer for service : SimpleStockTopicSub2. Error registering consumer: org.wso2.andes.AMQSecurityException: org.wso2.andes.AMQSecurityException: Permission denied: binding SimpleStockTopicSub2 [error code 403: access refused] [error code 403: access refused]
[2015-10-16 11:11:24,407] ERROR - ServiceTaskManager JMS Connection failed : 403 - shutting down worker tasks
[2015-10-16 11:11:24,408] ERROR - ServiceTaskManager Error reciving the message.
[2015-10-16 11:11:24,408]  INFO - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2
[2015-10-16 11:11:28,965] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:11:29,410]  WARN - ServiceTaskManager Unable to shutdown all polling tasks of service : SimpleStockTopicSub2
[2015-10-16 11:11:29,411]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 shutdown
[2015-10-16 11:11:29,411]  INFO - ServiceTaskManager Task manager for service : SimpleStockTopicSub2 [re-]initialized
[2015-10-16 11:11:34,412] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : SimpleStockTopicSub2 failed. Next retry in 20 seconds
[2015-10-16 11:11:37,623]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:42,764]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:48,053]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:48,966]  INFO - ServiceTaskManager Reconnection attempt : 2 for service : SimpleStockTopicSub2
[2015-10-16 11:11:53,324]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:54,413]  INFO - ServiceTaskManager Reconnection attempt : 2 for service : SimpleStockTopicSub2
[2015-10-16 11:11:58,611]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2
[2015-10-16 11:11:58,840]  INFO - DeploymentInterceptor Removing Axis2 Service: SimpleStockTopicSub2 {super-tenant}
[2015-10-16 11:11:59,422]  INFO - AMQConnection Unable to connect to broker at tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
org.wso2.andes.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
	at org.wso2.andes.client.util.BlockingWaiter.block(BlockingWaiter.java:176)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:112)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:89)
	at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:126)
	at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:615)
	at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:397)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:327)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
	at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:690)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:868)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:750)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:533)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
	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)
[2015-10-16 11:11:59,425]  INFO - FailoverRoundRobinServers ==== Checking failoverAllowed() ====
[2015-10-16 11:11:59,425]  INFO - FailoverRoundRobinServers Cycle Servers:
Cycle Retries:2
Current Cycle:0
Server Retries:0
Current Retry:0
Current Broker:0
>tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
tcp://192.168.48.142:5672?connectdelay='10'&retries='5'

[2015-10-16 11:11:59,425]  INFO - FailoverRoundRobinServers ====================================
[2015-10-16 11:11:59,426]  INFO - FailoverRoundRobinServers Delay between connect retries:10
[2015-10-16 11:12:03,677]  INFO - ServiceTaskManager Reconnection attempt : 3 for service : SimpleStockTopicSub2

[2015-10-16 11:12:29,448]  INFO - AMQConnection Unable to connect to broker at tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
org.wso2.andes.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
	at org.wso2.andes.client.util.BlockingWaiter.block(BlockingWaiter.java:176)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:112)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:89)
	at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:126)
	at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:615)
	at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:397)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:327)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
	at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:690)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:868)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:750)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:533)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
	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)
[2015-10-16 11:12:29,451]  INFO - FailoverRoundRobinServers ==== Checking failoverAllowed() ====
[2015-10-16 11:12:29,451]  INFO - FailoverRoundRobinServers Cycle Servers:
Cycle Retries:2
Current Cycle:0
Server Retries:5
Current Retry:0
Current Broker:1
tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
>tcp://192.168.48.142:5672?connectdelay='10'&retries='5'

[2015-10-16 11:12:29,452]  INFO - FailoverRoundRobinServers ====================================
[2015-10-16 11:12:29,452]  INFO - FailoverRoundRobinServers Trying tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
[2015-10-16 11:12:29,452]  INFO - FailoverRoundRobinServers Delay between connect retries:10
[2015-10-16 11:12:59,475]  INFO - AMQConnection Unable to connect to broker at tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
org.wso2.andes.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
	at org.wso2.andes.client.util.BlockingWaiter.block(BlockingWaiter.java:176)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:112)
	at org.wso2.andes.client.state.StateWaiter.await(StateWaiter.java:89)
	at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:126)
	at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:615)
	at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:397)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:327)
	at org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
	at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:690)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:868)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:750)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:533)
	at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
	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)
[2015-10-16 11:12:59,478]  INFO - FailoverRoundRobinServers ==== Checking failoverAllowed() ====
[2015-10-16 11:12:59,479]  INFO - FailoverRoundRobinServers Cycle Servers:
Cycle Retries:2
Current Cycle:0
Server Retries:5
Current Retry:1
Current Broker:1
tcp://192.168.48.140:5672?connectdelay='10'&retries='5'
>tcp://192.168.48.142:5672?connectdelay='10'&retries='5'

[2015-10-16 11:12:59,480]  INFO - FailoverRoundRobinServers ====================================
[2015-10-16 11:12:59,480]  INFO - FailoverRoundRobinServers Trying tcp://192.168.48.142:5672?connectdelay='10'&retries='5'
[2015-10-16 11:12:59,481]  INFO - FailoverRoundRobinServers Delay between connect retries:10


 Comments   
Comment by Ravindra Ranwala [ 30/May/16 ]

The given information is not cleat for us to reproduce the issue. Please clearly state the necessary steps to reproduce the issue. If you are sharing the user store etc please state those specific information that will facilitate us to replicate the issue here.





[ESBJAVA-4200] FORCE_SC_ACCEPTED not working as expected when ESB cannot connect to the backend IP. Created: 08/Sep/15  Updated: 06/Aug/16

Status: Open
Project: WSO2 ESB
Component/s: Properties Management
Affects Version/s: 4.9.0 - RC2
Fix Version/s: None

Type: Bug Priority: High
Reporter: Sandapa Handakumbura Assignee: Nadeeshaan Gunasinghe
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : WSO2 ESB-4.9.0-RC4 (standalone)
Java version : jdk1.8.0_45


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

 Description   

When we invoke this proxy we do not get the 202 Accepted. This occurs only when the log mediator is present. When we remove the log mediator we get the 202 Accepted as expected.

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="mypx"
transports="http https"
startOnLoad="true"
trace="disable">
<description/>
<target>
<inSequence>
<property name="OUT_ONLY" value="true" scope="default" type="STRING"/>
<property name="FORCE_SC_ACCEPTED"
value="true"
scope="axis2"
type="STRING"/>
<log>
<property name="**** IN ******" value="AAAAAAAAAAAAA"/>
</log>
<send>
<endpoint>
<address uri="http://10.10.10.10:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
</target>
</proxy>



 Comments   
Comment by Nadeeshaan Gunasinghe [ 06/Aug/16 ]

When sending the request content the thread will wait until it's been notified after submit request or any error occurred. After that the particular thread will be released according to the current implementation.





[ESBJAVA-4199] zookeeper.session.timeout.ms and zookeeper.connection.timeout.ms parameters in kafka inbound endpoint are not working properly Created: 08/Sep/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-RC4
Java version : Oracle jdk 1.7.0
DB Version : embedded H2
OS : Ubuntu 14.04 LTS


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

 Description   

Create a kafka inbound endpoint and give values for zookeeper.session.timeout.ms and zookeeper.connection.timeout.ms parameters.

Timeouts are not performing within the given time durations.






[ESBJAVA-4155] Fault sequence not invoked in tenant mode Created: 03/Sep/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-RC2.zip
Message broker - Apache activemq 5.12.0
OS: Ubuntu 14.04
JDK: 1.7.0_79
Browser : Google Chrome Version 43.0.2357.65 (64-bit)
Setup: Standalone


Attachments: XML File activemq.xml     XML File api.xml     XML File store.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps
1. Create a user in activemq with read / write permissions ( this user does not have admin permission(queue creation) in activemq)
2. Disable anonymous access in activemq
3. Add the activemq jars to esb and create jms message store by giving credentials of the user created in step 1.
4. Create a Tenant and login to esb from that tenant
4. Create a simple api with "post" method and set the in sequence to the message store and set the fault sequence to the default fault sequence.
5. When the api is called the below exception is thrown which is correct but the fault sequence is not called.

In super tenant mode the exact scenario will invoke the fault sequence correctly.

[2015-09-03 18:59:57,743] ERROR - JmsStore Could not create a Message Producer for Store [NewRC1]. Error:User jason is not authorized to create: queue://idntink
javax.jms.JMSSecurityException: User jason is not authorized to create: queue://idntink
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
	at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1398)
	at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:2085)
	at org.apache.activemq.ActiveMQMessageProducer.<init>(ActiveMQMessageProducer.java:124)
	at org.apache.activemq.ActiveMQSession.createProducer(ActiveMQSession.java:1116)
	at org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:361)
	at org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:140)
	at org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:119)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
	at org.apache.synapse.rest.Resource.process(Resource.java:297)
	at org.apache.synapse.rest.API.process(API.java:378)
	at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
	at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:65)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
	at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRESTRequest(MultitenantMessageReceiver.java:611)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.doNhttpREST(MultitenantMessageReceiver.java:555)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.doREST(MultitenantMessageReceiver.java:366)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRequest(MultitenantMessageReceiver.java:224)
	at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:78)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
	at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
	at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: User jason is not authorized to create: queue://idntink
	at org.apache.activemq.security.AuthorizationBroker.addDestination(AuthorizationBroker.java:115)
	at org.apache.activemq.broker.MutableBrokerFilter.addDestination(MutableBrokerFilter.java:177)
	at org.apache.activemq.broker.region.RegionBroker.addProducer(RegionBroker.java:398)
	at org.apache.activemq.broker.jmx.ManagedRegionBroker.addProducer(ManagedRegionBroker.java:267)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.advisory.AdvisoryBroker.addProducer(AdvisoryBroker.java:188)
	at org.apache.activemq.broker.CompositeDestinationBroker.addProducer(CompositeDestinationBroker.java:56)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
	at org.apache.activemq.security.AuthorizationBroker.addProducer(AuthorizationBroker.java:201)
	at org.apache.activemq.broker.MutableBrokerFilter.addProducer(MutableBrokerFilter.java:112)
	at org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:618)
	at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:108)
	at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:338)
	at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
	at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
	at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
	at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:300)
	at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
	... 1 more
[2015-09-03 18:59:57,746]  WARN - JmsProducer [NewRC1-P-2]. Ignored MessageID : urn:uuid:3b254fc3-8979-4829-85e9-05b7383ff84d
[2015-09-03 18:59:57,746] ERROR - MessageStoreMediator Failed to store message [urn:uuid:aecb1192-a044-4b7b-aea1-abe49b81951c] in store [NewRC1].
[2015-09-03 18:59:57,746] ERROR - bbb Failed to store message [urn:uuid:aecb1192-a044-4b7b-aea1-abe49b81951c] in store [NewRC1].
[2015-09-03 18:59:57,747]  INFO - LogMediator To: local://axis2services/aaa, MessageID: urn:uuid:aecb1192-a044-4b7b-aea1-abe49b81951c, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">abdef</text></soapenv:Body></soapenv:Envelope>
[2015-09-03 19:02:57,929]  WARN - SourceHandler Connection time out after request is read: http-incoming-3


 Comments   
Comment by Jason De Silva [ 03/Sep/15 ]

Attached the activemq.xml xml (broker user configuration) and the ESB api and store configurations.





[ESBJAVA-4125] Creating a secondary ldap user store in read only mode fails to authenticate users Created: 27/Aug/15  Updated: 09/Aug/16

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

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

Pack : wso2esb-4.9.0-RC1.zip
ldap : default wso2is-5.0.0 with sp
OS: Ubuntu 14.04
JDK: 1.7.0_79
Browser : Google Chrome Version 43.0.2357.65 (64-bit)
Setup: Standalone


Attachments: XML File recreate.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps
1. Started WSO2 IS500 with SP with port off set to use as the ldap user store
2. Created secondary read only ldap user store in esb by filling mandatory fields pointing to IS ldap
3. The secondary user store was created successfully and the ldap users were shown.
4. Login to ESB with the a secondary user store user after applying login and home page permission for the internal/everyone user role

Issue - invalid user name / password popup is shown

Enabled debug log and found the below exception

javax.naming.directory.InvalidSearchFilterException: Unbalanced parenthesis; remaining name 'ou=Users,dc=WSO2,dc=ORG'
	at com.sun.jndi.ldap.Filter.findRightParen(Filter.java:694)
	at com.sun.jndi.ldap.Filter.encodeFilterList(Filter.java:733)
	at com.sun.jndi.ldap.Filter.encodeComplexFilter(Filter.java:657)
	at com.sun.jndi.ldap.Filter.encodeFilter(Filter.java:104)
	at com.sun.jndi.ldap.Filter.encodeFilterString(Filter.java:74)
	at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:547)
	at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
	at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1847)
	at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
	at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:386)
	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:356)
	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:339)
	at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267)
	at org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.getNameInSpaceForUserName(ReadOnlyLDAPUserStoreManager.java:2047)
	at org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.getNameInSpaceForUserName(ReadOnlyLDAPUserStoreManager.java:2015)
	at org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.doAuthenticate(ReadOnlyLDAPUserStoreManager.java:409)
	at org.wso2.carbon.user.core.common.AbstractUserStoreManager.authenticate(AbstractUserStoreManager.java:419)
	at org.wso2.carbon.user.core.common.AbstractUserStoreManager.authenticate(AbstractUserStoreManager.java:375)
	at org.wso2.carbon.user.core.common.AbstractUserStoreManager.authenticate(AbstractUserStoreManager.java:358)
	at org.wso2.carbon.core.services.authentication.AuthenticationAdmin.login(AuthenticationAdmin.java:100)
	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.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
	at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
	at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
	at org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
	at org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
	at org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
	at org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
	at org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:83)
	at org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:377)
	at org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:244)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)
TID: [-1234] [] [2015-08-27 14:56:20,018] DEBUG {org.wso2.carbon.user.core.common.AbstractUserStoreManager} -  Authentication failure. Wrong username or password is provided. {org.wso2.carbon.user.core.common.AbstractUserStoreManager}



 Comments   
Comment by Jason De Silva [ 27/Aug/15 ]

Uploaded the config file(recreate.xml) created for the secondary user store and observed that below elements have an "amp" removing that and restated the server led ldap users also to successfully login

<Property name="UserNameSearchFilter">(&amp;amp;(objectClass=person)(uid=?))</Property>
<Property name="GroupNameSearchFilter">(&amp;amp;(objectClass=groupOfNames)(cn=?))</Property>
Comment by Chanaka Fernando [ 09/Aug/16 ]

Can you check with ESB 5.0.0 RC2 pack and let us know the result?





[ESBJAVA-4905] Cache Mediator is not Listed in Mediators list Created: 27/Sep/16  Updated: 27/Sep/16

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

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

ESB 5.0


Attachments: PNG File Selection_072.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Refer the attached screenshot.






[ESBJAVA-4906] Message Processor Unable to process message after restarting ESB Created: 27/Sep/16  Updated: 27/Sep/16

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

Type: Bug Priority: High
Reporter: Sudipta Saha Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

UNIX


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

 Description   

If Messages are being queued in Message Stores and the Processor is disables (Use Case - Outage in Downstream) and before activating the Processor the Server crashes for some reason or the ESB is to be restarted for some reason then the Processor picks up the message post restart however the processing is not successful. PFB the generated exception -

TID: [-1] [] [2016-09-27 15:02:06,214] INFO

{org.apache.synapse.core.axis2.TimeoutHandler} - This engine will expire all callbacks after : 120 seconds, irrespective of the timeout action, after the specified or optional timeout {org.apache.synapse.core.axis2.TimeoutHandler}

TID: [-1234] [] [2016-09-27 15:02:06,851] ERROR

{org.apache.synapse.continuation.ContinuationStackManager} - Resource : ba373039034328a55d49f5a1591e8161d0d8fb6b2c08f04d not found {org.apache.synapse.continuation.ContinuationStackManager}

TID: [-1234] [] [2016-09-27 15:02:06,853] ERROR

{org.apache.synapse.core.axis2.SynapseCallbackReceiver} - Synapse encountered an exception, No error handlers found - [Message Dropped]
Resource : ba373039034328a55d49f5a1591e8161d0d8fb6b2c08f04d not found {org.apache.synapse.core.axis2.SynapseCallbackReceiver}




[ESBJAVA-4763] NullPointerException while sending IDOC to SAP Created: 16/Jul/16  Updated: 28/Sep/16

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

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

Attachments: Text File DebuggingWithWSO2SuggestedParameters_sapDebugEnabled.txt     Text File Test_SAP_XSLT.txt     XML File idocTestXSLT.xslt     File sapdelts.dest     Text File test_sap.txt    
Severity: Blocker
Estimated Complexity: Advanced
Test cases added: No

 Description   

Facing the following error while sending the IDOC to SAP.

Transport configurations are fine (Even BAPI message to SAP is successful)

TID: [0] [ESB] [2016-07-12 13:50:39,213] ERROR

{org.wso2.carbon.transports.sap.SAPTransportSender} - Error while sending an IDoc to the EPR : idoc:/sapdelts {org.wso2.carbon.transports.sap.SAPTransportSender}

java.lang.NullPointerException
at org.wso2.carbon.transports.sap.idoc.DefaultIDocXMLMapper.closeStream(DefaultIDocXMLMapper.java:68)
at org.wso2.carbon.transports.sap.idoc.DefaultIDocXMLMapper.getDocumentList(DefaultIDocXMLMapper.java:59)
at org.wso2.carbon.transports.sap.SAPTransportSender.getIDocs(SAPTransportSender.java:163)
at org.wso2.carbon.transports.sap.SAPTransportSender.sendMessage(SAPTransportSender.java:103)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:114)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
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.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:724)
TID: [0] [ESB] [2016-07-12 13:50:39,215] ERROR

{org.apache.synapse.core.axis2.Axis2Sender} - Unexpected error during sending message out {org.apache.synapse.core.axis2.Axis2Sender}

org.apache.axis2.AxisFault: Error while sending an IDoc to the EPR : idoc:/sapdelts
at org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:226)
at org.wso2.carbon.transports.sap.SAPTransportSender.sendMessage(SAPTransportSender.java:136)
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:338)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:333)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
at org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:114)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)



 Comments   
Comment by Muralidharan Balanandan [ 19/Jul/16 ]

Proxy used to send IDOC to SAP

Comment by Muralidharan Balanandan [ 19/Jul/16 ]

the .dest file used to connect to SAP

Comment by Chanaka Fernando [ 20/Jul/16 ]

This looks like an issue with the connectivity from the ESB to SAP over IDOC transport or an error with the IDOC message. Could you please enable the error handler with the following parameters for this proxy and attach the resulting log.

<parameter name="transport.sap.enableTIDHandler">enabled</parameter>
<parameter name="transport.sap.enableErrorListener">enabled</parameter>

Another thing you can do is to check the validity of the IDOC message which you are sending to the SAP system from ESB. If the message is not formatted properly, you will get this kind of error.

Comment by Chanaka Fernando [ 20/Jul/16 ]

Reducing the priority since this looks like a configuration issue.

Comment by Muralidharan Balanandan [ 20/Jul/16 ]

Thanks Chanaka Fernando.. Can you please share some reference to valid IDOC message or message content. It would be very helpful.

Comment by Muralidharan Balanandan [ 21/Jul/16 ]

We validated the IDOC message and its fine. As you suggested, added the above parameters and tried. Attaching the latest proxy. XSLT used and the logs.
Kindly have a look and let us know your findings.

Comment by Muralidharan Balanandan [ 26/Jul/16 ]

Receive the following error code in trace.

TID: [0] [ESB] [2016-07-26 10:09:29,255] WARN

{org.apache.synapse.FaultHandler} - ERROR_CODE : 8001 {org.apache.synapse.FaultHandler}

TID: [0] [ESB] [2016-07-26 10:09:29,255] WARN

{org.apache.synapse.FaultHandler} - ERROR_MESSAGE : null {org.apache.synapse.FaultHandler}

TID: [0] [ESB] [2016-07-26 10:09:29,255] WARN

{org.apache.synapse.FaultHandler} - ERROR_DETAIL : null {org.apache.synapse.FaultHandler}

TID: [0] [ESB] [2016-07-26 10:09:29,255] WARN

{org.apache.synapse.FaultHandler} - ERROR_EXCEPTION : null {org.apache.synapse.FaultHandler}

TID: [0] [ESB] [2016-07-26 10:09:29,256] WARN

{org.apache.synapse.FaultHandler} - FaultHandler : Endpoint [sapidocendpoint] {org.apache.synapse.FaultHandler}

TID: [0] [ESB] [2016-07-26 10:09:29,256] WARN

{org.apache.synapse.endpoints.EndpointContext} - Endpoint : sapidocendpoint will be marked SUSPENDED as it failed {org.apache.synapse.endpoints.EndpointContext}

TID: [0] [ESB] [2016-07-26 10:09:29,256] WARN

{org.apache.synapse.endpoints.EndpointContext} - Suspending endpoint : sapidocendpoint - current suspend duration is : 30000ms - Next retry after : Tue Jul 26 10:09:59 CLT 2016 {org.apache.synapse.endpoints.EndpointContext}

TID: [0] [ESB] [2016-07-26 10:09:29,256] ERROR

{org.wso2.carbon.transports.sap.SAPTransportSender} - Error while sending an IDoc to the EPR : idoc:/sapdelts {org.wso2.carbon.transports.sap.SAPTransportSender}

java.lang.NullPointerException
at org.wso2.carbon.transports.sap.idoc.DefaultIDocXMLMapper.closeStream(DefaultIDocXMLMapper.java:86)
at org.wso2.carbon.transports.sap.idoc.DefaultIDocXMLMapper.getDocumentList(DefaultIDocXMLMapper.java:79)
at org.wso2.ca

Comment by Evanthika Amarasiri [ 28/Sep/16 ]

I too faced the same issue. The reason was that the IDOC message was not correct. When I used a correct IDOC message, the NPE disappeared and the IDOC was sent properly.





[ESBJAVA-1754] Iterate Mediator operation scope not functioning properly with high concurrency Created: 10/Jan/13  Updated: 06/Aug/16

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

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

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

 Description   

Can reproduce with the following configuration:

<?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
<parameter name="cachableDuration">15000</parameter>
</registry>
<proxy name="aggregateMediatorTestProxy" transports="https http" startOnLoad="true" trace="disable">
<description/>
<target>
<inSequence>
<property name="counter" value="0" scope="operation"/>
<iterate xmlns:ns="http://org.apache.synapse/xsd" xmlns:ns3="http://org.apache.synapse/xsd" xmlns:m0="http://services.samples" id="iterate1" preservePayload="true" attachPath="//m0:getQuotes" expression="//m0:getQuotes/m0:getQuote"
sequential="true">
<target>
<sequence>

<log level="full">

<property name="target1" value="***********After 1st Iterate before 2nd Iterate************"/>
</log>
<iterate id="iterate2" preservePayload="true" attachPath="//m0:getQuote" expression="//m0:getQuotes/m0:getQuote/m0:request">
<target sequence="anon">
<sequence>
<property name="counter" expression="get-property('operation','counter') + 1" scope="operation"/>
<log level="custom">
<property name="printingCount" expression="get-property('operation','counter')"/>
</log>
<payloadFactory>
<format>
<m0:getQuote>
<m0:request>
<m0:symbol>WSO2 $1</m0:symbol>
</m0:request>
</m0:getQuote>
</format>
<args>
<arg expression="get-property('operation','counter')"/>
</args>
</payloadFactory>
<log level="full" category="DEBUG">
<property name="target1" value="***********after payload factory************"/>
</log>
<send>
<endpoint>
<address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</sequence>
</target>
</iterate>
</sequence>
</target>
</iterate>
</inSequence>
<outSequence>
<aggregate id="iterate2">
<completeCondition>
<messageCount min="-1" max="-1"/>
</completeCondition>
<onComplete xmlns:ns="http://org.apache.synapse/xsd" xmlns:ns3="http://org.apache.synapse/xsd" xmlns:m0="http://services.samples" expression="//m0:getQuoteResponse">
<log level="custom">
<property name="messageLog" value="****Aggregating****"/>
</log>
<send/>
</onComplete>
</aggregate>
</outSequence>
</target>
</proxy>
<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>
<sequence key="IterateMediatorSequence"/>
</in>
<out>
<sequence key="IteratorAggregateSequence"/>
</out>
</sequence>
</definitions>






[ESBJAVA-1724] ESB returns different response code for invalid URI request Created: 11/Dec/12  Updated: 06/Aug/16

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

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

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

 Description   

How to reproduce:
==============

1. Send HTTP request to invalid URI. Note the $ sign in uri

curl -v http://localhost:8280/services/$simpleProxy?WSO2

  • About to connect() to localhost port 8280 (#0)
  • Trying ::1... connected
  • Connected to localhost (::1) port 8280 (#0)
    > GET /services/?WSO2 HTTP/1.1
    > User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
    > Host: localhost:8280
    > Accept: /
    >
    < HTTP/1.1 200 OK
    < Content-Type: text/html
    < Date: Tue, 11 Dec 2012 14:02:30 GMT
    < Server: Synapse-HttpComponents-NIO
    < Transfer-Encoding: chunked
    <
    <html><head><title>Axis2: Services</title></head><body><h2>Deployed services</h2><h3><a href="/services/wso2carbon-sts?wsdl">wso2carbon-sts</a></h3>Available operations <ul><li>IssueToken</li></ul><h3><a href="/services/echo?wsdl">echo</a></h3>Available operations <ul><li>echoStringArrays</li><li>echoOMElement</li><li>echoInt</li><li>throwAxisFault</li><li>echoString</li></ul><h3><a href="/services/MessageProcessorAdminService?wsdl">MessageProcessorAdminService</a></h3>Available operations <ul><li>getSize</li><li>resendFirstMessage</li><li>deleteAllMessages</li><li>isActive</li><li>modifyMessageProcessor</li><li>getMessageProcessor</li><li>getMessageProcessorNames</li><li>getEnvelope</li><li>getMessageIds</li><li>activate</li><li>addMessageProcessor</li><li>deleteMessageProcessor</li><li>getClassName</li><li>deactivate</li><li>resend</li><li>deleteFirstMessages</li><li>deleteMessage</li><li>resendAll</li></ul><h3><a href="/services/Version?wsdl">Version</a></h3>Available operations <ul><li>getVersion</li></ul* Connection #0 to host localhost left intact
  • Closing connection #0

2. Send HTTP get request again. Note the $$ signs in URI.

curl -v http://localhost:8280/services/$$simpleProxy?WSO2

  • About to connect() to localhost port 8280 (#0)
  • Trying ::1... connected
  • Connected to localhost (::1) port 8280 (#0)
    > GET /services/8743simpleProxy?WSO2 HTTP/1.1
    > User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
    > Host: localhost:8280
    > Accept: /
    >
    < HTTP/1.1 202 Accepted
    < Date: Tue, 11 Dec 2012 14:02:39 GMT
    < Server: Synapse-HttpComponents-NIO
    < Transfer-Encoding: chunked
    <
  • Connection #0 to host localhost left intact
  • Closing connection #0

Why does ESB returns different response code for above two scenarios ? is this the expected behavior ?



 Comments   
Comment by Nuwan Wimalasekara [ 13/Dec/12 ]

curl -v http://localhost:8280/services//simpleProxy also returns 200. this url contains double slashes.





[ESBJAVA-3354] Editing Streams should not be allowed in BAM mediator Created: 30/Oct/12  Updated: 20/Jul/15

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

Type: Bug Priority: Normal
Reporter: Maninda Edirisooriya Assignee: Vijitha Ekanayake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

BAM 2.0.2 with ESB 4.5.1


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

 Description   

In BAM config UI, editing Stream information should not be allowed as edited streams are not supported. Only inserting and deleting should be possible.






[ESBJAVA-3349] BAM Mediator does not store field "meta_host" in Casandra when Internet is not available Created: 24/Sep/12  Updated: 20/Jul/15

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

Type: Bug Priority: Normal
Reporter: Maninda Edirisooriya Assignee: Vijitha Ekanayake
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

BAM 2.0 and ESB 4.5.0


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   

BAM mediator throws an exception while mediating and "meta_host" field seems empty in Cassandra database when Internet is not available. i.e. when IP address is set to 127.0.0.1.






[ESBJAVA-1555] Invalid schemaLocation appears in WSDL when proxy service endpoints are customized with ServiceURI parameter. Created: 30/Aug/12  Updated: 07/Oct/12

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

Type: Bug Priority: Normal
Reporter: Ramith Jayasinghe Assignee: Isuru Udana Loku Narangoda
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

How to reproduce:

1. Get a wsdl with schema imports.
2. Save them (wsdl and xsd files) in a embedded registry (either config registry or governance)
3. Define a proxy service using this wsdl.
4. customize the endpoint of the proxy service using ServiceURI
5. Load the WSDL of the proxy service from SOAP UI and notice SOAP UI complains that it can create the project.
Also notice that 'try it' UI seems to work.

for example:
with following proxy definition:

<proxy name="CustProxy" transports="http" startOnLoad="true" trace="disable">
<target>
<endpoint>
<address uri="http://localhost:8280/services/calculatorImportSchema"/>
</endpoint>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL key="conf:/trunk/calculatorImportSchema.wsdl">
<resource location="SCHEMA_LOCATION" key="conf:/trunk/calculator.xsd"/>
</publishWSDL>
<parameter name="ServiceURI">/test/custom</parameter>
</proxy

WSDL of proxy service will incorrectly point to:
http://localhost:8280/test/custom/CustProxy?xsd=calculator.xsd






[ESBJAVA-1503] New edit options (Source View / Design View) in service list are visible even when proxy services are Inactive. Created: 22/Aug/12  Updated: 25/Jul/15

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.5.0 M5
Fix Version/s: None

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

Pack : WSO2 ESB 4.5.0 - 20th August 2012


Attachments: PNG File screenshot1.png     PNG File screenshot2.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Not-applicable

 Description   

When proxy services are inactive, 'WSDL' and 'Try it' options are not visible in service list(as expected), but new edit options (Source View / Design View)are visible. And if you try to edit inactive proxy services using those options, An error is thrown. Error given on UI doesn't even give the reason.

[2012-08-22 10:07:06,034] ERROR - ProxyServiceAdmin Invalid proxy service definition :: The system is attempting to access an inactive service: InOnlyProxy
org.apache.axis2.AxisFault: The system is attempting to access an inactive service: InOnlyProxy
at org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:1033)
at org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.modifyProxyService(ProxyServiceAdmin.java:321)
at org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.modifyProxy(ProxyServiceAdmin.java:702)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:177)
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:49)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[2012-08-22 10:07:06,059] ERROR - ProxyServiceAdminClient Unable to modify proxy service: InOnlyProxy
org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminProxyAdminException: ProxyServiceAdminProxyAdminException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.modifyProxy(ProxyServiceAdminStub.java:1573)
at org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient.modifyProxy(ProxyServiceAdminClient.java:112)
at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_jsp.java:107)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:161)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:690)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:599)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:536)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:265)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:643)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:637)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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_insertAttribute_7(template_jsp.java:539)
at org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:290)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:161)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:690)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:477)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:329)
at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:258)
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:722)
at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:177)
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:49)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)



 Comments   
Comment by Sandapa Handakumbura [ 22/Aug/12 ]

At least the Error message given on UI should be meaningful.





[ESBJAVA-2213] Callout mediator improvement to get NTLM working Created: 02/May/12  Updated: 06/Aug/16

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

Type: Improvement Priority: Normal
Reporter: Nandika Jayawardana Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any


Attachments: Text File callout-mediator-update.patch     Text File callout-mediator.patch    
Severity: Major
Estimated Complexity: Moderate

 Description   

With this fix, it is possible to reuse the existing Axis2 client options available in the Synapse message context when invoking the external service through the Callout mediator. This can be enabled by setting the property initAxis2ClientOptions to "false". By default, it's value is "true", so that this new addition does not affect any of the its current usages.



 Comments   
Comment by Nandika Jayawardana [ 02/May/12 ]

patch committed to trunk

Comment by Rajika Kumarasiri [ 10/Jul/12 ]

Does this patches made up their ways to Synapse ?

Rajika





[ESBJAVA-3477] Policies loaded using Local Entries should be able to use the default password call back handler. Created: 17/May/12  Updated: 06/Aug/16

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

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

WSO2 ESB 4.0.3


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

 Description   

Policies loaded using the Local Entries in the ESB must be able to use the default password call back handler. ESB throws following error at the current implementation when try to use the default password callback handler.

org.apache.axis2.AxisFault: General security error (WSSecurityEngine: Callback supplied no password for: wso2carbon)
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)






[ESBJAVA-3475] SOAP Faults are not properly decrypted when sending through to a secured endpoint through secured ESB proxy (Both endpoint and proxy are secured with an encryption mechanism) Created: 02/Sep/11  Updated: 06/Aug/16

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

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

Ubuntu, Linux


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

 Description   

Following are the steps to reproduce.
1. Create a service in WSAS
2. Secure WSAS service using security scenario 5 (Sign and Encrypt)
3. Create an ESB proxy and an ESB endpoint
4. Also secure ESB proxy service using security scenario 5 (Sign and Encrypt)
5. Send an invalid message to endpoint through ESB proxy so that endpoint will send a soap fault
6. Client will not receive the soap fault instead it will print a message similar to following,

2011-08-25 14:55:44,799 [-] [main] ERROR AxisEngine The signature or decryption was invalid; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
org.apache.axis2.AxisFault: The signature or decryption was invalid; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95)
at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:259)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:165)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:556)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:532)
at org.wso2.identity.esb.kerberos.KerberosClient.main(Unknown Source)
Caused by: org.apache.ws.security.WSSecurityException: The signature or decryption was invalid; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
at org.apache.ws.security.processor.ReferenceListProcessor.decryptEncryptedData(ReferenceListProcessor.java:250)
at org.apache.ws.security.processor.EncryptedKeyProcessor.decryptDataRef(EncryptedKeyProcessor.java:443)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:381)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(EncryptedKeyProcessor.java:104)
at org.apache.ws.security.processor.EncryptedKeyProcessor.handleToken(EncryptedKeyProcessor.java:84)
at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:333)
at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:250)
at org.apache.rampart.RampartEngine.process(RampartEngine.java:171)
at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 10 more
Caused by: org.apache.xml.security.encryption.XMLEncryptionException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
Original Exception was org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="axis2ns49",rawname="xmlns:axis2ns49"" is invalid. Prefixed namespace bindings may not be empty.
at org.apache.xml.security.encryption.XMLCipher$Serializer.deserialize(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.decryptElement(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.decryptElementContent(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.doFinal(Unknown Source)
at org.apache.ws.security.processor.ReferenceListProcessor.decryptEncryptedData(ReferenceListProcessor.java:248)
... 18 more

Further this issue only occurs when we applied encryption to both client -> ESB and ESB -> WSAS flows.

On ESB side before encrypting message it will get a message similar to following,

<?xml version="1.0" encoding="UTF-8"?>
<fragment
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<faultcode xmlns:axis2ns34="">soapenv:Server</faultcode>
<faultstring xmlns:axis2ns35="">For input string: "1er"</faultstring>
<detail xmlns:axis2ns36=""></detail>
</soapenv:Fault>
</fragment>






[ESBJAVA-1564] Gracefully Restart server does not wait until server to persist synapse configuration in to file system. Created: 03/Sep/12  Updated: 07/Oct/12

Status: Open
Project: WSO2 ESB
Component/s: Core Engine
Affects Version/s: 4.5.0 M5
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Nuwan Wimalasekara Assignee: Isuru Udana Loku Narangoda
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

I upload a synapse configuration which has one proxy service which use groovy script. after test Groovy.jar is removed from class path and upload a new synapse configuration which has not that proxy service. I let 5 sec to deploy new synapse and restart serve gracefully.
when restarting server i got following error and server does not responding any more even if it says carbon server started.
the problem is that proxy service does not delete from file system. when ESB deploying proxy service again error occurred because of no grrovy.jar in classpath.

if we make a much delay scenario get passed. restarting server does not wait server to delete proxy from file system.

Refer Test case:
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/esb/4.5.0/modules/integration/tests/src/test/java/org/wso2/carbon/esb/mediator/test/script/GroovySupportWithinProxyTestCase.java

ERROR

[2012-09-03 12:05:19,629] INFO - Axis2SynapseController Loading mediator extensions...
[2012-09-03 12:05:19,633] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - [2012-09-03 12:05:19,633] INFO - CarbonSynapseController Loading the mediation configuration from the file system
[2012-09-03 12:05:19,635] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- [2012-09-03 12:05:19,635] INFO - MultiXMLConfigurationBuilder Building synapse configuration from the synapse artifact repository at : ././repository/deployment/server/synapse-configs/default
[2012-09-03 12:05:19,636] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - [2012-09-03 12:05:19,636] INFO - XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
[2012-09-03 12:05:19,720] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- [2012-09-03 12:05:19,719] FATAL - ServiceBusInitializer Failed to initialize ESB due to a fatal error
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - java.lang.NoClassDefFoundError: groovy/lang/MissingMethodException
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at com.sun.script.groovy.GroovyScriptEngineFactory.getScriptEngine(GroovyScriptEngineFactory.java:90)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at javax.script.ScriptEngineManager.getEngineByExtension(ScriptEngineManager.java:256)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.mediators.bsf.ScriptMediator.initScriptEngine(ScriptMediator.java:452)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.mediators.bsf.ScriptMediator.initInlineScript(ScriptMediator.java:315)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.mediators.bsf.ScriptMediator.<init>(ScriptMediator.java:134)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.mediators.bsf.ScriptMediatorFactory.createSpecificMediator(ScriptMediatorFactory.java:102)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:192)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:69)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.ProxyServiceFactory.createProxy(ProxyServiceFactory.java:172)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.SynapseXMLConfigurationFactory.defineProxy(SynapseXMLConfigurationFactory.java:142)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.xml.MultiXMLConfigurationBuilder.createProxyServices(MultiXMLConfigurationBuilder.java:225)
[2012-09-03 12:05:19,721] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.config.xml.MultiXMLConfigurationBuilder.getConfiguration(MultiXMLConfigurationBuilder.java:130)
[2012-09-03 12:05:19,721] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.apache.synapse.config.SynapseConfigurationBuilder.getConfiguration(SynapseConfigurationBuilder.java:100)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.Axis2SynapseController.createSynapseConfiguration(Axis2SynapseController.java:443)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.mediation.initializer.CarbonSynapseController.createSynapseConfiguration(CarbonSynapseController.java:167)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.apache.synapse.ServerManager.start(ServerManager.java:177)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:412)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:172)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at java.lang.reflect.Method.invoke(Method.java:597)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
[2012-09-03 12:05:19,722] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
[2012-09-03 12:05:19,722] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.wso2.carbon.event.core.internal.builder.EventBrokerHandler.startEventBroker(EventBrokerHandler.java:57)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS.activate(EventBrokerBuilderDS.java:72)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2012-09-03 12:05:19,723] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2012-09-03 12:05:19,723] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at java.lang.reflect.Method.invoke(Method.java:597)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
[2012-09-03 12:05:19,724] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
[2012-09-03 12:05:19,724] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:503)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:289)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- Caused by: java.lang.ClassNotFoundException: groovy.lang.MissingMethodException
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
[2012-09-03 12:05:19,725] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
[2012-09-03 12:05:19,725] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- ... 70 more
[2012-09-03 12:05:19,727] INFO

{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} - [2012-09-03 12:05:19,727] INFO - RuleEngineConfigDS Successfully registered the Rule Config service
[2012-09-03 12:05:20,490] INFO {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler}

- [2012-09-03 12:05:20,490] INFO - CarbonUIServiceComponent Mgt Console URL : https://10.100.3.190:9443/carbon/
[2012-09-03 12:05:23,053] INFO

{org.wso2.carbon.automation.core.utils.ClientConnectionUtil} - Waiting until server starts on port 9443
[2012-09-03 12:05:24,054] INFO {org.wso2.carbon.automation.core.utils.ClientConnectionUtil}

- Waiting until server starts on port 9443






[ESBJAVA-4734] Update to VFS 2.1 Created: 06/Jul/16  Updated: 07/Aug/16

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

Type: Improvement Priority: Normal
Reporter: Philipp Bruegger Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB, transport, vfs
Remaining Estimate: 4 hours
Time Spent: Not Specified
Original Estimate: 4 hours
Environment:

-


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   

Finally after several years, the Apache VFS library has been update to the version 2.1.

This version contains a whole bunch of bugfixes which are very important.

Please update the VFS library with the new release of the ESB.
Thanks



 Comments   
Comment by Philipp Bruegger [ 06/Jul/16 ]

https://commons.apache.org/proper/commons-vfs/download.html

Also update to the most recent versions of JCIFS and JSCH

Comment by Chanaka Fernando [ 07/Aug/16 ]

Reducing the priority since this is an improvement.





[ESBJAVA-4693] [Intermittent] Response transformation is not working properly in Pre-RC pack which was used Created: 21/Jun/16  Updated: 21/Jun/16

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

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

OS: Ubuntu 14.04
JDK: 1.8.0
Pack


Attachments: File OrderService.aar     File TestCaseCAR_1.0.0.car    
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   

Used the attached proxy service (Test_TransformerProxy_2), sequence (test_seq_4) and xslt (ResponseTransformation.xslt )for response transformation in Pre-RC but failed with the following error

Note: This occurred in a pack that was used for some time

[2016-06-21 12:19:57,260] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "POST /services/Test_TransformerProxy_2.Test_TransformerProxy_2HttpSoap11Endpoint HTTP/1.1[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "Accept-Encoding: gzip,deflate[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "SOAPAction: "urn:getOrderDetails"[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "Content-Length: 318[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "Host: erandi-Latitude-E6540:8280[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "Connection: Keep-Alive[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "User-Agent: Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "[\r][\n]"
[2016-06-21 12:19:57,261] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sam="http://sample.wso2.org">[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "   <soapenv:Header/>[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "   <soapenv:Body>[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "      <sam:getOrderDetails>[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "         <!--Optional:-->[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "         <sam:requestID>icoo2</sam:requestID>[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "      </sam:getOrderDetails>[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "   </soapenv:Body>[\n]"
[2016-06-21 12:19:57,262] DEBUG - wire HTTP-Listener I/O dispatcher-11 >> "</soapenv:Envelope>"
[2016-06-21 12:19:57,262] DEBUG - headers http-incoming-3 >> POST /services/Test_TransformerProxy_2.Test_TransformerProxy_2HttpSoap11Endpoint HTTP/1.1
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> Accept-Encoding: gzip,deflate
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> Content-Type: text/xml;charset=UTF-8
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> SOAPAction: "urn:getOrderDetails"
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> Content-Length: 318
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> Host: erandi-Latitude-E6540:8280
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> Connection: Keep-Alive
[2016-06-21 12:19:57,263] DEBUG - headers http-incoming-3 >> User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
[2016-06-21 12:19:57,268] DEBUG - headers http-outgoing-2 >> POST /services/OrderDetailsRetriever/ HTTP/1.1
[2016-06-21 12:19:57,268] DEBUG - headers http-outgoing-2 >> Accept-Encoding: gzip,deflate
[2016-06-21 12:19:57,268] DEBUG - headers http-outgoing-2 >> Content-Type: text/xml;charset=UTF-8
[2016-06-21 12:19:57,268] DEBUG - headers http-outgoing-2 >> SOAPAction: "urn:getOrderDetails"
[2016-06-21 12:19:57,268] DEBUG - headers http-outgoing-2 >> Transfer-Encoding: chunked
[2016-06-21 12:19:57,269] DEBUG - headers http-outgoing-2 >> Host: 10.100.5.63:9793
[2016-06-21 12:19:57,269] DEBUG - headers http-outgoing-2 >> Connection: Keep-Alive
[2016-06-21 12:19:57,269] DEBUG - headers http-outgoing-2 >> User-Agent: Synapse-PT-HttpComponents-NIO
[2016-06-21 12:19:57,270] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "POST /services/OrderDetailsRetriever/ HTTP/1.1[\r][\n]"
[2016-06-21 12:19:57,270] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "Accept-Encoding: gzip,deflate[\r][\n]"
[2016-06-21 12:19:57,270] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2016-06-21 12:19:57,270] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "SOAPAction: "urn:getOrderDetails"[\r][\n]"
[2016-06-21 12:19:57,270] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "Transfer-Encoding: chunked[\r][\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "Host: 10.100.5.63:9793[\r][\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "Connection: Keep-Alive[\r][\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "[\r][\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "13e[\r][\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sam="http://sample.wso2.org">[\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "   <soapenv:Header/>[\n]"
[2016-06-21 12:19:57,271] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "   <soapenv:Body>[\n]"
[2016-06-21 12:19:57,272] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "      <sam:getOrderDetails>[\n]"
[2016-06-21 12:19:57,272] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "         <!--Optional:-->[\n]"
[2016-06-21 12:19:57,272] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "         <sam:requestID>icoo2</sam:requestID>[\n]"
[2016-06-21 12:19:57,272] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "      </sam:getOrderDetails>[\n]"
[2016-06-21 12:19:57,272] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "   </soapenv:Body>[\n]"
[2016-06-21 12:19:57,272] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "</soapenv:Envelope>[\r][\n]"
[2016-06-21 12:19:57,273] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "0[\r][\n]"
[2016-06-21 12:19:57,273] DEBUG - wire HTTP-Sender I/O dispatcher-2 << "[\r][\n]"
[2016-06-21 12:19:57,275] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "HTTP/1.1 200 OK[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Transfer-Encoding: chunked[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Date: Tue, 21 Jun 2016 06:49:57 GMT[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "Server: WSO2 Carbon Server[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "215[\r][\n]"
[2016-06-21 12:19:57,276] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getOrderDetailsResponse xmlns:ns="http://sample.wso2.org"><ns:return xmlns:ax2439="http://sample.wso2.org/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax2439:OrderDetails"><ax2439:orderAmount>2000</ax2439:orderAmount><ax2439:orderId>12345</ax2439:orderId><ax2439:orderName>Test Order</ax2439:orderName></ns:return></ns:getOrderDetailsResponse></soapenv:Body></soapenv:Envelope>[\r][\n]"
[2016-06-21 12:19:57,277] DEBUG - headers http-outgoing-2 << HTTP/1.1 200 OK
[2016-06-21 12:19:57,277] DEBUG - headers http-outgoing-2 << Content-Type: text/xml;charset=UTF-8
[2016-06-21 12:19:57,277] DEBUG - headers http-outgoing-2 << Transfer-Encoding: chunked
[2016-06-21 12:19:57,277] DEBUG - headers http-outgoing-2 << Date: Tue, 21 Jun 2016 06:49:57 GMT
[2016-06-21 12:19:57,277] DEBUG - headers http-outgoing-2 << Server: WSO2 Carbon Server
[2016-06-21 12:19:57,277] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "0[\r][\n]"
[2016-06-21 12:19:57,277] DEBUG - wire HTTP-Sender I/O dispatcher-2 >> "[\r][\n]"
[2016-06-21 12:19:57,279]  WARN - SynapseConfigUtils Cannot convert null to a StreamSource
[2016-06-21 12:19:57,280] ERROR - XSLTMediator Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:myresources/ResponseTransformation.xslt'}
org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
	at org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:580)
	at org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:81)
	at org.apache.synapse.mediators.transform.XSLTMediator.createTemplate(XSLTMediator.java:394)
	at org.apache.synapse.mediators.transform.XSLTMediator.performXSLT(XSLTMediator.java:243)
	at org.apache.synapse.mediators.transform.XSLTMediator.mediate(XSLTMediator.java:202)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:215)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:332)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
	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-21 12:19:57,281] ERROR - XSLTMediator Unable to perform XSLT transformation using : Value {name ='null', keyValue ='conf:myresources/ResponseTransformation.xslt'} against source XPath : s11:Body/child::*[position()=1] | s12:Body/child::*[position()=1] reason : Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:myresources/ResponseTransformation.xslt'}
org.apache.synapse.SynapseException: Error creating XSLT transformer using : Value {name ='null', keyValue ='conf:myresources/ResponseTransformation.xslt'}
	at org.apache.synapse.mediators.AbstractMediator.handleException(AbstractMediator.java:365)
	at org.apache.synapse.mediators.transform.XSLTMediator.createTemplate(XSLTMediator.java:404)
	at org.apache.synapse.mediators.transform.XSLTMediator.performXSLT(XSLTMediator.java:243)
	at org.apache.synapse.mediators.transform.XSLTMediator.mediate(XSLTMediator.java:202)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:215)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
	at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:332)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
	at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
	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.synapse.SynapseException: Cannot convert null to a StreamSource
	at org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:580)
	at org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:81)
	at org.apache.synapse.mediators.transform.XSLTMediator.createTemplate(XSLTMediator.java:394)
	... 18 more







[ESBJAVA-4674] JMS inbound endpoint CacheLevel param Created: 13/Jun/16  Updated: 13/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Inbound Endpoints
Affects Version/s: 4.9.0, 5.0.0-Beta
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: gregory eve Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Create a JMS inbound endpoint in the management console.

the parameter transport.jms.CacheLevel* is not explicit we have the choice between

{1,2,3}

.

The solution is to read the documentation to find what are these numbers.

A better solution is to replace the numbers by the JMS constants

{conn = 1, session = 2, consumer = 3,none = 0}




[ESBJAVA-4672] New Inbound Endpoint parameters not mandatory Created: 13/Jun/16  Updated: 13/Jun/16

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

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

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

got to the admin console.

Add a new inbound endpoint.
sequence and error sequence are not compulsory.
validate the the form without these params.
An error occured: "Error initializing inbound endpoint test"






[ESBJAVA-4648] The interface to a Registry from Synapse should improve to get the resource media type Created: 02/Jun/16  Updated: 07/Jun/16

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

Type: Improvement Priority: Normal
Reporter: Krishan Malan Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

When going to implement class mediator to create a registry endpoint template it will not identify as a registry template.

After analyzing further, identified that endpoint template should have media type application/vnd.wso2.template.endpoint and artifacts created through the class mediator not having this media type.

We required to improve the registry API for the synapse in order to send media type when creating the endpoint template.

Do following change in org.wso2.carbon.mediation.registry.WSO2Registry.java [1]

public void newResource(String key, boolean isDirectory, String mediaType) {

setTenantInfo();

Registry registry = getRegistry(key);
String resolvedKey = resolvePath(key);
try {
Resource resource;
if (isDirectory)

{ resource = registry.newCollection(); }

else

{ resource = registry.newResource(); resource.setMediaType(mediaType); }

registry.put(resolvedKey, resource);
} catch (RegistryException e)

{ handleException("Error while saving a resource at " + key, e); }

}

[1] https://github.com/wso2/carbon-mediation/blob/master/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L317






[ESBJAVA-4638] Processor should deactivate before send Through the deactivate Seq Created: 30/May/16  Updated: 06/Aug/16

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

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

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

 Description   

Processor should deactivate before send Through the deactivate Seq

https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/message/processor/impl/forwarder/ForwardingService.java#L749-L751






[ESBJAVA-4750] [ESB][JSON][Message Forwarding Processor] Missing square brackets of array when define one value Created: 12/Jul/16  Updated: 29/Jul/16

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

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

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.8
Packs : ESB 4.9.0
ESB Setup: Standalone
JMS Broker: MB (3.1.0)


Attachments: PNG File postmanScreen.png     PNG File responses.png    
Severity: Major
Estimated Complexity: Moderate

 Description   

Prerequisites:

  • ESB should be configured with MB.
  • ESB and MB should be up and running.

Steps to reproduce:
1. Add a proxy (which will accept json messages) and jms message store.

<proxy name="InformationIncome" startOnLoad="true" trace="disable" transports="http https">
        <description/>
        <target>
            <inSequence>
                <log level="full"/>
                <property name="FORCE_SC_ACCEPTED" scope="axis2" value="true"/>
                <property name="OUT_ONLY" value="true"/>
                <property name="content-Type" scope="transport"
                    type="STRING" value="application/json"/>
                <property name="messageType" scope="axis2" type="STRING" value="application/json"/>
                <log level="full"/>
                <store messageStore="InformationIncomeMS"/>
            </inSequence>
        </target>
    </proxy>

 <messageStore
        class="org.apache.synapse.message.store.impl.jms.JmsStore" name="InformationIncomeMS">
        <parameter name="store.jms.destination">JMSQueue</parameter>
        <parameter name="store.producer.guaranteed.delivery.enable">false</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="store.jms.JMSSpecVersion">1.1</parameter>
    </messageStore>

2. Add message processor to retrieve messages. And added endpoint.

<messageProcessor
        class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
        messageStore="InformationIncomeMS" name="testP" targetEndpoint="aspnet">
        <parameter name="client.retry.interval">1000</parameter>
        <parameter name="throttle">false</parameter>
        <parameter name="max.delivery.attempts">4</parameter>
        <parameter name="member.count">1</parameter>
        <parameter name="max.delivery.drop">Enabled</parameter>
        <parameter name="interval">1000</parameter>
        <parameter name="is.active">true</parameter>
        <parameter name="target.endpoint">aspnet</parameter>
    </messageProcessor>

 <endpoint name="aspnet">
        <address uri="http://localhost:9001/services/SimpleStockQuoteService"/>
    </endpoint>
  • Note: endpoint point to tcpmon to identify the response.

3. Send message to proxy service with json content (used POSTMAN). [1]

{
    "name" : "farzam",
    "lastname" : "vatanzadeh",
    "age" : "1000",
    "nested" : {
        "id" : "cd12334dasc",
        "group" : "asd",
        "list" : ["salam"]
    }
}

Expected Result:

  • It should contain square brackets in the message.

Actual Result:

  • It will not contain square bractes in the message when coming after MB

Note: This situation common for JMS brokers as same issue reported through activemq. And also this will be only seen through scheduled message forwarding processor. This working properly with message sampling processor.

When adding two parameters, it takes correctly.[2]

  "list" : ["salam","hello"]

This issue was reported in Stack-overflow [3,4]

[1] Refer attachment: postmanScreen.png
[2] Refer attachment: responses
[3] http://stackoverflow.com/questions/38202892/wso2-esb-array-with-single-element-json-to-json-conversion-brackets-missing
[4] http://stackoverflow.com/questions/38321898/wso2-esb-json-missing-quotes-and-brackets-when-using-scheduld-forwarding-message



 Comments   
Comment by Zygi Mantus [ 29/Jul/16 ]

We have the same bug using DSS and ESB, any clues how to solve this issue?





[ESBJAVA-4749] [WebSocket] dispatch.sequence and dispatch.fault.sequence can be optional Created: 12/Jul/16  Updated: 12/Jul/16

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

Type: Improvement Priority: Normal
Reporter: Balasubramaniyam Senduran Assignee: Kevin Ratnasekera
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Since we can only receive the ws messages and log it or process. i.e without sending it to anther server and receiver the message back.
ws.outflow.dispatch.sequence , ws.outflow.dispatch.fault.sequence can be empty. but currently it is marked as mandatory fields.

Also similar to the Sequence and the Error sequence, adding the functionality to get the sequence from config registry / governance registry would be better.

Parameter names are not consistent eg: "Error Sequence" and "ws.outflow.dispatch.fault.sequence" (i.e space separated and dot separated)






[ESBJAVA-4732] [REST / Tenant ] API invocation URL is displayed incorrectly in management console for tenant mode Created: 06/Jul/16  Updated: 06/Jul/16

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

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

Pack - wso2esb-5.0.0-pre-RC2.zip
JDK - IBM 1.8
DB- MySql 5.7


Attachments: JPEG File Selection_005.jpg    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

1. Create a tenant domain in ESB
2. Login as tenant admin
3. Create a REST API and save
4. Click on API section from the right-hand side
5. Check the API Invocation URL displayed

Expected results:-

Actual Results:-






[ESBJAVA-4711] While deploying a proxy configuration change in tenant in the cluster, one of the workers throws IllegalStateException. Created: 28/Jun/16  Updated: 09/Aug/16

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

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

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

 Comments   
Comment by Jagath Ariyarathne [ 09/Aug/16 ]

Could you please attach the proxy config and the complete error you get.





[ESBJAVA-4647] Getting null point exception in the payload factory mediator when using $ctx Created: 02/Jun/16  Updated: 02/Jun/16

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

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

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

 Description   

When we using $ctx directly in the payload factory mediator if the property is not set, it throws the null point exception [1].This can be reproduced with proxy [2].

[1]
[2016-06-02 11:47:43,471] ERROR - SequenceMediator Runtime error occurred while mediating the message
java.lang.NullPointerException
at org.apache.synapse.mediators.transform.PayloadFactoryMediator.replaceCTX(PayloadFactoryMediator.java:236)
at org.apache.synapse.mediators.transform.PayloadFactoryMediator.regexTransformCTX(PayloadFactoryMediator.java:213)
at org.apache.synapse.mediators.transform.PayloadFactoryMediator.mediate(PayloadFactoryMediator.java:155)
at org.apache.synapse.mediators.transform.PayloadFactoryMediator.mediate(PayloadFactoryMediator.java:104)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:54)
at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:164)
at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:215)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:398)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:145)
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-02 11:47:43,474] INFO - LogMediator To: /services/11test.11testHttpSoap12Endpoint, WSAction: urn:mediate, SOAPAction: urn:mediate, MessageID: urn:uuid:f933dae8-06ed-42a2-b008-8b829ebbb65e, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE = Runtime error occurred while mediating the message, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body/></soapenv:Envelope>

[2]
<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="11test"
transports="http,https"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<property name="param1" value="111111"/>
<property name="param2" value="222222"/>
<payloadFactory media-type="xml">
<format>
<urn:elts xmlns:urn="wso2.esb.test">
<urn:elt1>$1</urn:elt1>
<urn:elt2>$ctx:param2</urn:elt2>
<urn:elt3>$2</urn:elt3>
<urn:elt4>$ctx:param4</urn:elt4>
</urn:elts>
</format>
<args>
<arg evaluator="xml" expression="get-property('param1')"/>
<arg evaluator="xml" expression="get-property('param3')"/>
</args>
</payloadFactory>
<log level="custom"/>
<respond/>
</inSequence>
<outSequence>
<log/>
<send/>
</outSequence>
</target>
<description/>
</proxy>






[ESBJAVA-4639] [ESB][WebContextRoot]Login Fail does not properly indicate with pop up message. Created: 30/May/16  Updated: 30/May/16

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

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

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.7
Packs : ESB 5.0.0 BETA
ESB Setup: Standalone


Attachments: PNG File actualResult.png     PNG File expectedResult.png    
Severity: Major
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0

 Description   

Preconditions:
1) WebContextRoot should be change. (Go to carbon.xml and edit it)

Sample Configuration:

<WebContextRoot>/dilshani</WebContextRoot>

2. ESB should be up and running

Steps to reproduce:
1. Login to ESB with invalid credentials

Expected Result:

  • Proper error message indicating invalid credentials

Actual Result

  • No any error message (Refer attachments)





[ESBJAVA-4608] Can we upgrade JsonPath library to the latest version Created: 10/May/16  Updated: 10/May/16

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

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

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

 Description   

In current esb we are using com.jayway.jsonpath_0.8.1. Can we use the latest version for this as the current version is sort of old.

<dependency>
<groupId>com.jayway.jsonpath</groupId>
<artifactId>json-path</artifactId>
<version>2.2.0</version>
</dependency>






[ESBJAVA-4705] Unable to publish messages to RabbitMQ, if full configuration permissions were not given to RabbitMQ user. Created: 23/Jun/16  Updated: 25/Jul/16

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

Type: Bug Priority: Normal
Reporter: ajanthan e Assignee: Maheeka Jayasuriya
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

After applying the patch0003 in WSO2 ESB 4.9.0 and publishing message to queue through topic exchange and when only the Write permission given to the topic exchange for the RabbitMQ user, not able to publish to the queue and throwing the below error at RabbitMQ logs.

=ERROR REPORT==== 23-Jun-2016::12:09:04 ===
Channel error on connection <0.12984.0> (127.0.0.1:20762 -> 127.0.0.1:5671, vhost: 'EVENT3', user: 'wso2events3user'), channel 1:
operation queue.declare caused a channel exception access_refused: "access to queue 'amq.gen-kgM7wYRYAGlb8tAGDAq7Xg' in vhost 'EVENT3' refused for user 'wso2events3user'"






[ESBJAVA-4659] ESb 5.0.0 axis2.xml doesn't contain the hornetQ listener configurations by default Created: 07/Jun/16  Updated: 07/Jun/16

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

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

ESB 5.0.0


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

 Description   

HornetQ listener configurations [1] are missing in the axis2.xml by default

[1] https://docs.wso2.com/display/ESB500/Configure+with+HornetQ






[ESBJAVA-4655] Lost data in ESB stats Created: 06/Jun/16  Updated: 06/Jun/16

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

Type: Improvement Priority: Normal
Reporter: Amal Gunatilake Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Since ESB statistics cleaning thread and mediation data collection thread are concurrent threads, having the ESB statistics cleaning thread enabled will cause cleaning the data randomly before the mediation data collection thread collects it.

The cause of the problem is enabling both configurations on a given instance. We only should enable either stat-publisher or stat-cleaner. If we enable both, there is a risk of losing data. And if we disable both there is the risk of going OOM.

This looks like an error prone configuration and we can certainly look into how to improve this.

Please refer mail thread: "LOST DATA IN DAS FROM ESB"






[ESBJAVA-4652] [ESB][JMS][Sender]when adding cache level as producer within axis2.xml giving an error Created: 03/Jun/16  Updated: 22/Aug/16

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

Type: Bug Priority: Normal
Reporter: Dilshani Subasinghe Assignee: Eranda Rajapakshe
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.7
Packs : ESB 5.0.0 Alpha
ESB Setup: Standalone
JMS Broker: MB (3.1.0)


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

 Description   

Preconditions:
1. ESB should be configured with MB.
Sample configuration for axis2.xml

 <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
<parameter name="myQueueConnectionFactory" locked="false">
            <parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
            <parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter>
            <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
            <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                        <parameter name="transport.jms.CacheLevel">producer</parameter>
        </parameter>
</transportSender>

2. MB should be up and running
3. ESB should be up and running

Steps to reproduce:
1. Create a proxy in ESB.
Sample configuration:

 <proxy name="StockQuoteProxy" startOnLoad="true" transports="http">
        <description/>
        <target>
            <inSequence>
                <property name="OUT_ONLY" value="true"/>
                <send>
                    <endpoint>
                        <address uri="jms:/StockQuotesQueue?&amp;transport.jms.ConnectionFactory=myQueueConnectionFactory"/>
                    </endpoint>
                </send>
            </inSequence>
            <outSequence>
                <send/>
            </outSequence>
        </target>
    </proxy>

2. Create an queue in MB (Ex: StockQuotesQueue )

3. Publish messages to proxy.

Expected result:

  • Sending messages to jms queue in MB

Actual Result:

  • Proxy cant identify endpoint and adding messages to fault sequence.





[ESBJAVA-4632] [ESB 500][JMS] Missing messages when using "transport.Transactionality" parameter Created: 25/May/16  Updated: 05/Aug/16

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

Type: Bug Priority: Normal
Reporter: Dilshani Subasinghe Assignee: prabath ariyarathna
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.7
Packs : ESB 5.0.0 Alpha
ESB Setup: Standalone
JMS Broker: ActiveMQ (5.11.1)


Attachments: PNG File inboundResult.png     PNG File proxyResult.png    
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

 Description   

Preconditions:
1. ESB should be configured with ActiveMQ.
Configure JMS parameters as follows in axis2.xml

  • JMS receiver
  <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <parameter name="myTopicConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
                <parameter name="transport.jms.DestinationType" locked="false">topic</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>

        <parameter name="default" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
                <parameter name="transport.jms.DestinationType" locked="false">topic</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>
    </transportReceiver>
  • JMS sender
  <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
           <parameter name="myTopicConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
                <parameter name="transport.jms.DestinationType" locked="false">topic</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">failover:tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                <parameter name="transport.Transactionality" locked="false">local</parameter>
                <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
        </parameter>
     </transportSender>

Steps to reproduce:
1. Create ESB proxy with jms transport.

 <proxy name="QueueProxy" startOnLoad="true" transports="https http jms">
        <description/>
        <target>
            <inSequence>
                <property name="OUT_ONLY" value="true"/>
                <log level="full"/>
                <send>
                    <endpoint>
                        <address uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=failover:tcp://localhost:61616&amp;transport.jms.DestinationType=queue&amp;transport.jms.SessionTransacted=true&amp;transport.Transactionality=local"/>
                    </endpoint>
                </send>
            </inSequence>
        </target>
        <parameter name="transport.jms.ConnectionFactory">myQueueConnectionFactory</parameter>
        <parameter name="transport.jms.DestinationType">queue</parameter>
        <parameter name="transport.jms.Destination">QueueProxy</parameter>
    </proxy>

2. Publish messages to queue "QueueProxy"

Expected result:

  • All messages should be send to other queue "MyQueue"

Actual Result:

  • Messages will be missing.

Note: Refer attachments. When testing same scenario with inbound endpoints, it may work properly.



 Comments   
Comment by Nuwan Wimalasekara [ 27/May/16 ]

Hi Dilshani,
I could not observed this behaviour on ESB 5.0.0-BETA. Can you please test this issue on 5.0.0-BETA and verify

Thanks,
Nuwanw

Comment by Dilshani Subasinghe [ 27/May/16 ]

Hi Nuwan,
I can reproduce the issue with Beta pack.

Regards,
Dilshani

Comment by Nuwan Wimalasekara [ 01/Jun/16 ]

This issue can not be reproduced with ActiveMQ client 5.8 versions. only reproduced with ActiveMQ client 5.9 or later versions

Even if the 5.9 version, when we send the messages with DeliveryMode.PERSISTENT, all the messages are consumed by ESB properly.

producer.setDeliveryMode(DeliveryMode.PERSISTENT)

Comment by Isuru Udana Loku Narangoda [ 08/Jun/16 ]

Hi,

Is this only happening when transport.Transactionality is set ?

Comment by Dilshani Subasinghe [ 08/Jun/16 ]

Hi,

Yes, It is.

Regards,
Dilshani

Comment by prabath ariyarathna [ 05/Aug/16 ]

This is only reproduced when we set transaction in the JMS listener side and send messages with non-persistent DeliveryMode . This scenario is highly unlike hence I have reduced the priority level of the ticket.





[ESBJAVA-4635] Message envelope view doesn't show the actual request coming in when a breakpoint added to sequence level Created: 24/May/16  Updated: 09/Jun/16

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

Type: Improvement Priority: Normal
Reporter: Chathurika De Silva Assignee: Nuwan Pallewela
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Ubuntu 14.04
JDK: 1.8.0


Attachments: PNG File MessageEnvelope.png    
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   

The message envelope does not show the actual message when the breakpoint is added to the sequence level. It gets populates only when the mediator level is hit



 Comments   
Comment by Isuru Udana Loku Narangoda [ 09/Jun/16 ]

Here when the message arrive to the sequence mediator (which calls the sequence 'beta_seq_1'), the soap envelope is empty as we are not building the message. Once we go into the mediators in the beta_seq_1 and if there are content-aware mediator placed in that sequence, you will able to see the payload of the message in the Message Envelope view because the message get built at that point.

What we are currently showing is the actual envelope at a particular point in the mediation flow.
And also we cannot forcefully build the message and show it in this view, when debugging is enabled. Debug mode shouldn't cause any behavioural changes to the actual message. Basically in both normal mode and debugger mode, server should have the same behaviour.

To see the message, please use the wirelog view.

Comment by Chathurika De Silva [ 09/Jun/16 ]

Hi Isuru

Thank you for your response. Based on your explanation, I am reopening the issue because if the message envelope is to show the message when built, then until that the tab should be empty or show a text to the user that in that level, the message would not be shown. The empty message body that is shown currently is misleading to the user.

Thank you
Erandi

Comment by Isuru Udana Loku Narangoda [ 09/Jun/16 ]

Hi Chathurika,

We need to align our runtime with the debugger Envelope view. At that point what we have is a empty SOAP Envelope. If we show nothing it is misleading too. This message building mechanism is now a fundamental concept of our ESB which developers must be aware of.

I am resolving the issue, feel free to re-open if you have further concerns.

Comment by Chathurika De Silva [ 09/Jun/16 ]

Hi Isuru

I agree with you. But this is a UI we are providing for the user, and we can make it a better user experience at the UI level by minimizing providing of misleading information to the user and it's not a good practice to assume that the user knows everything about what we provide. So if this is not something that is not going to be fixed, you have the freedom of closing it as "Won't fix"

Thank You
Erandi

Comment by Isuru Udana Loku Narangoda [ 09/Jun/16 ]

I still think we should show whatever available in the Envelope as it is in the Envelope view, because that is what we have at that point in the envelope. It is not a good idea to leave it empty or forcefully build and show the built message which change the behaviour.

So there is no bug in this case, rather this is the expected behaviour.
However it is better to do an improvement (some indicator in the view) which helps someone to understand whether message is build or not.

So I am changing the issue type to Improvement and using the same jira to track it.





[ESBJAVA-4620] Esb 4.9.0 automatically add charset encoring to the Content-Type header and not allowed to remove Created: 13/May/16  Updated: 16/May/16

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

Type: Bug Priority: Normal
Reporter: Randika Perera Assignee: viraj senevirathne
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

ESB 4.9.0 is automatically adds charset encoding to the Content-Type header.

"Content-Type: application/json; charset=UTF-8"

But whenever the back end is not supported for the charset encoding it should be able to modify this and remove.
But it's not allowed to remove this with property or header mediator.






[ESBJAVA-4615] MQTT proxy failed to send messages to endpoint when redeploying the proxy Created: 12/May/16  Updated: 12/May/16

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

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

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

 Description   

The topic that ESB is listening contains the message which is sent with isRetained true, each and every subscription, That topic sends a message to MQTT proxy. This happens when redeploying the proxy. if the endpoint is inside the proxy service, Than it will failed to send the message to backend, because the endpoint is not initialised at the time of message receiving.

As a workaround we can deploy the endpoint separately and refer in the proxy service.

[2016-05-12 17:28:39,422] ERROR - MqttListenerCallback Connection Lost - Client Disconnected from topic esb.newtest1
MqttException (0) - java.lang.IllegalStateException: not initialized, endpoint must be in initialized state
at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:176)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: not initialized, endpoint must be in initialized state
at org.apache.synapse.endpoints.AbstractEndpoint.readyToSend(AbstractEndpoint.java:285)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:60)
at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:232)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.axis2.transport.mqtt.MqttListenerCallback.messageArrived(MqttListenerCallback.java:54)
at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:354)
at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:162)
... 1 more

Sample proxy service.

<proxy xmlns="http://ws.apache.org/ns/synapse"
name="SampleProxy"
transports="mqtt"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log level="custom">
<property name="path" value="Receiving.. "/>
</log>
<property name="OUT_ONLY" value="true"/>
<property name="FORCE_SC_ACCEPTED"
value="true"
scope="axis2"
type="STRING"/>
</inSequence>
<endpoint>
<address uri="mqtt:/SampleProxy?mqtt.server.host.name=localhost&mqtt.server.port=1884&mqtt.client.id=esb.test.sender&mqtt.topic.name=esb.test2&mqtt.subscription.qos=0&mqtt.blocking.sender=false"/>
</endpoint>
</target>
<parameter name="mqtt.topic.name">esb.test</parameter>
<parameter name="mqtt.connection.factory">mqttConFactory</parameter>
<parameter name="mqtt.subscription.qos">0</parameter>
<parameter name="mqtt.session.clean">true</parameter>
<parameter name="mqtt.content.type">text/plain</parameter>
<description/>
</proxy>






[ESBJAVA-4683] [ESB500][JMS][Topics]ESB Subscription will not have proper name in IBM MQ Created: 16/Jun/16  Updated: 16/Jun/16

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

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

Operating System : Windows server-2012-R2
Java Version : JDK1.8
Packs : ESB 5.0.0 Beta
ESB Setup: Standalone
JMS Broker: IBM MQ (8.0.0.2)


Attachments: PNG File WMQ.png    
Severity: Major
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0

 Description   

Preconditions:
1. ESB should be configured with IBM MQ.
Sample Axis2.xml config:

<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
  <parameter name="default" locked="false">
 <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
    <parameter name="java.naming.provider.url" locked="false">file:/C:/Users/Administrator/Documents/jndidirectory</parameter>
    <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">myQueueConnectionFactory</parameter>
    <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
    <parameter name="transport.jms.UserName" locked="false">Administrator</parameter>
    <parameter name="transport.jms.Password" locked="false">wso2321#qa</parameter>
  </parameter>

  <parameter name="myQueueConnectionFactory1" locked="false">
    <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
    <parameter name="java.naming.provider.url" locked="false">file:/C:/Users/Administrator/Documents/jndidirectory</parameter>
    <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">myQueueConnectionFactory</parameter>
    <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
    <parameter name="transport.jms.UserName" locked="false">Administrator</parameter>
    <parameter name="transport.jms.Password" locked="false">wso2321#qa</parameter>
	 </parameter>
	
	<parameter name="myTopicConnectionFactory1" locked="false">
    <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
    <parameter name="java.naming.provider.url" locked="false">file:/C:/Users/Administrator/Documents/jndidirectory</parameter>
    <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">myTopicConnectionFactory</parameter>
    <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
	<parameter name="transport.jms.DestinationType" locked="false">topic</parameter>
    <parameter name="transport.jms.UserName" locked="false">Administrator</parameter>
    <parameter name="transport.jms.Password" locked="false">wso2321#qa</parameter>
  </parameter>
</transportReceiver>

2. IBM MQ should be up and running
3.ESB should be up and running

Steps to reproduce:
1. Created a proxy which will subscribe to a JMS topic
Sample Configuration:

 <proxy name="testProxy" startOnLoad="true" transports="http https jms">
        <description/>
        <target>
            <inSequence>
                <send>
                    <endpoint>
                        <address uri="jms:/jmsTopic?transport.jms.ConnectionFactory=myTopicConnectionFactory1"/>
                    </endpoint>
                </send>
            </inSequence>
        </target>
        <parameter name="transport.jms.Destination">testTopic</parameter>
        <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory1</parameter>
    </proxy>

Expected Result:

  • Subscription should be created within IBM MQ.

Actual Result:

  • Subscription will be created, but without proper name. (Refer attachment)

Note: When adding durable subscriber, it will show the subscriber name properly. When not adding subscriber name, this will be happen






[ESBJAVA-4681] No error when we calling a nonexistent endpoint Created: 15/Jun/16  Updated: 15/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Endpoints Management, Registry
Affects Version/s: 4.9.0
Fix Version/s: None

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

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

 Description   

Test case:

  • create a proxy service or an api
  • in the end sequence add a send mediator and set a nonexistent registry entry
  • test the flow

no error log generated
message pass through faultSequence but ERROR_MESSAGE, ERROR_CODE, etc. are empty.

Same problem if xml in registry ressource is not well formated.






[ESBJAVA-4682] Car file log appender does not append car file name for connectors deployed with the same car file Created: 15/Jun/16  Updated: 15/Jun/16

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

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

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

 Description   

Similar to https://wso2.org/jira/browse/ESBJAVA-4643






[ESBJAVA-4675] JMS Inbound endpoints connection options missing Created: 13/Jun/16  Updated: 24/Jun/16

Status: Open
Project: WSO2 ESB
Component/s: Inbound Endpoints
Affects Version/s: 4.9.0, 5.0.0-Beta
Fix Version/s: None

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

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

 Description   

JMS inbound endpoint restrict the list of connection parameters which can be used, but they are missing parameters.

For example take the parameters which can be used with ActiveMQ: http://activemq.apache.org/connection-configuration-uri.html

Half of the parameters can't be used.

A custom field list could be a solution to allow all the parameters fo all the MQ on the market.

The problem is in the admin console and in the ESB tool.



 Comments   
Comment by gregory eve [ 24/Jun/16 ]

for example we can't add:
<parameter name="transport.jms.ConcurrentConsumers">10</parameter>
<parameter name="transport.jms.MaxConcurrentConsumers">12</parameter>





[ESBJAVA-4653] [ESB][JMS][Sender] Did not create queue in broker when add configuration in axis2.xml Created: 03/Jun/16  Updated: 22/Aug/16

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

Type: Bug Priority: Normal
Reporter: Dilshani Subasinghe Assignee: Eranda Rajapakshe
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.7
Packs : ESB 5.0.0 Alpha
ESB Setup: Standalone
JMS Broker: MB (3.1.0)


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

 Description   

Preconditions:
1. ESB should be configured with MB.
Sample configuration in axis2.xml

 <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
<parameter name="myQueueConnectionFactory" locked="false">
            <parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
            <parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter>
            <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
            <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
</transportSender>

2. MB should be up and running
3. ESB should be up and running

Steps to reproduce:
1. Create a proxy in ESB.
Sample configuration:

 <proxy name="StockQuoteProxy" startOnLoad="true" transports="http">
        <description/>
        <target>
            <inSequence>
                <property name="OUT_ONLY" value="true"/>
                <send>
                    <endpoint>
                        <address uri="jms:/StockQuotesQueue?&amp;transport.jms.ConnectionFactory=myQueueConnectionFactory"/>
                    </endpoint>
                </send>
            </inSequence>
            <outSequence>
                <send/>
            </outSequence>
        </target>
    </proxy>

2. Publish messages to proxy

Expected Result:

  • Creating queue in MB side and publishing messages to it

Actual Result:

  • Giving an error indicating missing listener in broker side.
[2016-06-03 00:36:43,425] ERROR - AMQConnection Throwable Received but no listener set: org.wso2.andes.client.AMQNoRouteException: Error: No Route for message [error code 312: no route]

Note: when created queue in MB, it doesn't give any error. But according to other configurations, it may create queue automatically.






[ESBJAVA-4628] Log Messages when they have Special Characters Created: 23/May/16  Updated: 23/May/16

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

Type: Improvement Priority: Normal
Reporter: Nadeeshaan Gunasinghe Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

When we try to log a full message when there are special characters in the message, ESB throws the following exception

ERROR - LogMediator Could not build full log message: Can not serialize OM Element Envelope






[ESBJAVA-4766]  JSON formatter should be able to escape auto premitive nature selectively on a payload based on JSON field value. Created: 18/Jul/16  Updated: 18/Jul/16

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

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

4.9.0


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

 Description   

JSON formatter should be able to escape auto premitive nature selectively on a payload and this should be configurable at ESB.






[ESBJAVA-4767] Upgrading Saxon-HE to 9.7 Created: 18/Jul/16  Updated: 18/Jul/16

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

Type: Improvement Priority: Normal
Reporter: Nuwan Wimalasekara Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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




[ESBJAVA-4756] Add synapse variables for system and operation scopes Created: 14/Jul/16  Updated: 14/Jul/16

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

Type: Improvement Priority: Normal
Reporter: Nadeeshaan Gunasinghe Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

We need add the synapse variables for operation and system scopes as well



 Comments   
Comment by Nadeeshaan Gunasinghe [ 14/Jul/16 ]

Fix added with https://github.com/wso2/wso2-synapse/pull/575

Thanks,
Nadeeshaan.





[ESBJAVA-4753] Cannot install "Stratos Message Broker - Dashboard UI Features" in ESB Created: 13/Jul/16  Updated: 01/Sep/16

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

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

Operating System : Linux (ubuntu 15.10)
Java Version : JDK1.8
Packs : ESB 4.9.0
ESB Setup: Standalone


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

 Description   

Preconditions:
ESB should be up and running

Steps to reproduce:
1. Go to "features"
2. Installed repo "http://product-dist.wso2.com/p2/carbon/releases/wilkes/"
3. Try to install feature "Stratos Message Broker - Dashboard UI Features" Version 3.1.0

Expected Result:

  • Should install feature

Actual Result:

  • It gives and error as follows:
Cannot complete the install because of a conflicting dependency. Software being installed: WSO2 Stratos Message Broker - Dashboard UI Features 3.1.0 (org.wso2.stratos.mb.dashboard.ui.feature.group 3.1.0) Software currently installed: WSO2 Carbon - Carbon UI Feature 4.4.1 (org.wso2.carbon.core.ui.feature.group 4.4.1) Only one of the following can be installed at once: WSO2 Carbon - Carbon UI Feature 4.4.1 (org.wso2.carbon.core.ui.feature.jar 4.4.1) WSO2 Carbon - Carbon UI Feature 4.4.2 (org.wso2.carbon.core.ui.feature.jar 4.4.2) WSO2 Carbon - Carbon UI Feature 4.4.3 (org.wso2.carbon.core.ui.feature.jar 4.4.3) WSO2 Carbon - Carbon UI Feature 4.4.4 (org.wso2.carbon.core.ui.feature.jar 4.4.4) Cannot satisfy dependency: From: WSO2 Carbon - Carbon UI Feature 4.4.1 (org.wso2.carbon.core.ui.feature.group 4.4.1) To: org.wso2.carbon.core.ui.feature.jar [4.4.1] Cannot satisfy dependency: From: WSO2 Carbon - Carbon UI Feature 4.4.3 (org.wso2.carbon.core.ui.feature.group 4.4.3) To: org.wso2.carbon.core.ui.feature.jar [4.4.3] Cannot satisfy dependency: From: WSO2 Carbon - Carbon UI Feature 4.4.4 (org.wso2.carbon.core.ui.feature.group 4.4.4) To: org.wso2.carbon.core.ui.feature.jar [4.4.4] Cannot satisfy dependency: From: WSO2 Stratos Message Broker - Dashboard UI Features 3.1.0 (org.wso2.stratos.mb.dashboard.ui.feature.group 3.1.0) To: org.wso2.carbon.core.ui.feature.group [4.4.3,4.5.0)

Note: Version 3.0.0 also giving same error and can not install.



 Comments   
Comment by Chanaka Fernando [ 13/Jul/16 ]

What is the use case here?

Comment by Dilshani Subasinghe [ 13/Jul/16 ]

It was given in the documentation [1] that we can install MB UI feature without configuring MB instance. If we are not supporting exact feature, it is better to remove that from the documentation.

[1] https://docs.wso2.com/display/MB310/Integrating+WSO2+ESB

Comment by Joao Melo [ 01/Sep/16 ]

Successful install using the new version of WSO2 ESB 5.0.





[ESBJAVA-4721] When converting xml to JSON ESB is not identifying array with single element as an array. Created: 01/Jul/16  Updated: 01/Jul/16

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

Type: Improvement Priority: Normal
Reporter: Nipun Thameera Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Given a situation when making a request to ESB with JSON payload, and under the hood ESB is building this payload (JSON > XML > JSON) before sending it to the back end.

When ESB is converting JSON payload (with an array which only has single element in it) to xml it will be transform as an single xml entry.
So problem is when converting this XML back to JSON it is not possible to differentiate whether that entry is an attribute or an array. Hence ESB fail to transform the xml to the format of the original JSON payload.

Solution for this is adding xml instructions( <?xml-multiple?>) when converting JSON to XML. Please find below example.

JSON payload

{"users": {"user": ["user1"]}}

Converted XML(without instructions.)

<users>
    <user>user1</user>
</users>

Converted XML(with xml instructions)

<users>
    <?xml-multiple?>
    <user>user1</user>
</users>

Currently this has to be done by adding xslt mediator in ESB and moreover this mediator is payload independent. Hence customers have to write the xslt mediators specifically for every payload which has single array element in it.

So if we can check before transforming, whether JSON payload has an array with single element and if yes, adding the xml instruction when converting JSON to xml by default will prevent the additional overhead of writing xslt mediators.






[ESBJAVA-4699] Endpoint name contains unnecessary information when endpoint description inculded Created: 22/Jun/16  Updated: 22/Jun/16

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

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

ESB 490 standalone pack
JAVA - 7
DB - H2
OS - ubuntu


Attachments: PNG File Endpoints.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Steps to recreate the issue
1) Log in to ESB
2) Create an endpoint (add endpoint description)
3) Save the endpoint

Endpoint name appeared as "span href="#">testendpoint" (image attached)






[ESBJAVA-4662] Error can be seen when set Multi Receivers / Load Balancing urls in DAS Configuration in ESB Created: 08/Jun/16  Updated: 09/Jun/16

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

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

Java version: 1.8.0_45
Setup:standalone
Database : h2


Attachments: PNG File DASPub.png    
Severity: Major
Estimated Complexity: Moderate

 Description   

Steps

1 Logging to ESB console
2 Go to Configure then DAS Configuration and add Add Server.
3 Enter the 2 urls (In this case use ESB analytics urls of failover cluster . Details explanation can be found in [1] )
4 Click Test Server

Below error can be seen *DAS Server cannot be connected! *. Please refer the attached screeshot

[1] https://docs.wso2.com/display/DAS310/Setting+up+Multi+Receiver+and+Load+Balancing+Data+Agent



 Comments   
Comment by Buddhima Wijeweera [ 09/Jun/16 ]

Hi,
Could you please try with a latest ESB pack and see? (Because we had to adopt across product behavior of using OSGi service for publishing data to analytic server)

Thanks,
Buddhima





[ESBJAVA-4637] No need to specify charset when we get byte array from the base64 encoded string Created: 28/May/16  Updated: 30/May/16

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

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

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

 Description   

I think we don't need to specify charset here(1) to decode the string because base64 string doesn't have any specific encodings. So we don't need to specify it.
We can correct this as a
decodedValue = new Base64().decode(charset);

(1) https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/util/xpath/Base64DecodeFunction.java#L86



 Comments   
Comment by Buddhima Wijeweera [ 30/May/16 ]

Hi,

The above mentioned simplification can be achieved with apache commons-codec 1.6. At the moment wso2-synapse is using commons-codes 1.2. Hence the existing way of achieving this is fine.
Additionally commons-codec 1.6 internally use StringUtils.getBytesUtf8() [1], seems does the same as we see in new Base64().decode(value.getBytes(charset));

[1] https://commons.apache.org/proper/commons-codec/apidocs/org/apache/commons/codec/binary/StringUtils.html#getBytesUtf8(java.lang.String)

Thanks,
Buddhima





[ESBJAVA-3886] Enhance the ability of Microsoft SCOM monitoring through SNMP Created: 08/Jul/15  Updated: 06/Aug/16

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

Type: Improvement Priority: Normal
Reporter: Vijitha Ekanayake Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

SCOM can only have a restricted number of discoveries configured, thus they cannot add multiple SNMP entry points for a single server to SCOM. The WSO2 SNMP entry point however only exposes WSO2 specific OIDs and NOT the JVM OIDs. Hence, they cannot monitor WSO2 sufficiently as is required by their customer.

To overcome this problem we have to enhanced the SNMPAgent class to load the JVMManagement OIDs at startup. This means that the SNMP entry point by WSO2 now exposes both WSO2 OIDs as well as JVM OIDs.

https://server.oosnmp.net/dist/release/org/snmp4j/snmp4j-agent-jmx/2.0.0/snmp4j-agent-jmx-2.0.0.jar can be used as the dependency.

Following code may helpful.
// Add this field to the SNMPAgent class
private JvmManagementMib jvmManagementMIB;
// Add the following lines in "registerSnmpMIBs()" below the super.registerSnmpMibs() call:
try

{ jvmManagementMIB = new JvmManagementMibInst(super.agent.getNotificationOriginator()); jvmManagementMIB.registerMOs(server, null); }

catch (DuplicateRegistrationException ex)

{ logger.error("Unable to register JVM-MANAGEMENT-MIB", ex); }




[ESBJAVA-4091] Special characters are not working with the HttpEndpoint template query parameters Created: 21/Aug/15  Updated: 06/Aug/16

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

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

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

 Description   

If we set encoded query parameters value with the special characters like #

original value = 123!@#$^*()

Encoded value = 123!%40%23%24%5E*()

only attached "123!@" part to the URL.






[ESBJAVA-4082] When deactivating/activating proxy services, It's better if a confirmation is requested from the user. Created: 20/Aug/15  Updated: 06/Aug/16

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.9.0 - Beta
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: Sandapa Handakumbura Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Pack : ESB 4.9.0 RC1 SNAPSHOT - 18th August 2015 pack (standalone)
Java version : jdk1.8.0_45


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

 Description   

Something like what's there for message processors ("Do you want to deactivate/activate the proxy service?").






[ESBJAVA-4083] 'Quality of Service Configuration' title is still there in service dashboard. Shouldn't it be removed? Created: 20/Aug/15  Updated: 06/Aug/16

Status: Open
Project: WSO2 ESB
Component/s: Proxy Services Management
Affects Version/s: 4.9.0 - Beta
Fix Version/s: None

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

Pack : ESB 4.9.0 RC1 SNAPSHOT - 18th August 2015 pack (standalone)
Java version : jdk1.8.0_45


Attachments: PNG File QoS.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Not-applicable




[ESBJAVA-4045] Anonymous Endpoint parameter and Pick From Registry parameter has UI issue in target configuration of clone mediator. Created: 11/Aug/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-BETA-SNAPSHOT
Java version : Oracle jdk 1.7.0
DB Version : embedded H2
OS : Ubuntu 14.04 LTS


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

 Description   

Steps to Recreate :

1. Create a custom proxy using clone mediator including below instructions.
-Proxy name - clonetest
-In insequence,
add a clone mediator and a target
-In Target, add an anonymous endpoint as below
http://localhost:9000/services/MTOMSwASampleService
-Then save the proxy

2. Then if we, go to source view, the code will display as below, without the endpoint name we mentioned in target.

<proxy xmlns="http://ws.apache.org/ns/synapse"
name="testclone"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<clone id="12" sequential="true">
<target/>
</clone>
</inSequence>
</target>
<description/>
</proxy>

3. Also when we go to design view of the proxy, the anonymous endpoint of the target configuration has dis-selected.

4.The same scenario happens when referring endpoint via registry for the target config: in clone mediator.






[ESBJAVA-4008] Cannot install any feature after uninstalling a feature Created: 04/Aug/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-BETA-SNAPSHOT (https://svn.wso2.org/repos/wso2/people/chanakaf/ESB490-Beta/)
Java Version : Java 1.7
Setup : Standalone
Browser : Chrome Version 43.0.2357.130 (64-bit) | FireFox 38.0
DB : H2


Attachments: PNG File Selection_252.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Steps to Reproduce

1. Add the P2 repo and install a feature. (In my case I installed "Business Adaptor HL7")
2. Now uninstall the feature.
3. Now try to install another feature.

Issue : After selecting a feature Next button is inactive and following was observed in the UI. Also refer the screenshot attached.

The copies of profile default are not in sync.


 Comments   
Comment by Yasassri Rathnayake [ 04/Aug/15 ]

After restarting the server the issue was fixed.





[ESBJAVA-4009] Inbound Endpoints icon is the same as Scheduled Tasks icon. Created: 04/Aug/15  Updated: 06/Aug/16

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

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

Pack : ESB 4.9.0 BETA SNAPSHOT - 04-08-2015 (standalone)
Java version : jdk1.8.0_45
Browsers : FF, Chrome


Attachments: PNG File InboundEP_icon.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Not-applicable




[ESBJAVA-4072] User Token policy applied to axis2 service allows to consume service without authentication credentials Created: 19/Aug/15  Updated: 06/Aug/16

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

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

OS: Ubuntu 14.04
JDK: 1.7.0_79
Browser : Google Chrome Version 43.0.2357.65 (64-bit)
Setup: Standalone


Attachments: Zip Archive UTAxis2Service.zip     Zip Archive UserTokenPolicy.zip     File UserTokenService_1.0.0.aar    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps
1. Created a axis2 service using dev studio 3.8 alpha ( axis2 service project is attached )
2. Created a username token policy using dev studio ( Registry handler project attached)
3. Added the UT policy details to axis2 - services.xml to secure the service
4. Exported the axis2 service using dev studio and deployed the axis2 service in esb (service file is attached)
5. Service is shown as secured in esb

Issue
1. Invoked the axis2 service via soap ui without providing any security header and the request was successful.
2. Invoked the service using try it tool with false user name and password. Response is shown with the string echoed. And also below exception is thrown.

[2015-08-19 06:43:39,121] ERROR - AxisEngine SOAP header missing
org.apache.axis2.AxisFault: SOAP header missing
	at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:186)
	at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
	at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
	at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:359)
	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.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
	at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
	at org.apache.jsp.admin.jsp.WSRequestXSSproxy_005fajaxprocessor_jsp._jspService(WSRequestXSSproxy_005fajaxprocessor_jsp.java:294)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
	at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rampart.RampartException: SOAP header missing
	at org.apache.rampart.RampartEngine.process(RampartEngine.java:128)
	at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
	... 55 more






[ESBJAVA-4071] Applied kerberos security to axis2 service but allows to consume service without security headers Created: 19/Aug/15  Updated: 06/Aug/16

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

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

OS: Ubuntu 14.04
JDK: 1.7.0_79
Browser : Google Chrome Version 43.0.2357.65 (64-bit)
Setup: Standalone


Attachments: Zip Archive ESBConfFile.zip     Zip Archive EchoAxis2WebService.zip     Zip Archive ISConfFolder.zip     Zip Archive KerberosPolicy.zip     PNG File TryIt.png    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps
1. Activated KDC in wso2is 5.0.0 (IS conf attached)
2. Enabled kerberos in esb - ( ESB conf with is attached )
3. Created a echo axis2 service using devstudio 3.8 alpha ( axis2 project is attached )
4. Created kerberos policy from devstudio (policy project is attached)
5. Secured the axis2 service by adding the kerberos policy in axis2 services.xml
6. Exported the axis2 service .aar file and deployed it in esb
7. The service is shown as secured in esb

Issue
1. Event though service is shown as secured by invoking the service via soapui the response was received without sending security headers
2. Tryit tool also successfully shows the response even though warnings are shown (Refer pic attached)






[ESBJAVA-4062] ciphertool.bat file will not run as distributed Created: 13/Aug/15  Updated: 06/Aug/16

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

Type: Bug Priority: Normal
Reporter: Gregory Streetman Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 4 hours
Time Spent: Not Specified
Original Estimate: 4 hours
Environment:

Windows


Severity: Minor
Estimated Complexity: Novice
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   

The ciphertool.bat file adds all jars in the plugins directory to the classpath. This exceds the size of a command line, and the error you get is "The input line is too long" and "the syntax of the command is incorrect". To fix this, the line that adds these jars to the classpath:
FOR %%c in ("%CARBON_HOME%\repository\bib*.jar") DO set CARBON_CLASSPATH=Unable to render embedded object: File (CARBON_CLASSPATH) not found.;".\repository\lib%%~nC%%~xC"
Needs to be commented out. The ciphertool code does not require any of these external files.






[ESBJAVA-4054] Issue in cxf-ws-rm inbound endpoint. Created: 12/Aug/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-BETA-SNAPSHOT
Java version : Oracle jdk 1.7.0
DB Version : 5.5.5-10.0.20-MariaDB-wsrep
OS : Ubuntu 14.04 LTS


Attachments: PNG File cxf-rm-inbound.png     XML File server.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: No

 Description   

Steps to Recreate :

1. Create the following cxf-ws-rm inbound endpoint.
<inboundEndpoint name="cxf_rm_test" onError="fault"
protocol="cxf_ws_rm" sequence="RMIn" suspend="false">
<parameters>
<parameter name="inbound.cxf.rm.host">localhost</parameter>
<parameter name="inbound.cxf.rm.config-file">repository/conf/cxf/server.xml</parameter>
<parameter name="inbound.cxf.rm.port">4545</parameter>
</parameters>
</inboundEndpoint>
2. Specify incorrect name for the inbound.cxf.rm.config-file field as "repository/conf/cxf/serv.xml" in the same configuration.
Then an error message will show as it should be.

3. Then edit the inbound endpoint and give the correct configuration name as "repository/conf/cxf/server.xml"

UI throws an error message as "Unknown". Also, retained the incorrect configuration name.

ESB throws following errors.


ERROR - RPCInOnlyMessageReceiver Exception occurred while trying to invoke service method updateInboundEndpoint


java.lang.NullPointerException
	at org.wso2.carbon.inbound.endpoint.protocol.cxf.wsrm.InboundRMHttpListener.destroy(InboundRMHttpListener.java:136)
	at org.apache.synapse.inbound.InboundEndpoint.destroy(InboundEndpoint.java:125)
	at org.wso2.carbon.inbound.CarbonInboundManagementService.updateInboundEndpoint(CarbonInboundManagementService.java:209)
	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.updateInboundEndpoint(InboundAdminStub.java:1092)
	at org.wso2.carbon.inbound.ui.internal.InboundManagementClient.updteInboundEndpoint(InboundManagementClient.java:330)
	at org.apache.jsp.inbound.updateInbound_jsp._jspService(updateInbound_jsp.java:200)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
	at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.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.GeneratedMethodAccessor39.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:640)
	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:395)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
	at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.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:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)


 ERROR - InboundManagementClient org.apache.axis2.AxisFault: unknown
 

4. Also, in the same scenario, if we restart the ESB and go to inbound endpoint section in ESB, the inbound endpoint does not show there.






[ESBJAVA-4015] "encoding" attribute can be added only from master source view and it gets removed when edited from an Endpoint/Template design view/ source view. Created: 05/Aug/15  Updated: 06/Aug/16

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

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

Pack : ESB 4.9.0 BETA SNAPSHOT - 05-08-2015 (standalone)
Java version : jdk1.8.0_45


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

 Description   

Before editing (in master source view) :

<endpoint name="testEP">
<address encoding="UTF-16" uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>

After editing from endpoint design/source view :

<endpoint name="testEP">
<address uri="http://localhost:9001/services/SimpleStockQuoteService"/>
</endpoint>

Same happens for endpoint templates.






[ESBJAVA-4007] Exception observed when uninstalling a feature Created: 04/Aug/15  Updated: 06/Aug/16

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

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

Pack : wso2esb-4.9.0-BETA-SNAPSHOT (https://svn.wso2.org/repos/wso2/people/chanakaf/ESB490-Beta/)
Java Version : Java 1.8.0_05
Setup : Standalone
Browser : Chrome Version 43.0.2357.130 (64-bit) | FireFox 38.0
DB : H2


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

 Description   

Steps to Reproduce

1. Add the P2 repo and install a feature. (In my case I installed "Business Adaptor HL7")
2. Now uninstall the feature.

Issue : Following exception was observed.

 INFO - CarbonAuthenticationUtil 'admin@carbon.super [-1234]' logged in at [2015-08-04 15:09:28,785+0530]
java.io.FileNotFoundException: /home/chanaka/Source-Code-GIT/ESB490/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.1/repository/components/artifacts.xml (No such file or directory)
	at java.io.FileOutputStream.open(Native Method)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
	at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.save(SimpleArtifactRepository.java:1187)
	at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.save(SimpleArtifactRepository.java:1168)
	at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.<init>(SimpleArtifactRepository.java:348)
	at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.create(SimpleArtifactRepositoryFactory.java:134)
	at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryCreate(ArtifactRepositoryManager.java:61)
	at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.doCreateRepository(AbstractRepositoryManager.java:288)
	at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.createRepository(ArtifactRepositoryManager.java:49)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getBundlePoolRepository(Util.java:86)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.EclipseMarkSetProvider.getMarkSets(EclipseMarkSetProvider.java:41)
	at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector$ParameterizedSafeRunnable.run(GarbageCollector.java:69)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.contributeMarkSets(GarbageCollector.java:97)
	at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.traverseRegisteredProfiles(GarbageCollector.java:225)
	at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.runGC(GarbageCollector.java:163)
	at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.notify(GarbageCollector.java:148)
	at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.dispatchEvent(ProvisioningEventBus.java:108)
	at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.dispatchEvent(ProvisioningEventBus.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
	at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.publishEvent(ProvisioningEventBus.java:85)
	at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:96)
	at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
	at org.eclipse.equinox.internal.provisional.p2.director.PlanExecutionHelper.executePlan(PlanExecutionHelper.java:41)
	at org.eclipse.equinox.internal.provisional.p2.director.PlanExecutionHelper.executePlan(PlanExecutionHelper.java:23)
	at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.performProvisioningAction(ProvisioningUtils.java:209)
	at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.performProvisioningAction(ProvisioningUtils.java:70)
	at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.performProvisioningAction(ProvisioningUtils.java:85)
	at org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminService.performProvisioningAction(ProvisioningAdminService.java:313)
	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.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
	at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
	at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
	at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
	at org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.wso2.carbon.feature.mgt.stub.ProvisioningAdminServiceStub.performProvisioningAction(ProvisioningAdminServiceStub.java:1085)
	at org.wso2.carbon.feature.mgt.ui.ProvisioningAdminClient.performInstallation(ProvisioningAdminClient.java:138)
	at org.apache.jsp.feature_002dmgt.perform_005finstallation_002dajaxprocessor_jsp._jspService(perform_005finstallation_002dajaxprocessor_jsp.java:107)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
	at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)






[ESBJAVA-4004] Task with trigger count set to 0 gets invoked once during server restart. Created: 03/Aug/15  Updated: 06/Aug/16

Status: Open
Project: WSO2 ESB
Component/s: Scheduled Tasks
Affects Version/s: 4.9.0 - Beta
Fix Version/s: None

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

Pack : ESB 4.9.0 BETA SNAPSHOT - 29-07-2015 (standalone)
Java version : jdk1.8.0_45


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

 Description   

Steps to reproduce :

1. Add a scheduled task and set the trigger count to 0.

 <task class="org.apache.synapse.startup.tasks.MessageInjector"
        group="synapse.simple.quartz" name="CheckPrice">
        <trigger count="0" interval="5"/>
        <property name="to"
            value="http://localhost:9000/services/SimpleStockQuoteService" xmlns:task="http://www.wso2.org/products/wso2commons/tasks"/>
        <property name="soapAction" value="urn:getQuote" xmlns:task="http://www.wso2.org/products/wso2commons/tasks"/>
        <property name="message" xmlns:task="http://www.wso2.org/products/wso2commons/tasks">
            <m0:getQuote xmlns:m0="http://services.samples">
                <m0:request>
                    <m0:symbol>IBM</m0:symbol>
                </m0:request>
            </m0:getQuote>
        </property>
    </task>

2. Restart the server.

The task gets executed once.

[2015-08-03 20:41:32,509]  INFO - AbstractQuartzTaskManager Task scheduled: [-1234][ESB_TASK][CheckPrice]
[2015-08-03 20:41:32,510]  INFO - StartupFinalizerServiceComponent Server           :  WSO2 Enterprise Service Bus-4.9.0
[2015-08-03 20:41:32,510]  INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 21 sec
[2015-08-03 20:41:32,557]  INFO - LogMediator To: http://localhost:9000/services/SimpleStockQuoteService, WSAction: urn:getQuote, SOAPAction: urn:getQuote, MessageID: urn:uuid:b5ae6d3c-d44e-4220-83ab-74e96c74f128, Direction: request, MAIN_SEQUENCE_INVOKED = $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><m0:getQuote xmlns:m0="http://services.samples">
         <m0:request>
            <m0:symbol>IBM</m0:symbol>
         </m0:request>
      </m0:getQuote></soapenv:Body></soapenv:Envelope>
[2015-08-03 20:41:32,570]  INFO - TimeoutHandler This engine will expire all callbacks after : 120 seconds, irrespective of the timeout action, after the specified or optional timeout
[2015-08-03 20:41:32,612]  WARN - ConnectCallback Connection refused or failed for : localhost/127.0.0.1:9000
[2015-08-03 20:41:32,643]  INFO - LogMediator To: http://localhost:9000/services/SimpleStockQuoteService, WSAction: urn:getQuote, SOAPAction: urn:getQuote, MessageID: urn:uuid:b5ae6d3c-d44e-4220-83ab-74e96c74f128, Direction: request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 101503, ERROR_MESSAGE = Error connecting to the back end, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><m0:getQuote xmlns:m0="http://services.samples">
         <m0:request>
            <m0:symbol>IBM</m0:symbol>
         </m0:request>
      </m0:getQuote></soapenv:Body></soapenv:Envelope>
[2015-08-03 20:41:32,796]  INFO - CarbonUIServiceComponent Mgt Console URL  : https://192.168.1.5:9443/carbon/





[ESBJAVA-3969] HTTP/1.1 200 OK returned for a non-modified request containing If-None-Match <Etag with weak ETag validator> Created: 27/Jul/15  Updated: 06/Aug/16

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

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

ESB 4.9.0 Alpha5
Ubuntu 13.04
JRE 1.8.0_45


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

 Description   

When a non-modified request containing an ETag with a weak etag validatior for "If-None-Match", 'HTTP/1.1 200 OK' is returned instead of 'HTTP/1.1 304 Not Modified'

(For string etags HTTP/1.1 304 Not Modified is returned as expected)

Strong ETag validator :

curl -X POST -i -d @/home/kaushie/WSO2PRODUCTS/APIM/Desktop/hello -H "If-None-Match: \"-9590-4432100-54118-1017194-79-8657-4522-66\"" -H "SOAPAction: urn::greet" -H "Content-Type: text/xml" http://localhost:8280/services/helloProxy6

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)
HTTP/1.1 304 Not Modified
ETag: "-9590-4432100-54118-1017194-79-8657-4522-66"
Content-Type: text/xml;charset=UTF-8; charset=UTF-8
Date: Mon, 27 Jul 2015 12:02:50 GMT

__________________________________________________

Weak ETag validator:

curl -X POST -i -d @/home/kaushie/WSO2PRODUCTS/APIM/Desktop/hello -H "If-None-Match: W\"-9590-4432100-54118-1017194-79-8657-4522-66\"" -H "SOAPAction: urn::greet" -H "Content-Type: text/xml" http://localhost:8280/services/helloProxy6

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)
HTTP/1.1 200 OK
ETag: "-9590-4432100-54118-1017194-79-8657-4522-66"
Content-Type: text/xml;charset=UTF-8; charset=UTF-8
Date: Mon, 27 Jul 2015 12:02:59 GMT
Transfer-Encoding: chunked






[ESBJAVA-3953] Xerces error while processing IDocs Created: 23/Jul/15  Updated: 06/Aug/16

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

Type: Bug Priority: Normal
Reporter: Edward Walther Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: Axis2, ESB, Idoc, Xerces
Remaining Estimate: Not Specified