wso2 / ansible-apim Goto Github PK

Description:
<CARBON_HOME>/repository/deployment/server directory contains the APIs created by the UI and they need to be backed up before applying the newest changes.

Affected Product Version:
v2.6.0.5

Description:
Product packs included in the setup should be updated with a script which uses the in-place client.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Please

I'm currently working in a distributed API Manager and Analytics environment to be set through ansible scripts

I need to run analytics balanced through 2 IPs

In my project structure I have the following:
ansible-apim/roles/apim-analytics-worker/templates/carbon-home/conf/dashboard/deployment.yaml.j2

and in this yaml the following content:
baseUrl: https://localhost:9643

When I try to connect in Analytics :
https://:9643/analytics-dashboard

It tries to redirect it to localhost

I have read the documentation:

https://apim.docs.wso2.com/en/3.0.0/learn/analytics/configuring-apim-analytics/#step-5-configure-apim-idp-client

How can I change the baseUrl so that when I ran the ansible script it reflects properly in both distributed environment IPs ?

Thks!!

Description:
Puppet modules should provide an option for agents to get product packages and libraries through HTTP requests.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:
When the value for backup_enabled is uncommented and set to 'no', the deployment still takes a backup.

Suggested Labels:
Type/Bug
Priority/Medium

Suggested Assignees:
@Savidude

Description:
The KeyValidatorClientType in api-manager.xml is set to ThriftClient and by default, it should be set to WSClient in the apim role.

Affected Product Version:
v2.6.0.5

Description:
The following warning is encountered when running the Ansible playbook.

[DEPRECATION WARNING]: evaluating enable_performance_tuning as a bare variable, this behaviour will go away and you might need to add
|bool to the expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle. This feature will be removed in version
2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

Can be fixed by changing the conditional checking if performance tuning is enabled to a Boolean value.

- name: System performance tuning
  copy:
     src: "{{ item.src }}"
     dest: "{{ item.dest }}"
   loop: "{{ performance_tuning_file_list }}"
   when: enable_performance_tuning|bool

Suggested Labels:
Type/Bug
Priority/Low

Suggested Assignees:
@Savidude

Description:
The following error is encountered while starting a TrafficManager node

TID: [-1234] [] [2019-07-12 10:25:15,936] FATAL {org.wso2.carbon.core.init.CarbonServerManager} -  WSO2 Carbon initialization Failed {org.wso2.carbon.core.init.CarbonServerManager}
org.apache.axis2.AxisFault: Exception occured while loading the Axis configuration from /Users/savidude/.wum3/products/wso2am/2.6.0/wso2am-2.6.0/repository/conf/axis2/axis2.xml
	at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:194)
	at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
	at org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
	at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:399)
	at org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:220)
	at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:105)
	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 org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
	at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
	at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
	at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
	at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
	at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
	at org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
	at org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
	at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
	at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1230)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1174)
	at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1066)
	at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5370)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5668)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1700)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1690)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.axis2.deployment.DeploymentException: org.apache.synapse.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v28
	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

This can be fixed by renaming the repository/conf/axis2/axis2_TM.xml to repository/conf/axis2/axis2.xml

Suggested Labels:
Type/Bug
Priority/High

Suggested Assignees:
@Savidude

Description:
The following documentation for patterns has incorrect instructions.

docs/Pattern_2.md
docs/Pattern_3.md
docs/Pattern_4.md

Description:
Product packs should be provided as a .zip file, as opposed to using .deb and .rpm installers.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:
It will be better to have sample deployment Sync approaches also in this repository. Something like a pre-deployment role and a post-deployment role. Where it will remove the NFS mount before deleting the packs and then after the redeployment it will remount the NFS location to the deployment folder. WDYT?

Suggested Labels:
Improvement

Description:

Ansible scripts for Identity Server use a repeatable task to copy every single configuration file as below.

      template:
        src: "carbon-home/repository/conf/datasources/master-datasources.xml.j2"
        dest: "{{ setup_path }}/{{ product_name }}/{{ product_version }}/repository/conf/datasources/master-datasources.xml"

    - name: "Copy identity.xml"
      template:
        src: "carbon-home/repository/conf/identity/identity.xml.j2"
        dest: "{{ setup_path }}/{{ product_name }}/{{ product_version }}/repository/conf/identity/identity.xml"

    - name: "Copy carbon.xml"
      template:
        src: "carbon-home/repository/conf/carbon.xml.j2"
        dest: "{{ setup_path }}/{{ product_name }}/{{ product_version }}/repository/conf/carbon.xml"

    - name: "Copy registry.xml"
      template:
        src: "carbon-home/repository/conf/registry.xml.j2"
        dest: "{{ setup_path }}/{{ product_name }}/{{ product_version }}/repository/conf/registry.xml"

    - name: "Copy axis2.xml"
      template:
        src: "carbon-home/repository/conf/axis2/axis2.xml.j2"
        dest: "{{ setup_path }}/{{ product_name }}/{{ product_version }}/repository/conf/axis2/axis2.xml"

