Refer https://wso2.org/jira/browse/COMMONS-125

Refer https://wso2.org/jira/browse/COMMONS-131

This source needs to be removed from carbon-commons. We never did release this, but the obsoleted source is still lying around.

Refer https://wso2.org/jira/browse/COMMONS-117

It looks like [1] is not raising errors if the bundle is not activated. IMO this is not correct, we may need to raise an error if an error occurs while trying to initiatlize the SVN deployment synchronizer.

This issue can be re-created by enabling SVN deployment synchronizer in WSO2 ESB 4.9.0 without copying the dependent SVN libraries.

[1] https://github.com/wso2/carbon-commons/blob/master/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.subversion/src/main/java/org/wso2/carbon/deployment/synchronizer/subversion/SVNDeploymentSynchronizerComponent.java

https://wso2.org/jira/projects/CCOMMONS/issues/CCOMMONS-11

We are tried to configure logback logs for wso2 products (i.e IS 5.1.0) using below steps.

1. using both log4j-over-slf4j & jcl-over-slf4j bridges (by replacing all the log4j & commons logging .class contained in org.wso2.carbon.logging-4.4.2 by the same contained in the bridges).
2. Place logback-classic-1.1.5.jar, logback-core-1.1.5.jar, slf4j-api-1.7.17.jar in WSO2IS-5.1.0\repository\components\dropins\ directory
3. Place logger_2.0.0_SNAPSHOT_1.0.0.jar in wso2IS-5.1.0\repository\components\lib\ directory
4. Navigate to wso2IS-5.1.0/repository/conf/etc/bundle-config/ and create a folder named ch.qos.logback.classic (sumbolic name of the bundle logback-classic-1.1.2.jar)
5. Place the logback.xml file in the created folder
6. Start the server
   Then this is working.. but this is not recommend approach ( replacing class file approach in step 1).need to create a script (may be maven pom ) a and automation these steps
   or is there any recommended approach to configure logback for wso2 products

https://wso2.org/jira/projects/CCOMMONS/issues/CCOMMONS-7

Refer https://wso2.org/jira/browse/COMMONS-129

When a task is resumed[1], we are calling the TaskUtils.setTaskPaused(...) we should pass false here since the we are resuming the task

[1] https://github.com/wso2/carbon-commons/blob/v4.5.10/components/ntask/org.wso2.carbon.ntask.core/src/main/java/org/wso2/carbon/ntask/core/impl/clustered/ClusteredTaskManager.java#L171

Refer https://wso2.org/jira/browse/COMMONS-127

in logging components
class org.wso2.carbon.logging.service.LoggingAdmin
method private Appender getAppenderInLoggerWithName(Logger logger, String appenderName)
appender.getName() will return null when the appender is org.apache.solr.logging.log4j.EventAppender.

Caused by: java.lang.NullPointerException
at org.wso2.carbon.logging.service.LoggingAdmin.getAppenderInLoggerWithName(LoggingAdmin.java:550)
at org.wso2.carbon.logging.service.LoggingAdmin.getAppenderData(LoggingAdmin.java:153)

It will recur in wso2as-5.3.0

Refer https://wso2.org/jira/browse/COMMONS-113

See the attached screenshot. The info box is shown we change the logging level of any logger.

Refer https://wso2.org/jira/browse/COMMONS-114

Description:
The reason for the connection refused problem is as follows.

Currently, we are using DefaultHttpClient() class to create the client object in GoogleAnalyticsDataPublisher class. In order to configure a proxy and a port, we need to use SystemDefaultHttpClient() class to create the client object inside the GoogleAnalyticsDataPublisher class. This class can read the system properties configured in the wso2server.sh file

Affected Product Version:
carbon-commons 4.6.21

Following ui components are no longer used in the platform, we need to remove them,

• org.wso2.carbon.cluster.mgt.admin.ui
• org.wso2.carbon.deployment.synchonizer.ui
• org.wso2.carbon.discovery.ui
• org.wso2.carbon.reporting.custom.ui
• org.wso2.carbon.reporting.template.ui

https://wso2.org/jira/projects/CCOMMONS/issues/CCOMMONS-19

Refer https://wso2.org/jira/browse/COMMONS-110

Refer https://wso2.org/jira/browse/COMMONS-116

Description:
It is not a good practice to print un-trusted values in error messages.

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
carbon-commons repo is using an old orbit version of httpclient

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Refer https://wso2.org/jira/browse/COMMONS-109

Is there any reason not to raise errors if SVNDeploymentSynchronizerComponent is not activated? As I can see errors are logged as debug logs.

https://github.com/wso2/carbon-commons/blob/master/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.subversion/src/main/java/org/wso2/carbon/deployment/synchronizer/subversion/SVNDeploymentSynchronizerComponent.java