[ESBJAVA-4783] JMS store UI directs to MB message store UI when editing message store Created: 23/Jul/16  Updated: 23/Jul/16  Resolved: 23/Jul/16

Status: Resolved
Project: WSO2 ESB
Component/s: Message Stores
Affects Version/s: 5.0.0-Beta2
Fix Version/s: 5.0.0

Type: Bug Priority: High
Reporter: Buddhima Wijeweera Assignee: Buddhima Wijeweera
Resolution: Fixed Votes: 0
Labels: ESB-500, UI
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB 5.0.0 Beta2


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

 Description   

When editing a JMS store, UI shows MB store edting UI



 Comments   
Comment by Buddhima Wijeweera [ 23/Jul/16 ]

Fixed with https://github.com/wso2/carbon-mediation/pull/698.diff





[ESBJAVA-4772] [IBM JDK] Unable to start ESB pack with IBM JDK Created: 18/Jul/16  Updated: 22/Jul/16  Resolved: 20/Jul/16

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

Type: Bug Priority: Highest
Reporter: Pubudu D.P Assignee: Balasubramaniyam Senduran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

JDK:-
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160427_1620_B301573
JIT - tr.r14.java.green_20160329_114288
GC - R28_Java8_SR3_20160427_1620_B301573_CMPRSS
J9CL - 20160427_301573)
JCL - 20160421_01 based on Oracle jdk8u91-b14

Pack: wso2esb-5.0.0-BETA2.zip (Standalone)
OS: Ubuntu 14.04


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

 Description   

Pre-condition:-

  • IBM JDK should be installed

1. Unzip a fresh pack and start the server
2. Observe the logs

Expected Results:-

  • Server should be started without any errors

Actual Results:-

  • Following error is triggered and the server is not started

[2016-07-18 11:56:23,146]  INFO - UserStoreMgtDSComponent Carbon UserStoreMgtDSComponent activated successfully.
[2016-07-18 11:56:32,756]  INFO - TaglibUriRule TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined
[2016-07-18 11:56:32,908] ERROR - StandardContext Exception sending context initialized event to listener instance of class org.owasp.csrfguard.CsrfGuardServletContextListener
java.lang.RuntimeException: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at org.owasp.csrfguard.config.PropertiesConfigurationProviderFactory.retrieveConfiguration(PropertiesConfigurationProviderFactory.java:34)
	at org.owasp.csrfguard.config.overlay.ConfigurationAutodetectProviderFactory.retrieveConfiguration(ConfigurationAutodetectProviderFactory.java:73)
	at org.owasp.csrfguard.CsrfGuard.retrieveNewConfig(CsrfGuard.java:112)
	at org.owasp.csrfguard.CsrfGuard.config(CsrfGuard.java:86)
	at org.owasp.csrfguard.CsrfGuard.isPrintConfig(CsrfGuard.java:685)
	at org.owasp.csrfguard.CsrfGuardServletContextListener.printConfigIfConfigured(CsrfGuardServletContextListener.java:97)
	at org.owasp.csrfguard.CsrfGuardServletContextListener.contextInitialized(CsrfGuardServletContextListener.java:86)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
	at java.util.concurrent.FutureTask.run(FutureTask.java:277)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.lang.Thread.run(Thread.java:785)
Caused by: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at org.owasp.csrfguard.config.PropertiesConfigurationProvider.<init>(PropertiesConfigurationProvider.java:234)
	at org.owasp.csrfguard.config.PropertiesConfigurationProviderFactory.retrieveConfiguration(PropertiesConfigurationProviderFactory.java:32)
	... 15 more
Caused by: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at sun.security.jca.GetInstance.getService(GetInstance.java:99)
	at sun.security.jca.GetInstance.getInstance(GetInstance.java:218)
	at java.security.SecureRandom.getInstance(SecureRandom.java:342)
	at org.owasp.csrfguard.config.PropertiesConfigurationProvider.<init>(PropertiesConfigurationProvider.java:121)
	... 16 more
[2016-07-18 11:56:32,910] ERROR - StandardContext One or more listeners failed to start. Full details will be found in the appropriate container log file
[2016-07-18 11:56:32,915] ERROR - StandardContext Context [/] startup failed due to previous errors



 Comments   
Comment by Pubudu D.P [ 18/Jul/16 ]

Same issue exists with IBM JDK 1.7 as well.

java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470_27sr3fp40-20160422_01(SR3 FP40))
IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20160406_298393 (JIT enabled, AOT enabled)
J9VM - R27_Java727_SR3_20160406_0942_B298393
JIT - tr.r13.java_20160328_114186
GC - R27_Java727_SR3_20160406_0942_B298393_CMPRSS
J9CL - 20160406_298393)
JCL - 20160421_01 based on Oracle jdk7u101-b14

Comment by Chanaka Fernando [ 20/Jul/16 ]

Please set the following property[1] in "Owasp.CsrfGuard.Carbon.properties" file (SERVER_HOME/repository/conf/security) which is default set to [2].

[1] - org.owasp.csrfguard.PRNG.Provider=IBMJCE
[2] - org.owasp.csrfguard.PRNG.Provider=SUN

Comment by Chankami Maddumage [ 21/Jul/16 ]

Hi Chanaka ,

This same issue exists after changing mentioned property with IBM JDK 1.8 in ES-Analytics (5.0.0 beta).
Any other workaround to resolve this ?

Cheers,
Chankami

Comment by Chanaka Fernando [ 21/Jul/16 ]

Hi Chankami,

This is fixed with following PR[1]. Fix will be available with RC1.

[1] https://github.com/wso2/analytics-esb/pull/46

Comment by Chankami Maddumage [ 22/Jul/16 ]

Hi Chanka,

Noted

Cheers,
Chankami





[ESBJAVA-4761] MQTT Performance Issue Created: 15/Jul/16  Updated: 22/Jul/16  Resolved: 22/Jul/16

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

Type: Bug Priority: Highest
Reporter: dushan abeyruwan Assignee: Eranda Rajapakshe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   
ID: [-1234] [] [2016-07-15 14:08:46,822]  INFO {org.apache.synapse.mediators.builtin.LogMediator} -  mqttURL############################## = mqtt:/xxxx?mqtt.connection.factory=mqttFactory&mqtt.server.host.name=xxxx&mqtt.server.port=1885&mqtt.subscription.username=admin&mqtt.subscription.password=admin&mqtt.client.id=xxxx&mqtt.subscription.qos=0&mqtt.topic.name=carbon.super/retailnext/xxx/data {org.apache.synapse.mediators.builtin.LogMediator}
TID: [-1234] [] [2016-07-15 14:08:46,822]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connecting to null with client ID esb-bt-cloud-test-2 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:08:46,823]  INFO {org.apache.synapse.mediators.builtin.LogMediator} -  mqttURL############################## = mqtt:/yyy?mqtt.connection.factory=mqttFactory&mqtt.server.host.name=yyyy&mqtt.server.port=1885&mqtt.subscription.username=admin&mqtt.subscription.password=admin&mqtt.client.id=yyyyy&mqtt.subscription.qos=0&mqtt.topic.name=carbon.super/retailnext/yyyyyy/data {org.apache.synapse.mediators.builtin.LogMediator}
TID: [-1234] [] [2016-07-15 14:08:46,824]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connecting to null with client ID esb-bt-cloud-test-2 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:08:46,825]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:08:46,825] ERROR {org.apache.axis2.transport.mqtt.MqttSender} -  Exception occured at sending message {org.apache.axis2.transport.mqtt.MqttSender}
Client is not connected (32104)
	at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
	at org.eclipse.paho.client.mqttv3.internal.ClientComms.sendNoWait(ClientComms.java:132)
	at org.eclipse.paho.client.mqttv3.MqttAsyncClient.publish(MqttAsyncClient.java:785)
	at org.apache.axis2.transport.mqtt.MqttAsyncCallback$Publisher.doPublish(MqttAsyncCallback.java:272)
	at org.apache.axis2.transport.mqtt.MqttAsyncCallback.publish(MqttAsyncCallback.java:80)
	at org.apache.axis2.transport.mqtt.MqttSender.sendMessage(MqttSender.java:131)
	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:542)
	at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:79)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:461)
	at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:372)
	at org.apache.synapse.endpoints.DefaultEndpoint.send(DefaultEndpoint.java:77)
	at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:105)
	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.filters.FilterMediator.mediate(FilterMediator.java:160)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
	at org.apache.synapse.mediators.eip.splitter.IterateMediator.mediate(IterateMediator.java:241)
	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)
