[ESBJAVA-4784] Event publisher and CSRF warnings observed at server startup in Windows Created: 23/Jul/16  Updated: 24/Jul/16

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

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

OS:Windows 10
JDK: Oracle 1.8.0


Attachments: Text File wso2carbon.log    
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   

Errors related to EventPublisher and CSRF were observed in Windows at server startup and first login respectively. Carbon log attached herewith

At server startup

TID: [-1234] [] [2016-07-23 22:13:41,073] ERROR {org.wso2.carbon.event.publisher.core.EventPublisherDeployer} -  Error, Event Publisher not deployed and in inactive state, Error while deleting the Event Publisher : Illegal char <:> at index 2: /E:/erandi/erandi/wso2esb-5.0.0-BETA2/bin/../repository/deployment/server/\eventpublishers {org.wso2.carbon.event.publisher.core.EventPublisherDeployer}
org.wso2.carbon.event.publisher.core.exception.EventPublisherConfigurationException: Error while deleting the Event Publisher : Illegal char <:> at index 2: /E:/erandi/erandi/wso2esb-5.0.0-BETA2/bin/../repository/deployment/server/\eventpublishers
	at org.wso2.carbon.event.publisher.core.internal.util.helper.EventPublisherConfigurationFilesystemInvoker.delete(EventPublisherConfigurationFilesystemInvoker.java:131)
	at org.wso2.carbon.event.publisher.core.EventPublisherDeployer.processDeployment(EventPublisherDeployer.java:177)
	at org.wso2.carbon.event.publisher.core.EventPublisherDeployer.deploy(EventPublisherDeployer.java:83)
	at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
	at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
	at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
	at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
	at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
	at org.apache.synapse.Axis2SynapseController.deployMediatorExtensions(Axis2SynapseController.java:743)
	at org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:388)
	at org.apache.synapse.ServerManager.start(ServerManager.java:183)
	at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:452)
	at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:196)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)

At login

TID: [-1234] [] [2016-07-23 22:22:44,501]  WARN {org.owasp.csrfguard.log.JavaLogger} -  potential cross-site request forgery (CSRF) attack thwarted (user:<anonymous>, ip:192.168.1.3, method:HEAD, uri:/carbon/admin/login.jsp, error:required token is missing from the request) {org.owasp.csrfguard.log.JavaLogger}


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

Hi,

Seems this is fixed through : https://github.com/wso2/carbon-analytics-common/commit/7e9525881afcb4778b6f1cbb60af1181d6a5da45

So need to upgrade carbon-analytics-common dependency to obtain the change.

Thanks,
Buddhima





[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-4782] Improve logging for ESB Created: 22/Jul/16  Updated: 22/Jul/16

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

Type: Bug 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
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 to improve ESB logging so that we can easily identify errors and different states.

  • Timeouts : What timeout applies in a given error condition (global, EP, or socket TO)
  • Correlate connections, request, callbacks
  • Add additional information such as endpoint that failed and the target URL.
  • Use different use cases that we can think of by considering error codes





[ESBJAVA-4781] JSON formatter should be able to escape auto premitive feature selectively on a payload based on JSON field value. Created: 22/Jul/16  Updated: 22/Jul/16

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

Type: Bug Priority: Normal
Reporter: Kevin Ratnasekera 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




[ESBJAVA-4780] The Fault sequence doesn't get invoked when queue capacity exceeded in IMB MQ Created: 22/Jul/16  Updated: 22/Jul/16

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

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

Attachments: XML File MyJMSProxy.xml     File fix.diff    
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

In this scenario where we have capacity(N) limited queue in IBM MQ and he is using ESB to send messages to that queue.

This works fine till queue capacity not full but once it is full (after N requests), client will get the the error [1] not N+1 mesage onwards.

Eventough this error thown by the the jms client, it dosen't invoke fault sequence. It continue the message flow from the callout mediator position.

This is the problem.

>> Following code segment catch the JMS exception and log it. Therefore synapse level dosen't recive the error and fault sequence dosen't get invoked.

org/apache/axis2/transport/jms/JMSMessageSender.java:181

} catch (JMSException e)

{ log.error("Error sending message with MessageContext ID : " + msgCtx.getMessageID() + " to destination : " + destination, e); }

finally {






[ESBJAVA-4778] CXF orbit bundle import conflicts Created: 22/Jul/16  Updated: 24/Jul/16  Due: 21/Jul/16

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

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

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

 Description   

We planned to release RM-connector with the ESB 5.0 GA release. I got following exception while RM-Connector testing with the latest ESB pack.

[2016-07-21 14:03:29,854] ERROR - NativeWorkerPool Uncaught exception

java.lang.LinkageError: javax/xml/bind/attachment/AttachmentMarshaller

at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.startDocument(XMLSerializer.java:818)

at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.prewrite(MarshallerImpl.java:344)

at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:307)