But there is a optimal way to achieve same as follows:

TASKS:

- name: copy wso2 conf files
  template:
    src:   "{{ carbon_home }}/repository/conf/{{ item.source }}"
    dest: "{{ setup_path }}/{{ product_name }}/{{ product_version }}/repository/conf/{{ item.dest }}"
    owner: "{{ wso2_user }}"
    group: "{{ wso2_group }}"
  with_items: "{{ config_files }}"

VARS:

config_files:

  - source: 'datasources/master-datasources.xml.j2'
    dest: 'datasources/master-datasources.xml'

  - source: 'identity/identity.xml.j2'
    dest: 'identity/identity.xml'

  - source: 'carbon.xml.j2'
    dest: 'carbon.xml'

  - source: 'registry.xml.j2'
    dest: 'registry.xml'

  - source: 'axis2/axis2.xml.j2'
    dest: 'axis2/axis2.xml' 

Affected Product Version:
v2.6.0.1

Description:
if you don't pass the parameter -K to run the playbook it fails with the message: Missing sudo password.

$ ansible-playbook -i dev site.yml
...
TASK [common : Create group] ****************************************************************************
fatal: [apim_1]: FAILED! => {"msg": "Missing sudo password"}
fatal: [apim-is-as-km_1]: FAILED! => {"msg": "Missing sudo password"}
fatal: [apim-analytics-worker_1]: FAILED! => {"msg": "Missing sudo password"}

Suggested Labels:
Documentation

Description:
Ansible resources should be created for API Manager 3.0.0

Description:
Add Ansible scripts for WSO2 API Management 2.6.0 with the following groups.

• apim
• apim-analytics
• apim-is-as-km

Suggested Labels:
Type/Improvement
Priority/Normal

Affected Product Version:
API Management 2.6.0
API Management Analytics 2.6.0

OS, DB, other environment details and versions:
Ansible 2.6.2
Ubuntu 16.04 or higher
CentOS 7

Description:
Add instructions on previous Ansible versions and how they are managed.

Description:
The apim-analytics-dashboard rule is required when configuring alerts from the analytics side.

Description:
Needs to be fixed by moving the

- name: Copy WSO2APIM service file
   template:
     src: "wso2apim.service.j2"
     dest: /etc/systemd/system/wso2is.service

Block to before the server is being stopped at

- name: Stop wso2apim as a service
   systemd:
     name: wso2apim
     state: stopped

Suggested Labels:
Type/Bug
Priority/High

Suggested Assignees:
@Savidude

Description:
Remove this role as it is no longer needed

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:

The README instructs to copy the packs to the files directory but they should be copied to the files/packs folder.

Description:
In some cases, we need to ship tools like API Manager CLI, etc. We need to add the capability of copying such tools/resources to Ansible agents.

Description:
Sometimes the JDK archive name is different from the extracted folder name. Current Ansible scripts expect them to be the same.

Possible Fix

- name: Unzip JDK
  unarchive:
    src: /path/to/jdk.tar.gz
    dest: /path/to/extract/{{ jdk_name }}
    extra_opts: [--strip-components=1]

Description:
$Subject as it is important to have community contributions.

Description:
Add configurations for performance tuning at the OS level. Refer to the documentation on Performance Tuning.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:

[keystore.primary]
name = "{{ key_store_location }}"
password = "{{ key_store_password }}"
alias = "{{ key_store_key_alias }}"
key_password = "{{ key_store_key_password }}"

Affected Product Version:
IS-KM 5.10.0

Description:
Some of the tasks contain double quotes for the name and some do not.

Suggested Assignees:
@VimukthiPerera

Affected Product Version:
All up to 2.6.0

Description:
Add Ansible scripts to deploy WSO2 API Manager 2.5.0

Suggested Labels:
Type/Improvement

Affected Product Version:
API Manager 2.5.0

OS, DB, other environment details and versions:
Ubuntu 16.04 or higher
Ansible 2.6.2

Description:
The current validation query is set to "SELECT 1". This changes according the type of the database. Therefore the query should be parameterized similar to the DriverClassName.

For eg - Oracle DB the validation query is "SELECT 1 FROM DUAL"

Description:
$subject

Description:

When using script for distributed setup database driver did not get set in the master-datasource.xml. It set a empty value.

Suggested Labels:

Suggested Assignees:

Affected Product Version:
3.2.x

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
The site.yml playbook at the end of the file contains a sample that shows how to combine two different roles at a single node. The sample describes how to start both API Manager default profile and Identity Server as Key Manager in the same apim_1 node.