TID: [-1] [] [2016-07-15 14:08:46,825]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:08:46,827]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  connect failedConnection lost (32109) - java.io.EOFException {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:08:46,827] ERROR {org.apache.axis2.transport.mqtt.MqttSender} -  Exception occured at sending message {org.apache.axis2.transport.mqtt.MqttSender}
Connection lost (32109) - java.io.EOFException
	at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:138)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException
	at java.io.DataInputStream.readByte(DataInputStream.java:267)
	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:56)
	at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:100)
	... 1 more
TID: [-1] [] [2016-07-15 14:08:46,831]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:08:46,832] ERROR {org.apache.axis2.transport.mqtt.MqttSender} -  Exception occured at sending message {org.apache.axis2.transport.mqtt.MqttSender}
Client is not connected (32104)
	at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:27)
	at org.eclipse.paho.client.mqttv3.internal.ClientComms.sendNoWait(ClientComms.java:132)
	at org.eclipse.paho.client.mqttv3.MqttAsyncClient.publish(MqttAsyncClient.java:785)
	at org.apache.axis2.transport.mqtt.MqttAsyncCallback$Publisher.doPublish(MqttAsyncCallback.java:272)
	at org.apache.axis2.transport.mqtt.MqttAsyncCallback.publish(MqttAsyncCallback.java:80)
	at org.apache.axis2.transport.mqtt.MqttSender.sendMessage(MqttSender.java:131)
	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:542)
	at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:79)
	at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:461)
	at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:372)
	at org.apache.synapse.endpoints.DefaultEndpoint.send(DefaultEndpoint.java:77)
	at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:105)
	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.filters.FilterMediator.mediate(FilterMediator.java:160)
	at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
	at org.apache.synapse.mediators.eip.splitter.IterateMediator.mediate(IterateMediator.java:241)
	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)
TID: [-1] [] [2016-07-15 14:08:46,832]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:08:46,832]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:08:46,835]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  message delivered .. : org.eclipse.paho.client.mqttv3.MqttDeliveryToken@7631c9a8 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:08:46,835]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Publish Completed {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:08:46,835]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Disconnecting {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:08:46,836]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Disconnect Completed {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
ata {org.apache.synapse.mediators.builtin.LogMediator}
TID: [-1234] [] [2016-07-15 14:09:16,115]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connecting to null with client ID esb-bt-cloud-test-2 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
ta {org.apache.synapse.mediators.builtin.LogMediator}
TID: [-1234] [] [2016-07-15 14:09:16,116]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connecting to null with client ID esb-bt-cloud-test-2 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:16,121]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  connect failedConnection lost (32109) - java.io.EOFException {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:09:16,121] ERROR {org.apache.axis2.transport.mqtt.MqttSender} -  Exception occured at sending message {org.apache.axis2.transport.mqtt.MqttSender}
Connection lost (32109) - java.io.EOFException
	at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:138)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException
	at java.io.DataInputStream.readByte(DataInputStream.java:267)
	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:56)
	at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:100)
	... 1 more
TID: [-1] [] [2016-07-15 14:09:16,123]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:16,128]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  message delivered .. : org.eclipse.paho.client.mqttv3.MqttDeliveryToken@613984b0 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:16,128]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Publish Completed {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:09:16,132]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Disconnecting {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:16,133]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Disconnect Completed {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:09:17,290]  INFO {org.apache.synapse.mediators.builtin.LogMediator} -  ata {org.apache.synapse.mediators.builtin.LogMediator}
TID: [-1234] [] [2016-07-15 14:09:17,291]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connecting to null with client ID esb-bt-cloud-test-2 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:17,295]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Connected {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:17,298]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  message delivered .. : org.eclipse.paho.client.mqttv3.MqttDeliveryToken@19fd4c45 {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:17,298]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Publish Completed {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1234] [] [2016-07-15 14:09:17,298]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Disconnecting {org.apache.axis2.transport.mqtt.MqttAsyncCallback}
TID: [-1] [] [2016-07-15 14:09:17,299]  INFO {org.apache.axis2.transport.mqtt.MqttAsyncCallback} -  Disconnect Completed {org.apache.axis2.transport.mqtt.MqttAsyncCallback}


 Comments   
Comment by Eranda Rajapakshe [ 22/Jul/16 ]

Issues when concurrently accessing MQTT sender was resolved with this[1] commit.

[1]. https://github.com/wso2/wso2-axis2-transports/commit/dee6e5e9c2f9fbff10304d3ddd470a2586e0c93c





[ESBJAVA-4739] [ IBM JDK 8 / MySql] Unable to start ESB with IBM JDK 8 when registry mounted and pointed to Mysql 5.7 Created: 08/Jul/16  Updated: 21/Jul/16  Resolved: 21/Jul/16

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

Type: Bug Priority: Highest
Reporter: Pubudu D.P Assignee: Balasubramaniyam Senduran
Resolution: Fixed 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:-
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled)

DB:- MySql 5.7


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

 Description   

Pre- Conditions:-

  • Configure the DB with MySql 5.7 and run mysql5.7.sql script manually
  • Mount the registry

1. Go to [$HOME]/bin
2. Start the server and observe

Expected Results:-

  • ESB server should be successfully started

Actual Results:-

  • The following exception is triggered
  • ESB is not started