at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:163)

at org.apache.cxf.jaxb.JAXBEncoderDecoder.writeObject(JAXBEncoderDecoder.java:615)

at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.java:248)

at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:237)

at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.writeSoapEnvelopeStart(SoapOutInterceptor.java:169)

at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMessage(SoapOutInterceptor.java:87)

at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMessage(SoapOutInterceptor.java:67)

at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)

at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:516)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:425)

at org.apache.cxf.ws.rm.Proxy.invoke(Proxy.java:313)

at org.apache.cxf.ws.rm.Proxy.createSequence(Proxy.java:199)

at org.apache.cxf.ws.rm.RMManager.getSequence(RMManager.java:472)

at org.apache.cxf.ws.rm.RMCaptureOutInterceptor.handle(RMCaptureOutInterceptor.java:156)

at org.apache.cxf.ws.rm.AbstractRMInterceptor.handleMessage(AbstractRMInterceptor.java:83)

at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)

at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:516)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:425)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326)

at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279)

at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:314)

at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:327)

at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:246)

at org.wso2.carbon.connector.rm.ReliableMessage.invokeBackendRMService(ReliableMessage.java:118)

at org.wso2.carbon.connector.rm.ReliableMessage.connect(ReliableMessage.java:58)

at org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)

at org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:84)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:94)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:56)

at org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:104)

at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:148)

at org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:84)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:94)

at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:56)

at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)

at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:210)

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)

Steps to reproduce the issue.

1. Install CXF feature to the latest ESB pack. Since we haven't release p2 repo yet for the ESB 5.0 . We need to manually install the CXF feature to the pack.

https://github.com/wso2/carbon-mediation/tree/master/features/inbound-endpoints/org.wso2.carbon.inbound.endpoints.ext.wsrm.feature