But this causes an error that wso2is-km requested service could not be found.

Suggested Labels:
Documentation

Description:
Create IS as Key Manager role in Ansible resources for APIM since IS is used as a key manager instead of the default key manager.

Suggested Labels:
Type/Improvement

Affected Product Version:
APIM 2.6.0
OS, DB, other environment details and versions:
Ansible 2.6.2

Related Issues:
#4

Hi

Docs[1] about patterns are empty, can you provide more info, or explain the idea or architecture used to create this ansible scripts, to allow us to reuse and make improvements?

[1]https://github.com/wso2/ansible-apim/blob/master/docs/Pattern_1.md

Best regards
Clóvis

Description:

In XSSValue which is enabled to mitigate cross-site scripting attack [1], verification is done against the patterns configured in xss-patterns.properties [2]. Since there is a pattern as "alert(.*?)", this case fails. Validation will fail for all actions that have the word alert.

[1] https://docs.wso2.com/display/ADMIN44x/Mitigating+Cross+Site+Scripting+Attacks
[2] https://github.com/wso2-support/carbon4-kernel/blob/support-4.4.35/core/org.wso2.carbon.ui/src/main/java/org/wso2/carbon/ui/valve/XSSValve.java#L107

Fix

In the /repository/conf/security/xss-patterns.properties file, there is a pattern defined as pattern14=alert(.?)*.

Replace it with the following pattern

pattern14=alert\((.*?)\)
Above changes will fix the XSS issue which AAA life is facing when they have enabled the XSS configuration.

To enable the XSS configuration, do the following in the carbon.xml file.

1. Need to add the following value under the tag of the configuration under the section.
   commonauth
   After the modification configuration will be as follows.

Description:

While trying to run key-manager profile getting issue below:

2019-12-19 15:31:11,470] INFO - UserStoreMgtDSComponent Carbon UserStoreMgtDSComponent activated successfully.
[2019-12-19 15:31:12,362] FATAL - CarbonServerManager WSO2 Carbon initialization Failed
org.apache.axis2.AxisFault: Exception occured while loading the Axis configuration from C:\WSO2\Distributed3.0.0\KeyManager/repository/conf/axis2/axis2.xml
at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:194) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) ~[axis2_1.6.1.wso2v38.jar:?]
at org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:415) [org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:305) [org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118) [org.wso2.carbon.core_4.5.1.jar:?]
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:973) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
Caused by: org.apache.axis2.deployment.DeploymentException: org.apache.synapse.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v38
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:713) ~[axis2_1.6.1.wso2v38.jar:?]
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:125) ~[axis2_1.6.1.wso2v38.jar:?]
at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192) ~[org.wso2.carbon.core_4.5.1.jar:?]
Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
apim-gateway.yml file missing from /dev/group_vars
File is referenced for Deployment Pattern 2 but is not
provided in the /dev directory

Suggested Labels:

Suggested Assignees:

Affected Product Version:
3.1.0

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
Clustering configurations in axis2.xml should support other membership schemes.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:
APIM Gateway Profile is not deploying . When analyse the carbon logs its noticed that this is a toml parser issue in deployment.toml.j2 template of gateway role due to some duplicate tags

Suggested Labels:

Suggested Assignees:

Affected Product Version:
3.2

OS, DB, other environment details and versions:

Steps to reproduce:
Run ansible-playbook with gateway profile information in the site.yml

Related Issues:

Description:
Ansible resources for API Manager 3.0.0
Branch name: 3.0.x

At https://github.com/wso2/ansible-apim/tree/3.1.x

Affected Product Version:
3.1.0

Description:
This could remain in the documentation. However, is not required by default. As a result, this task could be left commented out.

Suggested Labels:
Type/Improvement
Priority/Normal

Suggested Assignees:
@Savidude

Description:

Navigate to carbon-home of the apim-analytics-worker role. All the files required to deploy the API Manager analytics are here. Follow the instructions in the following files to modify the files.

Configure Analytics
Minimum HA deployment

Above links are pointing to old versions.
[1] https://github.com/wso2/ansible-apim/blob/3.1.x/docs/Pattern_2.md

Affected Product Version:
3.1.x branch.

Description:
Error message FAILED! => {"msg": "'performance_tuning_file_list' is undefined"} is encountered while running APIM analytics and IS as KM profiles.

Can be fixed by adding the following to apim-analytics.yml and apim-is-as-km.yml

# Performance tuning configurations
enable_performance_tuning: false
performance_tuning_file_list:
  - { src: '{{ product_package_location }}/system/etc/sysctl.conf',
      dest: '/etc/sysctl.conf' }
  - { src: '{{ product_package_location }}/system/etc/security/limits.conf',
      dest: '/etc/security/limits.conf' }

Suggested Labels:
Type/Bug
Priority/High