[2016-07-08 11:28:06,974]  INFO - SolrClient Default Embedded Solr Server Initialized
[2016-07-08 11:28:07,379]  INFO - UserStoreMgtDSComponent Carbon UserStoreMgtDSComponent activated successfully.
[2016-07-08 11:28:14,651]  INFO - TaglibUriRule TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined
[2016-07-08 11:28:14,830]  ERROR - StandardContext Exception sending context initialized event to listener instance of class org.owasp.csrfguard.CsrfGuardServletContextListener 
java.lang.RuntimeException: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at org.owasp.csrfguard.config.PropertiesConfigurationProviderFactory.retrieveConfiguration(PropertiesConfigurationProviderFactory.java:34)
	at org.owasp.csrfguard.config.overlay.ConfigurationAutodetectProviderFactory.retrieveConfiguration(ConfigurationAutodetectProviderFactory.java:73)
	at org.owasp.csrfguard.CsrfGuard.retrieveNewConfig(CsrfGuard.java:112)
	at org.owasp.csrfguard.CsrfGuard.config(CsrfGuard.java:86)
	at org.owasp.csrfguard.CsrfGuard.isPrintConfig(CsrfGuard.java:685)
	at org.owasp.csrfguard.CsrfGuardServletContextListener.printConfigIfConfigured(CsrfGuardServletContextListener.java:97)
	at org.owasp.csrfguard.CsrfGuardServletContextListener.contextInitialized(CsrfGuardServletContextListener.java:86)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
	at java.util.concurrent.FutureTask.run(FutureTask.java:277)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.lang.Thread.run(Thread.java:785)
Caused by: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at org.owasp.csrfguard.config.PropertiesConfigurationProvider.<init>(PropertiesConfigurationProvider.java:234)
	at org.owasp.csrfguard.config.PropertiesConfigurationProviderFactory.retrieveConfiguration(PropertiesConfigurationProviderFactory.java:32)
	... 15 more
Caused by: java.security.NoSuchAlgorithmException: no such algorithm: SHA1PRNG for provider SUN
	at sun.security.jca.GetInstance.getService(GetInstance.java:99)
	at sun.security.jca.GetInstance.getInstance(GetInstance.java:218)
	at java.security.SecureRandom.getInstance(SecureRandom.java:342)
	at org.owasp.csrfguard.config.PropertiesConfigurationProvider.<init>(PropertiesConfigurationProvider.java:121)
	... 16 more
[2016-07-08 11:28:14,832] ERROR - StandardContext One or more listeners failed to start. Full details will be found in the appropriate container log file
[2016-07-08 11:28:14,833] ERROR - StandardContext Context [/] startup failed due to previous errors


Note:-

  • Same set up gets successfully started when pointed to Oracle JDK 1.8
  • Stand alone pack gets started successfully with IBM JDK 8


 Comments   
Comment by Pubudu D.P [ 08/Jul/16 ]

Similar issue found for MSSQL : ESBJAVA-4740

Comment by Ayoma Wijethunga [ 08/Jul/16 ]

In CSRFGuard configuration file available at /repository/conf/security/Owasp.CsrfGuard.Carbon.dashboard.properties, please check below configuration key. It should be changed to "IBMJCE" for IBM JDK.

# WSO2 - Pseudo-random number generator provider should be configured based on 
# environment (SUN/IBMJCE)
org.owasp.csrfguard.PRNG.Provider=IBMJCE
Comment by Pubudu D.P [ 11/Jul/16 ]

Hi Ayoma,

I have tried the suggested tweak and it did not fix the issue. ESB starts with the same exception. Can you please take a look if we need to do any other configs for this to work?

Cheers,
Pubudu.

Comment by Jagath Ariyarathne [ 21/Jul/16 ]

Tested with ESB 5.0.0 BETA2 pack. It solves the issue by applying above property.





[ESBJAVA-4777] Support transport.jms.ConcurrentConsumers in inbound endpoint Created: 21/Jul/16  Updated: 21/Jul/16  Resolved: 21/Jul/16

Status: Resolved
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: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

We can set concurrent consumers for the jms Endpoints. Need to add this capability for the inbound endpoints too.



 Comments   
Comment by Nadeeshaan Gunasinghe [ 21/Jul/16 ]

https://wso2.org/jira/browse/ESBJAVA-4722





[ESBJAVA-4724] Client does not received the message return by the fault sequence Created: 04/Jul/16  Updated: 20/Jul/16  Resolved: 20/Jul/16

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

Type: Bug Priority: Normal
Reporter: Tharanga Wijeweera Assignee: Chanaka Fernando
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Re-producing steps:

1. Created the following API with the sequences

 <api xmlns="http://ws.apache.org/ns/synapse" name="test" context="/test">
   <resource methods="POST" inSequence="abc" faultSequence="FaultSequence-v1 "/>
</api>
<?xml version="1.0" encoding="UTF-8"?>
<sequence name="abc" onError="FaultSequence-v1" xmlns="http://ws.apache.org/ns/synapse">
    <log level="custom">
        <property name="testLog" value="========================================"/>
    </log>
    <log level="full"/>
    <drop/>
</sequence>
<?xml version="1.0" encoding="UTF-8"?>
<sequence name="FaultSequence-v1" trace="disable" xmlns="http://ws.apache.org/ns/synapse">
    <log level="custom">
        <property name="00000000000000000000000000" value="."/>
    </log>
    <property action="remove" name="TRANSPORT_HEADERS" scope="axis2"/>
    <payloadFactory media-type="json">
        <format>{"errors": {"error_code": "ESB-1080","error_description":"Exception occurred while processing request. Please try again. If problem persists, please contact support."}}</format>
    </payloadFactory>
    <property name="messageType" scope="axis2" value="application/json"/>
    <respond/>
</sequence>

2. Invoked the API using following CURL with the attachment (test.png)

curl -X POST -H "X-JWT-Assertion: <Token>" "http://localhost:8280/test?chunk=false" --data-binary @./test.png -k -v

Observations:
1. It executed the fault sequence (FaultSequence-v1) due to following error

java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1911)
	at org.apache.synapse.commons.builders.XFormURLEncodedBuilder.extractParametersFromRequest(XFormURLEncodedBuilder.java:223)
	at org.apache.synapse.commons.builders.XFormURLEncodedBuilder.processDocumentWrapper(XFormURLEncodedBuilder.java:128)

2. Even it hit to fault sequence, the message inside the fault sequence was not returned.



 Comments   
Comment by Balasubramaniyam Senduran [ 20/Jul/16 ]

Fix is merged in https://github.com/wso2/wso2-synapse/commit/2c8fa39618590b1e40da7f35788ece08f3262e22

Comment by Balasubramaniyam Senduran [ 20/Jul/16 ]

The fix can be verify by posting different size of binary data, without the fix , data larger than 16 k will not get response.

curl -X POST "http://localhost:8280/test" --data-binary @test1.png -k -v





[ESBJAVA-4423] Custom status message descriptions in response, are not retained when using the passthrough transport Created: 17/Feb/16  Updated: 20/Jul/16  Resolved: 20/Jul/16

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

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

Attachments: File KERNEL-441.diff    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When a custom status message is used, it get replaced by the default status message when going through esb.



 Comments   
Comment by Vinod Kavinda [ 24/Feb/16 ]

Fixed in https://github.com/wso2/wso2-synapse/pull/466
Tests available in https://github.com/wso2/product-esb/pull/452

Comment by Ravi Undupitiya [ 20/Jul/16 ]

Fix does not work in tenant mode. This case is fixed with attached diff.

Comment by Ravi Undupitiya [ 20/Jul/16 ]

PR to 4.4.x with tenant fix https://github.com/wso2/carbon-kernel/pull/1086

Comment by Ananda Manoj Kumara [ 20/Jul/16 ]

Merged with b4aa7c0087c864d85e666f2530f11506074e6206