2. Need to install RM-Connector (Since we haven't released it yet. You have to build connector from the code)

https://github.com/prabathariyaratna/esb-connectors/tree/master/reliablemessage/reliablemessage-connector/reliablemessage-connector-1.0.0

3. You can use existing service as the backend service (https://github.com/prabathariyaratna/esb-connectors/tree/master/reliablemessage/reliablemessage-connector/reliablemessage-connector-1.0.0/org.wso2.carbon.connector/src/test/resources/rmserver)

5. Please refer following document for other configurations (https://docs.wso2.com/pages/viewpage.action?title=Working%2Bwith%2Bthe%2BRM%2BConnector&spaceKey=CONNECTORS)

Note:- Once I have removed the javax.xml.bind.attachment;resolution:=optional entry from the import section of the orbit bundle. Then it was worked fine. We need to check the RM-Inbound also with this change since we are sharing cxf bundle among the RM inbound and outbound.

https://github.com/wso2/orbit/blob/master/cxf/3.0.5.wso2v2/pom.xml






[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-4775] Shipping ESB/APIM with enabling connection throttling for Passthrough transport Created: 20/Jul/16  Updated: 20/Jul/16

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

Type: Task Priority: High
Reporter: Isuru Udana Loku Narangoda Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned as APIMANAGER-5284 CLONE - Shipping ESB/APIM with enabli... Open
Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

With reference to mail thread "Shipping ESB/APIM with enabling connection throttling for Passthrough transport" at architecture@

In the Passthrough HTTP transport[1] there is a configuration parameter called 'max_open_connections' to control the maximum number of connections getting established with the client.

Currently we are shipping the product without specifying a default value for that, that means we are allowing any number of connections.
Allowing limitless connection establishment with the client may lead to a catastrophic incident if it gets a sudden burst of requests.

So shall we ship the product with a sensible default value ?

[1] https://docs.wso2.com/display/ESB490/HTTP+PassThrough+Transport






[ESBJAVA-4774] Sequence name text doesn't prevent of performing an XSS attack Created: 20/Jul/16  Updated: 20/Jul/16

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

Type: Bug Priority: Highest
Reporter: Balasubramaniyam Senduran Assignee: Balasubramaniyam Senduran
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   

It is able to create a sequence named

<script>alert(123)</script>






[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-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-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-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-4769] JMS message publishing fails after encryptiing JMS credentials in the axis2.xml Created: 18/Jul/16  Updated: 18/Jul/16

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

Type: Bug Priority: High
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:

ActiveMQ
ESB 4.8.1


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

 Description   

Enable user validation on the broker and encrypt the following JMS credentials in axis2.xml sender configuration and try to publish a message.

<parameter name="java.naming.security.credentials" svns:secretAlias="Axis2.Jndi.Parameter.Password">password</parameter>
<parameter name="transport.jms.Password" svns:secretAlias="Axis2.Jms.Parameter.Password">password</parameter>

The following exception occurs.
The value being passed as the password after encrypting the credentials is actually the value in the axis2.xml (i.,e the value 'password'). The encrypted value of the password is not considered here.

[2016-07-14 01:02:59,557] ERROR - JMSConnectionFactory Error creating JMS session from JMS CF : default
javax.jms.JMSSecurityException: User name [sa] or password is invalid.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1393)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496)
at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:324)
at org.apache.axis2.transport.jms.JMSUtils.createSession(JMSUtils.java:680)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:346)
at org.apache.axis2.transport.jms.JMSConnectionFactory.getSession(JMSConnectionFactory.java:397)
at org.apache.axis2.transport.jms.JMSMessageSender.<init>(JMSMessageSender.java:87)
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:123)
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: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: java.lang.SecurityException: User name [sa] or password is invalid.
at org.apache.activemq.security.SimpleAuthenticationBroker.authenticate(SimpleAuthenticationBroker.java:103)
at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:71)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:98)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:103)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
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:125)
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:233)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 more
[2016-07-14 01:02:59,566] ERROR - Axis2Sender Unexpected error during sending message out
org.apache.axis2.transport.jms.AxisJMSException: Error creating JMS session from JMS CF : default
at org.apache.axis2.transport.jms.JMSConnectionFactory.handleException(JMSConnectionFactory.java:248)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:350)
at org.apache.axis2.transport.jms.JMSConnectionFactory.getSession(JMSConnectionFactory.java:397)
at org.apache.axis2.transport.jms.JMSMessageSender.<init>(JMSMessageSender.java:87)
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:123)
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: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: javax.jms.JMSSecurityException: User name [sa] or password is invalid.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1393)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496)
at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:324)
at org.apache.axis2.transport.jms.JMSUtils.createSession(JMSUtils.java:680)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:346)
... 24 more
Caused by: java.lang.SecurityException: User name [sa] or password is invalid.
at org.apache.activemq.security.SimpleAuthenticationBroker.authenticate(SimpleAuthenticationBroker.java:103)
at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:71)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:98)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:103)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
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:125)
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:233)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 more
[2016-07-14 01:02:59,570] WARN - FaultHandler ERROR_CODE : 0
[2016-07-14 01:02:59,570] WARN - FaultHandler ERROR_MESSAGE : Unexpected error during sending message out
[2016-07-14 01:02:59,571] WARN - FaultHandler ERROR_DETAIL : org.apache.synapse.SynapseException: Unexpected error during sending message out
at org.apache.synapse.core.axis2.Axis2Sender.handleException(Axis2Sender.java:172)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:71)
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.axis2.transport.jms.AxisJMSException: Error creating JMS session from JMS CF : default
at org.apache.axis2.transport.jms.JMSConnectionFactory.handleException(JMSConnectionFactory.java:248)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:350)
at org.apache.axis2.transport.jms.JMSConnectionFactory.getSession(JMSConnectionFactory.java:397)
at org.apache.axis2.transport.jms.JMSMessageSender.<init>(JMSMessageSender.java:87)
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:123)
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:482)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:59)
... 15 more
Caused by: javax.jms.JMSSecurityException: User name [sa] or password is invalid.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1393)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496)
at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:324)
at org.apache.axis2.transport.jms.JMSUtils.createSession(JMSUtils.java:680)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createSession(JMSConnectionFactory.java:346)
... 24 more
Caused by: java.lang.SecurityException: User name [sa] or password is invalid.
at org.apache.activemq.security.SimpleAuthenticationBroker.authenticate(SimpleAuthenticationBroker.java:103)
at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:71)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:98)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:103)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
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:125)
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:233)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 more

[2016-07-14 01:02:59,571] WARN - FaultHandler ERROR_EXCEPTION : org.apache.synapse.SynapseException: Unexpected error during sending message out
[2016-07-14 01:02:59,572] WARN - FaultHandler FaultHandler : AnonymousEndpoint
[2016-07-14 01:02:59,572] WARN - EndpointContext Endpoint : AnonymousEndpoint will be marked SUSPENDED as it failed
[2016-07-14 01:02:59,572] WARN - EndpointContext Suspending endpoint : AnonymousEndpoint - last suspend duration was : 30000ms and current suspend duration is : 30000ms - Next retry after : Thu Jul 14 01:03:29 IST 2016






[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-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-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-4765] OutOfMemory Error if SSL Port overloaded with connnections Created: 18/Jul/16  Updated: 18/Jul/16

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

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

Create sockets with SSL port around (100000 sockets) and close as soon as accepted.






[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





Generated at Sun Jul 24 12:15:47 IST 2016 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.