Suggested Assignees:
@Savidude

Description:

This is where [1] that issue happens.
[1]

Description:
All roles have the same process of installing a JDK distribution. This can be moved to the common module.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:
Variable values are not provided for validation queries.

Suggested Labels:
Type/Bug
Priority/Hign

Suggested Assignees:
@Savidude

Description:
$subject with the worker node loop.

Description:

Hi, i am still facing the same issue while trying to run traffic-manager profile through APIM 3.0.0

[2019-12-24 16:11:25,041] INFO - EmbeddedRegistryService Connected to mount at configregistry in 2ms
[2019-12-24 16:11:25,042] INFO - EmbeddedRegistryService Connected to mount at govregistry in 4ms
[2019-12-24 16:11:25,066] INFO - RegistryCoreServiceComponent Registry Mode : READ-WRITE
[2019-12-24 16:11:25,316] INFO - JmxReporterBuilder Creating JMX reporter for Metrics with domain 'org.wso2.carbon.metrics'
[2019-12-24 16:11:25,323] INFO - AbstractReporter Started JMX reporter for Metrics
[2019-12-24 16:11:27,453] INFO - SolrClient Default Embedded Solr Server Initialized
[2019-12-24 16:11:27,935] INFO - UserStoreMgtDSComponent Carbon UserStoreMgtDSComponent activated successfully.
[2019-12-24 16:11:30,733] FATAL - CarbonServerManager WSO2 Carbon initialization Failed
org.apache.axis2.AxisFault: Exception occured while loading the Axis configuration from C:\WSO2\Distributed3.0.0\TF\TrafficManager/repository/conf/axis2/axis2.xml
at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:194) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) ~[axis2_1.6.1.wso2v38.jar:?]
at org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:415) [org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:305) [org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118) [org.wso2.carbon.core_4.5.1.jar:?]
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:973) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
Caused by: org.apache.axis2.deployment.DeploymentException: org.apache.synapse.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v38
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:713) ~[axis2_1.6.1.wso2v38.jar:?]
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:125) ~[axis2_1.6.1.wso2v38.jar:?]
at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192) ~[org.wso2.carbon.core_4.5.1.jar:?]
... 8 more
Caused by: java.lang.ClassNotFoundException: org.apache.synapse.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v38
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:512) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:423) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:415) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:155) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_232]
at java.lang.Class.forName0(Native Method) ~[?:1.8.0_232]
at java.lang.Class.forName(Class.java:264) ~[?:1.8.0_232]
at org.apache.axis2.util.Loader.loadClass(Loader.java:261) ~[axis2_1.6.1.wso2v38.jar:?]
at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:687) ~[axis2_1.6.1.wso2v38.jar:?]
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:125) ~[axis2_1.6.1.wso2v38.jar:?]
at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341) ~[org.wso2.carbon.core_4.5.1.jar:?]
at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192) ~[org.wso2.carbon.core_4.5.1.jar:?]
... 8 more
Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:
mysql

Steps to reproduce:
run wso2 apim 3.0.0 as traffic manager

Related Issues:
#50

Description:
Product packs are provided to the setup through .zip files. Add support for .deb and .rpm files as well.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@Savidude

Description:
Step 3 in Pattern 1 doc mentions "Customize the roles for API Manager pattern 4". Should be "Customize the roles for API Manager pattern 1".

Description:
The following error log can be seen while starting the server as a service in gateway, km, tm, publisher roles.

JAVA_HOME environment variable is set to /opt/java
CARBON_HOME environment variable is set to /mnt/apim-tm/wso2am-3.2.0
Using Java memory options: -Xms256m -Xmx1024m
[2020-09-15 05:55:40,777]  INFO {org.wso2.config.mapper.ConfigParser} - Initializing configurations with deployment configurations
[2020-09-15 05:55:40,965] ERROR {org.wso2.config.mapper.TomlParser} - user_store previously defined at line 7, column 1 (line 15, column 1)
[2020-09-15 5:55:40,965]  SEVERE {org.wso2.carbon.server.Main handleConfiguration} - Error while performing configuration changes 
org.wso2.config.mapper.ConfigParserException: Error parsing deployment configuration
	at org.wso2.config.mapper.TomlParser.parse(TomlParser.java:140)
	at org.wso2.config.mapper.ConfigParser.parse(ConfigParser.java:257)
	at org.wso2.config.mapper.ConfigParser.deploy(ConfigParser.java:225)
	at org.wso2.config.mapper.ConfigParser.deployAndStoreMetadata(ConfigParser.java:188)
	at org.wso2.config.mapper.ConfigParser.parse(ConfigParser.java:135)
	at org.wso2.carbon.server.Main.handleConfiguration(Main.java:236)
	at org.wso2.carbon.server.Main.main(Main.java:107)
	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 org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:69)
	at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:51)