[ESBJAVA-4673] Follow consistent naming for ESB runtime, tooling and analytics Created: 13/Jun/16  Updated: 20/Jul/16  Due: 30/Jun/16  Resolved: 20/Jul/16

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

Type: Improvement Priority: Highest
Reporter: Lakshika Paiva Assignee: Viraj Rajaguru
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

As per chat, the download file name on GitHub for ESB 5 (GA) tooling and analytics need to be correct and consistent with the runtime, unlike in ESB 5 beta.

Here is how it should be:

WSO2 ESB 5.0.0 - wso2esb-5.0.0.zip
WSO2 ESB Tooling 5.0.0 - wso2esb-tooling-5.0.0.zip
WSO2 ESB Analytics 5.0.0 - wso2esb-analytics-5.0.0.zip

This may affect all products which do not follow this pattern.



 Comments   
Comment by Chanaka Fernando [ 20/Jul/16 ]

We have a concern here with the naming for ESB tooling component since we have multiple distributions with the tooling. Here are the distributions.

wso2esb-tooling-composite-p2-5.0.0-BETA2.zip
wso2esb-tooling-eclipse-jee-mars-linux-gtk-5.0.0-BETA2.zip
wso2esb-tooling-eclipse-jee-mars-linux-gtk-x86_64-5.0.0-BETA2.zip
wso2esb-tooling-eclipse-jee-mars-macosx-cocoa-x86_64-5.0.0-BETA2.zip
wso2esb-tooling-eclipse-jee-mars-win32-5.0.0-BETA2.zip
wso2esb-tooling-eclipse-jee-mars-win64-x86_64-5.0.0-BETA2.zip
wso2esb-tooling-main-p2-5.0.0-BETA2.zip

Here the names in between the version and the term "tooling" are required to demonstrate the relevant package.

ESB[1] and Analytics[2] components are already renamed for the required structure with beta2 release. Tooling component names will stay as it is mentioned above.

[1] https://github.com/wso2/analytics-esb/releases

[2] https://github.com/wso2/product-esb/releases





[ESBJAVA-4393] Message Processor deployed via a capp can not be reactivated, once it is automatically deactivated after reaching the max delivery attempts Created: 28/Jan/16  Updated: 20/Jul/16  Resolved: 20/Jul/16

Status: Resolved
Project: WSO2 ESB
Component/s: Message Processors
Affects Version/s: 4.8.1
Fix Version/s: 4.9.0

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

Attachments: XML File Proxy1.xml     File mpissue_1.0.0.car     File wso2carbon.log.2016-01-27    
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   

Create a Message Processor, store and proxy service setup using a capp. You may need to point the Message processor to some endpoint which returns some error HTTP SC such as 404, 400, 500 etc and let it retry till it deactivates automatically. Then the MP deactivates. After that shut down the ESB. Go to the Active MQ console and remove the queue. Then restart the ESB. You may see that the MP is still in deactivated mode. When you reactivate the MP you will get the following error in ESB console.

TID: [0] [ESB] [2016-01-18 14:12:46,812] ERROR

{org.wso2.carbon.message.processor.service.MessageProcessorAdminService} - Error While accessing MessageProcessor view {org.wso2.carbon.message.processor.service.MessageProcessorAdminService}

TID: [0] [ESB] [2016-01-18 14:12:46,813] ERROR

{org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} - Exception occurred while trying to invoke service method activate {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver}

org.apache.axis2.AxisFault
at org.wso2.carbon.message.processor.service.MessageProcessorAdminService.activate(MessageProcessorAdminService.java:526)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.wso2.carbon.message.processor.stub.MessageProcessorAdminServiceStub.activate(MessageProcessorAdminServiceStub.java:503)
at org.wso2.carbon.message.processor.ui.MessageProcessorAdminServiceClient.activate(MessageProcessorAdminServiceClient.java:343)
at org.apache.jsp.message_005fprocessor.ScheduledProcessorActionHandler_jsp._jspService(org.apache.jsp.message_005fprocessor.ScheduledProcessorActionHandler_jsp:88)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
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:848)
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:848)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
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:749)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:605)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:544)
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:1015)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:700)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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(org.apache.jsp.admin.layout.template_jsp:603)
at org.apache.jsp.admin.layout.template_jsp._jspService(org.apache.jsp.admin.layout.template_jsp:335)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
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:848)
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:848)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
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:749)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
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:848)
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:848)
at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
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:222)
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:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
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:1004)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)



 Comments   
Comment by Ravindra Ranwala [ 28/Jan/16 ]

The fix is attached.

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

Can you please send a pull request ?

Comment by Chanaka Fernando [ 29/Jun/16 ]

@Ravindra: Please attach the PR to the ticket.

Comment by Ravindra Ranwala [ 20/Jul/16 ]

The issue was solved from this pr [1]. Also the issue is related to jira [2]. Since ESB 4.9.0 we are not persisting the state during deactivation and upon restart the MP keeps running. The issue is resolved since the PR [1] is already merged into the public branch.

[1] https://github.com/ravindraranwala/wso2-synapse/commit/629da0bf167904173a1eda81e16db3009aa50c21
[2] https://wso2.org/jira/browse/ESBJAVA-3239





[ESBJAVA-3903] NPE when invoking a producer proxy with rabbitmq.replyto.name property [RabbitMQ] Created: 14/Jul/15  Updated: 20/Jul/16  Resolved: 20/Jul/16

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

Type: Bug Priority: High
Reporter: Asanthi Kulasinghe Assignee: Maheeka Jayasuriya
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB 4.9.0
Operating System :Ubuntu 13.04
Java Version : 1.7.0


Attachments: XML File AMQPProxy_ESB_as_a_consumer.xml     XML File AMQPProxy_ESB_producer_with_reply_queue.xml     XML File AMQPProxy_listen_and_publish.xml    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Proxy 'AMQPProxy_ESB_producer_with_reply_queue' publishes a message on a queue and expects a reply on the queue referred to by the 'rabbitmq.replyto.name' endpoint uri property.
Proxy 'AMQPProxy_ESB_as_a_consumer' listens to the queue which the above proxy publishes the message to, forwards the message to the specified backend endpoint and publishes the response on the queue specified by the 'rabbitmq.replyto.name' property of the publisher proxy.

The following exception occurs when 'AMQPProxy_ESB_producer_with_reply_queue' proxy is invoked.

(Invocation of a proxy which listens to the queue, forwards the message to a backend endpoint and publishes the response on a different queue is successful : Attached - AMQPProxy_listen_and_publish.xml)

curl -v -X POST -d @/home/kaushie/WSO2PRODUCTS/APIM/Desktop/hello "http://localhost:8280/services/AMQPProxy_ESB_producer_with_reply_queue" -H "SOAPAction: urn::greet" -H "Content-Type: text/xml"
curl: /usr/local/lib/libldap_r-2.4.so.2: no version information available (required by /usr/lib/x86_64-linux-gnu/libcurl.so.4)
curl: /usr/local/lib/liblber-2.4.so.2: no version information available (required by /usr/lib/x86_64-linux-gnu/libcurl.so.4)

  • About to connect() to localhost port 8280 (#0)
  • Trying 127.0.0.1...
  • Connected to localhost (127.0.0.1) port 8280 (#0)
    > POST /services/AMQPProxy_ESB_producer_with_reply_queue HTTP/1.1
    > User-Agent: curl/7.29.0
    > Host: localhost:8280
    > Accept: /
    > SOAPAction: urn::greet
    > Content-Type: text/xml
    > Content-Length: 275
    >
  • upload completely sent off: 275 out of 275 bytes

________________________________________________________________

[2015-07-14 15:04:26,969] DEBUG - wire >> "POST /services/AMQPProxy_ESB_producer_with_reply_queue HTTP/1.1[\r][\n]"
[2015-07-14 15:04:26,970] DEBUG - wire >> "User-Agent: curl/7.29.0[\r][\n]"
[2015-07-14 15:04:26,970] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
[2015-07-14 15:04:26,970] DEBUG - wire >> "Accept: /[\r][\n]"
[2015-07-14 15:04:26,970] DEBUG - wire >> "SOAPAction: urn::greet[\r][\n]"
[2015-07-14 15:04:26,970] DEBUG - wire >> "Content-Type: text/xml[\r][\n]"
[2015-07-14 15:04:26,971] DEBUG - wire >> "Content-Length: 275[\r][\n]"
[2015-07-14 15:04:26,971] DEBUG - wire >> "[\r][\n]"
[2015-07-14 15:04:26,971] DEBUG - wire >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.wso2.org/types"> <soapenv:Header/> <soapenv:Body> <typ:greet> <name>----------KAUSHIE--------</name> </typ:greet> </soapenv:Body></soapenv:Envelope>"
[2015-07-14 15:04:26,978] DEBUG - headers http-incoming-1 >> POST /services/AMQPProxy_ESB_producer_with_reply_queue HTTP/1.1
[2015-07-14 15:04:26,979] DEBUG - headers http-incoming-1 >> User-Agent: curl/7.29.0
[2015-07-14 15:04:26,979] DEBUG - headers http-incoming-1 >> Host: localhost:8280
[2015-07-14 15:04:26,979] DEBUG - headers http-incoming-1 >> Accept: /
[2015-07-14 15:04:26,979] DEBUG - headers http-incoming-1 >> SOAPAction: urn::greet
[2015-07-14 15:04:26,979] DEBUG - headers http-incoming-1 >> Content-Type: text/xml
[2015-07-14 15:04:26,979] DEBUG - headers http-incoming-1 >> Content-Length: 275
[2015-07-14 15:04:27,051] INFO - LogMediator To: /services/AMQPProxy_ESB_producer_with_reply_queue, WSAction: urn::greet, SOAPAction: urn::greet, MessageID: urn:uuid:8105b690-ff88-4144-9fd1-59660f8398cb, Direction: request, producer = ****************************** PRODUCER ***************************, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.wso2.org/types"><soapenv:Body> <typ:greet> <name>----------KAUSHIE--------</name> </typ:greet> </soapenv:Body></soapenv:Envelope>
[2015-07-14 15:04:27,061] INFO - TimeoutHandler This engine will expire all callbacks after : 120 seconds, irrespective of the timeout action, after the specified or optional timeout
[2015-07-14 15:04:27,069] INFO - RabbitMQConnectionFactory RabbitMQ ConnectionFactory : localhost_5672_guest_guest_null_null_null_null_null_null_null initialized
[2015-07-14 15:04:27,123] INFO - LogMediator To: , WSAction: urn::greet, SOAPAction: urn::greet, MessageID: urn:uuid:1C4ACE8F7D87E993FA1436866467109, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.wso2.org/types"><soapenv:Body> <typ:greet> <name>----------KAUSHIE--------</name> </typ:greet> </soapenv:Body></soapenv:Envelope>
[2015-07-14 15:04:27,145] INFO - RabbitMQConnectionFactory [localhost_5672_guest_guest_null_null_null_null_null_null_null] Successfully connected to RabbitMQ Broker
[2015-07-14 15:04:27,170] ERROR - Axis2Sender Unexpected error during sending message out
java.lang.NullPointerException
at org.apache.axis2.transport.rabbitmq.RabbitMQSender.processResponse(RabbitMQSender.java:145)
at org.apache.axis2.transport.rabbitmq.RabbitMQSender.sendOverAMQP(RabbitMQSender.java:103)
at org.apache.axis2.transport.rabbitmq.RabbitMQSender.sendMessage(RabbitMQSender.java:88)
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:514)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:76)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:437)
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:105)
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:138)
at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:183)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:387)
at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:139)
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)
[2015-07-14 15:04:27,178] WARN - EndpointContext Endpoint : AnonymousEndpoint will be marked SUSPENDED as it failed
[2015-07-14 15:04:27,178] WARN - EndpointContext Suspending endpoint : AnonymousEndpoint - current suspend duration is : 30000ms - Next retry after : Tue Jul 14 15:04:57 IST 2015
[2015-07-14 15:04:27,184] INFO - LogMediator To: /services/AMQPProxy_ESB_producer_with_reply_queue, WSAction: urn::greet, SOAPAction: urn::greet, MessageID: urn:uuid:8105b690-ff88-4144-9fd1-59660f8398cb, Direction: request, 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://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.wso2.org/types"><soapenv:Body> <typ:greet> <name>----------KAUSHIE--------</name> </typ:greet> </soapenv:Body></soapenv:Envelope>
[2015-07-14 15:04:27,188] DEBUG - headers http-outgoing-1 >> POST /services/HelloService/ HTTP/1.1
[2015-07-14 15:04:27,188] DEBUG - headers http-outgoing-1 >> rabbitmq.message.correlation.id: urn:uuid:855cc83f-71ba-4d0e-b945-186e095f283e
[2015-07-14 15:04:27,188] DEBUG - headers http-outgoing-1 >> rabbitmq.message.id: urn:uuid:855cc83f-71ba-4d0e-b945-186e095f283e
[2015-07-14 15:04:27,189] DEBUG - headers http-outgoing-1 >> RABBITMQ_REPLY_TO: replySampleQueue
[2015-07-14 15:04:27,189] DEBUG - headers http-outgoing-1 >> Content-Type: text/xml; charset=UTF-8
[2015-07-14 15:04:27,189] DEBUG - headers http-outgoing-1 >> SOAPAction: "urn::greet"
[2015-07-14 15:04:27,189] DEBUG - headers http-outgoing-1 >> Transfer-Encoding: chunked
[2015-07-14 15:04:27,190] DEBUG - headers http-outgoing-1 >> Host: 10.100.5.40:9773
[2015-07-14 15:04:27,190] DEBUG - headers http-outgoing-1 >> Connection: Keep-Alive
[2015-07-14 15:04:27,190] DEBUG - headers http-outgoing-1 >> User-Agent: Synapse-PT-HttpComponents-NIO
[2015-07-14 15:04:27,193] DEBUG - wire << "POST /services/HelloService/ HTTP/1.1[\r][\n]"
[2015-07-14 15:04:27,193] DEBUG - wire << "rabbitmq.message.correlation.id: urn:uuid:855cc83f-71ba-4d0e-b945-186e095f283e[\r][\n]"
[2015-07-14 15:04:27,193] DEBUG - wire << "rabbitmq.message.id: urn:uuid:855cc83f-71ba-4d0e-b945-186e095f283e[\r][\n]"
[2015-07-14 15:04:27,194] DEBUG - wire << "RABBITMQ_REPLY_TO: replySampleQueue[\r][\n]"
[2015-07-14 15:04:27,194] DEBUG - wire << "Content-Type: text/xml; charset=UTF-8[\r][\n]"
[2015-07-14 15:04:27,194] DEBUG - wire << "SOAPAction: "urn::greet"[\r][\n]"
[2015-07-14 15:04:27,194] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2015-07-14 15:04:27,194] DEBUG - wire << "Host: 10.100.5.40:9773[\r][\n]"
[2015-07-14 15:04:27,195] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2015-07-14 15:04:27,195] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2015-07-14 15:04:27,195] DEBUG - wire << "[\r][\n]"
[2015-07-14 15:04:27,196] DEBUG - wire << "139[\r][\n]"
[2015-07-14 15:04:27,196] DEBUG - wire << "<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://www.wso2.org/types"> <soapenv:Header/> <soapenv:Body> <typ:greet> <name>----------KAUSHIE--------</name> </typ:greet> </soapenv:Body></soapenv:Envelope>[\r][\n]"
[2015-07-14 15:04:27,196] DEBUG - wire << "0[\r][\n]"
[2015-07-14 15:04:27,196] DEBUG - wire << "[\r][\n]"
[2015-07-14 15:04:27,197] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2015-07-14 15:04:27,197] DEBUG - wire >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2015-07-14 15:04:27,197] DEBUG - wire >> "Transfer-Encoding: chunked[\r][\n]"
[2015-07-14 15:04:27,197] DEBUG - wire >> "Date: Tue, 14 Jul 2015 09:34:27 GMT[\r][\n]"
[2015-07-14 15:04:27,198] DEBUG - wire >> "Server: WSO2 Carbon Server[\r][\n]"
[2015-07-14 15:04:27,199] DEBUG - wire >> "[\r][\n]"
[2015-07-14 15:04:27,200] DEBUG - wire >> "129[\r][\n]"
[2015-07-14 15:04:27,200] DEBUG - wire >> "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:greetResponse xmlns:ns="http://www.wso2.org/types"><return>Hello World, ----------KAUSHIE-------- !!!</return></ns:greetResponse></soapenv:Body></soapenv:Envelope>[\r][\n]"
[2015-07-14 15:04:27,201] DEBUG - headers http-outgoing-1 << HTTP/1.1 200 OK
[2015-07-14 15:04:27,202] DEBUG - headers http-outgoing-1 << Content-Type: text/xml;charset=UTF-8
[2015-07-14 15:04:27,202] DEBUG - headers http-outgoing-1 << Transfer-Encoding: chunked
[2015-07-14 15:04:27,202] DEBUG - headers http-outgoing-1 << Date: Tue, 14 Jul 2015 09:34:27 GMT
[2015-07-14 15:04:27,202] DEBUG - headers http-outgoing-1 << Server: WSO2 Carbon Server
[2015-07-14 15:04:27,208] DEBUG - wire >> "0[\r][\n]"
[2015-07-14 15:04:27,209] DEBUG - wire >> "[\r][\n]"



 Comments   
Comment by Maheeka Jayasuriya [ 19/Jul/16 ]

This is already resolved in latest source.





[ESBJAVA-4242] Performance Improvements to RabbitMQ Created: 30/Sep/15  Updated: 20/Jul/16  Resolved: 20/Jul/16

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

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

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

 Description   

1. Declaring and verifying existence queue/exchange at time of sending impacts performance
2. Connections created for each response listener in request-response request






[ESBJAVA-4241] Some channels are not getting closed after publishing data to the queue with RabbitMQ transport Created: 30/Sep/15  Updated: 20/Jul/16  Resolved: 20/Jul/16

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

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

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

 Description   

When sending a rabbitmq message some channels that are getting created are not cleared afterwards






[ESBJAVA-4757] analytics tenant publishers should be copied to tenant space Created: 15/Jul/16  Updated: 19/Jul/16  Resolved: 19/Jul/16

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

Type: Bug Priority: High
Reporter: Buddhima Wijeweera Assignee: Buddhima Wijeweera
Resolution: Invalid 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   

repository/deployment/server/eventpublishers files need to be copied



 Comments   
Comment by Buddhima Wijeweera [ 18/Jul/16 ]

Completed with: https://github.com/wso2/carbon-mediation/pull/688

This will copy what is available in super-tenant directory when tenant is created

Comment by Buddhima Wijeweera [ 19/Jul/16 ]

This change has been reverted with PR: https://github.com/wso2/carbon-mediation/pull/692





[ESBJAVA-4758] Add a global statistics enabling parameter Created: 15/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

Type: Bug Priority: High
Reporter: Buddhima Wijeweera Assignee: Buddhima Wijeweera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Adding a new parameter to synapse.properties which enable statistics for all artifacts in ESB



 Comments   
Comment by Buddhima Wijeweera [ 18/Jul/16 ]

Adding this functionality from : https://github.com/wso2/wso2-synapse/pull/602





[ESBJAVA-4745] Durable subscription is not working in the JMS Inbound with the MB Created: 08/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

Type: Bug Priority: Highest
Reporter: prabath ariyarathna Assignee: Nuwan Wimalasekara
Resolution: Not a bug Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Comments   
Comment by Nuwan Wimalasekara [ 18/Jul/16 ]

In order to work as durable subscription, you need to set the transport.jms.DurableSubscriberClientID in inbound-endpoint. If you use the same clientId , It will work. Please refer below configuration.

<inboundEndpoint xmlns="http://ws.apache.org/ns/synapse"
name="jms_inbound"
sequence="seq1"
onError="fault"
protocol="jms"
suspend="false">
<parameters>
<parameter name="interval">10</parameter>
<parameter name="sequential">true</parameter>
<parameter name="coordination">true</parameter>
<parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType">topic</parameter>
<parameter name="transport.jms.Destination">mytopic</parameter>
<parameter name="transport.jms.SessionTransacted">false</parameter>
<parameter name="transport.jms.SessionAcknowledgement">AUTO_ACKNOWLEDGE</parameter>
<parameter name="transport.jms.CacheLevel">3</parameter>
<parameter name="transport.jms.SubscriptionDurable">true</parameter>
<parameter name="transport.jms.DurableSubscriberClientID">mySub1</parameter>
<parameter name="transport.jms.DurableSubscriberName">mySub1</parameter>
<parameter name="transport.jms.SharedSubscription">false</parameter>
</parameters>
</inboundEndpoint>

Comment by Nuwan Wimalasekara [ 18/Jul/16 ]

For WSO2 MB refer below configuration

<inboundEndpoint xmlns="http://ws.apache.org/ns/synapse"
name="jms_inbound"
sequence="seq1"
onError="fault"
protocol="jms"
suspend="false">
<parameters>
<parameter name="interval">10</parameter>
<parameter name="sequential">true</parameter>
<parameter name="coordination">true</parameter>
<parameter name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="java.naming.provider.url">repository/conf/jndi.properties</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType">topic</parameter>
<parameter name="transport.jms.Destination">mytopic</parameter>
<parameter name="transport.jms.SessionTransacted">false</parameter>
<parameter name="transport.jms.SessionAcknowledgement">AUTO_ACKNOWLEDGE</parameter>
<parameter name="transport.jms.CacheLevel">3</parameter>
<parameter name="transport.jms.SubscriptionDurable">true</parameter>
<parameter name="transport.jms.DurableSubscriberClientID">mySub1</parameter>
<parameter name="transport.jms.DurableSubscriberName">mySub1</parameter>
<parameter name="transport.jms.SharedSubscription">false</parameter>
</parameters>
</inboundEndpoint>

Configure jndi properties as bellow repository/conf/jndi.properties
connectionfactory.TopicConnectionFactory = amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5673'
topic.mytopic = MyTopic





[ESBJAVA-4768] When using full path in sftp with file locking enabled, files processing gets skipped Created: 18/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

Type: Bug Priority: High
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

In Synapse VFS transport, when we give path relative to root( with url param "sftpPathFromRoot=true") for sftp location and if we enable file locking as well, then files won't get processed.

Only below logs can be seen (debug logs enabled)

[2016-07-13 14:11:34,192] DEBUG - VFSTransportListener Scanning directory or file : sftp://abc":***@"192.168.50.268/in?vfs.passive=true
[2016-07-13 14:11:34,516] DEBUG - VFSTransportListener File name pattern : .*.txt
[2016-07-13 14:11:34,517] DEBUG - VFSTransportListener Matching file : abc.txt
[2016-07-13 14:11:34,557] DEBUG - VFSTransportListener Processing file :sftp://abc":***@"192.168.50.268/in/abc.txt

if works properly there should be a log like below
[2016-07-18 10:18:31,767] DEBUG - VFSTransportListener Processing file :sftp://abc":***@"192.168.50.268/in/abc.xml



 Comments   
Comment by Rajith Vitharana [ 18/Jul/16 ]

Fixed with git commit[1], pull [2] to wso2-synapse master branch

[1] - 52cd34dccafc8df741c942e7c82dc76b9995618a
[2] - https://github.com/wso2/wso2-synapse/pull/603





[ESBJAVA-4770] When using keys with 2048 key strength, password encryption fails in synapse vfs transport Created: 18/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

Type: Bug Priority: High
Reporter: Rajith Vitharana Assignee: Rajith Vitharana
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File openssl-server.cnf    
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When using cipher keys with 2048 key size, password decryption fails in synapse VFS transport.

important key commands are listed below(openssl-server.cnf file is attached herewith)

1 - openssl req -x509 -days 7300 -config openssl-server.cnf -extensions server_req_extensions -newkey rsa:2048 -sha256 -out servercert.pem -outform PEM

2 - openssl pkcs12 -export -in servercert.pem -inkey serverkey.pem -certfile servercert.pem -out vfsKeystore.p12

3 - keytool -importkeystore -srckeystore vfsKeystore.p12 -srcstoretype pkcs12 -destkeystore vfsKeystore.jks -deststoretype JKS

4 - keytool -changealias -keystore vfsKeystore.jks -alias 1

5 - keytool -certreq -v -alias vfs -file vfsCertReq.req -keystore vfsKeystore.jks -ext san=dns:wso2.esb.com -ext eku=sa,ca



 Comments   
Comment by Rajith Vitharana [ 18/Jul/16 ]

Fixed with git commit[1], pull [2] to wso2-synapse master branch

[1] - 52cd34dccafc8df741c942e7c82dc76b9995618a
[2] - https://github.com/wso2/wso2-synapse/pull/603





[ESBJAVA-4773] WSO2 ESB 5.0.0 Beta2 - carbon version is not correct Created: 18/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

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

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

Check the version with following command.

sh wso2server.sh -version

Result is

WSO2 Enterprise Service Bus v5.0.0
WSO2 Carbon Framework v4.4.6

Carbon Framework version should be 4.4.7



 Comments   
Comment by Chanaka Fernando [ 18/Jul/16 ]

Fixed with following PR [1]

[1] https://github.com/wso2/product-esb/commit/5ec726a88e7d23a367ea13354fb9df670109f17a





[ESBJAVA-4762] SAP adaptor missing in plugins directory of 4.9.0 Created: 16/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

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

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

 Description   

Tried to do some SAP IDOC integration but received the following error. On analysis, found the SAP adaptor jar is missing in the WSO2 ESB product.

at java.lang.Thread.run(Thread.java:724)
Caused by: org.apache.axis2.deployment.DeploymentException: org.wso2.carbon.transports.sap.SAPTransportSender cannot be found by axis2_1.6.1.wso2v14
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:712)
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:124)
at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341)
at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192)
... 41 more
Caused by: java.lang.ClassNotFoundException: org.wso2.carbon.transports.sap.SAPTransportSender cannot be found by axis2_1.6.1.wso2v14
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:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:686)
... 44 more



 Comments   
Comment by Chanaka Fernando [ 18/Jul/16 ]

Fixed with following PR[1]

https://github.com/wso2/product-esb/commit/997d3929944ebc23351f33077f805b6df4393181





[ESBJAVA-4263] Message processor always deactivate. Created: 11/Oct/15  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

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

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

 Description   

Steps to reproduce:

1. set up sample https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber

2. Shutdown the backend-1

3. Send request.

4. Start the backend-1 before exceed the max.delivery.attempts count.

5. The message in the store will process but message processor going to deactivate.



 Comments   
Comment by Nuwan Wimalasekara [ 18/Jul/16 ]

The sample configuration need to be updated with correct configuration. We will update the configuration.

If the backend send a response, Message Processor expect a replySeq. If we have not defined it with send mediator, Message Processor will be deactivated. So defining reply seq will refrain message processor deactivation.

<send receive="replySeq" xmlns:ns="http://org.apache.synapse/xsd">
<endpoint name="Subscriber 1">
<address uri="http://localhost:9000/services/SimpleStockQuoteService/"/>
</endpoint>
</send>

Otherwise you have to set OUT_ONLY to true. Then ESB does not expect a response from backend.

<property name="OUT_ONLY" value="true"/>
<send xmlns:ns="http://org.apache.synapse/xsd">
<endpoint name="Subscriber 1">
<address uri="http://localhost:9000/services/SimpleStockQuoteService/"/>
</endpoint>
</send>





[ESBJAVA-4771] No Error is shown in ESB Console when Referring to a non existing Sequence Template Created: 18/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

Type: Bug Priority: Normal
Reporter: Nadeeshaan Gunasinghe Assignee: Nadeeshaan Gunasinghe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   
<proxy xmlns="http://ws.apache.org/ns/synapse"  name="TemplateTest" transports="https,http">
   <target>
      <inSequence>
         <log level="custom">
            <property name="msg" value="before"/>
         </log>
         <call-template target="cool"/>
         <log level="custom">
            <property name="msg" value="ok"/>
         </log>
      </inSequence>
      <faultSequence>
         <log level="custom">
            <property name="msg" value="not ok"/>
         </log>
      </faultSequence>
   </target>
   <description/>
</proxy>

Here the template cool is a non existing template and when invoking the proxy it does not shows any error message in the console or even do not execute the fault sequence



 Comments   
Comment by Nadeeshaan Gunasinghe [ 18/Jul/16 ]

This particular issue is fixed with the following fix.

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

Thanks,
Nadeeshaan.





[ESBJAVA-4698] ESB does not send the response body to the client, if the response does not contain the Content-Length and Content-Type. Created: 22/Jun/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

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

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

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

 Description   

In this case, ESB sends sends the response to the client with Content Type 'application/xml' and an empty payload. Please find the wire log [1].

[1] -
[2016-06-22 13:24:17,235] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "POST /testFile1.txt?uploads HTTP/1.1[\r][\n]"
[2016-06-22 13:24:17,235] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "x-amz-date: Wed, 22 Jun 2016 07:54:16 GMT[\r][\n]"
[2016-06-22 13:24:17,235] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "x-amz-storage-class: STANDARD[\r][\n]"
[2016-06-22 13:24:17,236] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Cookie: lang=en[\r][\n]"
[2016-06-22 13:24:17,236] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "x-amz-server-side-encryption: AES256[\r][\n]"
[2016-06-22 13:24:17,236] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Origin: chrome-extension://fdmmgilgnpjigdojojpjoooidkmcomcm[\r][\n]"
[2016-06-22 13:24:17,237] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Cache-Control: no-cache[\r][\n]"
[2016-06-22 13:24:17,237] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Accept-Language: en-US,en;q=0.8[\r][\n]"
[2016-06-22 13:24:17,237] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Authorization: xxxxxxxxxx[\r][\n]"
[2016-06-22 13:24:17,237] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Action: urn:initMultipartUpload[\r][\n]"
[2016-06-22 13:24:17,238] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Accept-Encoding: gzip, deflate[\r][\n]"
[2016-06-22 13:24:17,238] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Content-Type: application/xml[\r][\n]"
[2016-06-22 13:24:17,238] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Accept: /[\r][\n]"
[2016-06-22 13:24:17,238] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "x-amz-meta-: Content-Language:enus[\r][\n]"
[2016-06-22 13:24:17,238] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Transfer-Encoding: chunked[\r][\n]"
[2016-06-22 13:24:17,239] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Host: bucketName.s3-us-west-2.amazonaws.com[\r][\n]"
[2016-06-22 13:24:17,239] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "Connection: Keep-Alive[\r][\n]"
[2016-06-22 13:24:17,239] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-22 13:24:17,239] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "[\r][\n]"
[2016-06-22 13:24:17,239] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "0[\r][\n]"
[2016-06-22 13:24:17,240] DEBUG - wire HTTP-Sender I/O dispatcher-7 << "[\r][\n]"
[2016-06-22 13:24:17,549] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "HTTP/1.1 200 OK[\r][\n]"
[2016-06-22 13:24:17,549] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "x-amz-id-2: MoN1KJkqGdlgmCqoE+41P5OuIOgjVUBdjfcsKZ0/kXhAKyXok6Oze/hYbtVJ8aQ1IPh7OjEAptc=[\r][\n]"
[2016-06-22 13:24:17,550] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "x-amz-request-id: 97D13A3633DF8A8B[\r][\n]"
[2016-06-22 13:24:17,550] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "Date: Wed, 22 Jun 2016 07:54:19 GMT[\r][\n]"
[2016-06-22 13:24:17,550] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "x-amz-server-side-encryption: AES256[\r][\n]"
[2016-06-22 13:24:17,550] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "Transfer-Encoding: chunked[\r][\n]"
[2016-06-22 13:24:17,550] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "Server: AmazonS3[\r][\n]"
[2016-06-22 13:24:17,550] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "[\r][\n]"
[2016-06-22 13:24:17,551] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "16c[\r][\n]"
[2016-06-22 13:24:17,552] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "<?xml version="1.0" encoding="UTF-8"?>[\n]"
[2016-06-22 13:24:17,552] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "<InitiateMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Bucket>1466507117851testconbkt2</Bucket><Key>testFile1.txt</Key><UploadId>AZ44p4ySf0oNFg6Hg6.0ojiUKPaGXMNyGq3IdYiw2wwbygt6KWd_cMX2CbzGjJjEX5NcTIoLtjzp2rBy40YKtVfVtmGCxPtXRxNs_PW.5GNaEs07RHEMAERCWFAZR297</UploadId></InitiateMultipartUploadResult>[\r][\n]"
[2016-06-22 13:24:17,552] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "0[\r][\n]"
[2016-06-22 13:24:17,553] DEBUG - wire HTTP-Sender I/O dispatcher-7 >> "[\r][\n]"
[2016-06-22 13:24:17,555] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "HTTP/1.1 200 OK[\r][\n]"
[2016-06-22 13:24:17,556] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2016-06-22 13:24:17,556] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "Date: Wed, 22 Jun 2016 07:54:17 GMT[\r][\n]"
[2016-06-22 13:24:17,556] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "Transfer-Encoding: chunked[\r][\n]"
[2016-06-22 13:24:17,556] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "Connection: keep-alive[\r][\n]"
[2016-06-22 13:24:17,557] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "[\r][\n]"
[2016-06-22 13:24:17,557] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "0[\r][\n]"
[2016-06-22 13:24:17,557] DEBUG - wire HTTP-Listener I/O dispatcher-6 << "[\r][\n]"



 Comments   
Comment by Malaka Silva [ 22/Jun/16 ]

Seems like this is working fine with previous version.

Comment by Chanaka Fernando [ 12/Jul/16 ]

@Shakila

Can you check with the latest ESB 5.0.0 pack?

Comment by Shakila Sivagnanarajah [ 18/Jul/16 ]

Hi,
It is working fine with ESB 5.0.0-PRE-BETA2-PACK3.

Thanks,
Shakila





[ESBJAVA-4764] Deleting connector from management console gives an empty page Created: 18/Jul/16  Updated: 18/Jul/16  Resolved: 18/Jul/16

Status: Resolved
Project: WSO2 ESB
Component/s: Administration Console, Cloud Connectors
Affects Version/s: 5.0.0-Beta2
Fix Version/s: 5.0.0

Type: Bug Priority: High
Reporter: Buddhima Wijeweera Assignee: Buddhima Wijeweera
Resolution: Fixed Votes: 0
Labels: connector
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB version 5.0.0 - Beta2


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

 Description   

Add a connecotor through management-console.
Click delete button
Connector will be removed, but gives an empty page



 Comments   
Comment by Buddhima Wijeweera [ 18/Jul/16 ]

Fixed with : https://github.com/wso2/carbon-mediation/pull/690





[ESBJAVA-4656] Adding functionality to register custom statistic observers to recive statistics events Created: 06/Jun/16  Updated: 17/Jul/16  Resolved: 17/Jul/16

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

Type: Improvement Priority: High
Reporter: viraj senevirathne Assignee: viraj senevirathne
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Comments   
Comment by viraj senevirathne [ 06/Jun/16 ]

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

You can register custom observers by copying jar file which contains observer implementation.

  • It should implement org.wso2.carbon.das.messageflow.data.publisher.observer.MessageFlowObserver Interface
  • If observer is tenant aware, it should implement org.wso2.carbon.das.messageflow.data.publisher.observer.TenantInformation

Steps to follow

  • [Copy jar file to repository/components/lib directory of the ESB
  • Add all the custom observers separated with commas in carbon.xml like follows

<MediationFlowStatisticConfig>
<Observers>org.wso2.custom.Observer1,org.wso2.custom.Observer1r</Observers>
</MediationFlowStatisticConfig>





Generated at Sun Jul 24 08:22:09 IST 2016 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.