Description:

./micro-integrator.sh -version 

Gives the following output

${product.name} v${product.version}
WSO2 Carbon Framework v4.4.40

Create a doc for this and add it to the main readme.

Jenkins job log with split package warnings consoleText.txt

Description:
Following additional logs getting printed at the server startup

INFO - ManagementModeConfigurationLoader CEP started in Persistence enabled HA mode
2019-04-24 14:01:51,722 INFO [org.wso2.micro.integrator.integration.ServerLogReader] - [2019-04-24 14:01:51,722] [micro-integrator] INFO - TCPEventServer EventServer starting event listener on 0.0.0.0:11010
2019-04-24 14:01:51,728 INFO [org.wso2.micro.integrator.integration.ServerLogReader] - [2019-04-24 14:01:51,728] [micro-integrator] INFO - EventHandler Event Management TCPEventServer for EventReceiver started on port 11010

microeiisfailingatsecureproxyservices.zip

Description:
SecureProxy scenario is not supported in Micro EI. A supporting secure proxy scenario has to be implemented.

Affected Product Version:
Micro EI 6.4.0

OS, DB, other environment details and versions:
Any environment

Steps to reproduce:
Try to invoke Performance Test scenario SecureProxy in repo, "performance-ei" and the following exception could be observed.

java.lang.RuntimeException: org.wso2.carbon.security.util.ServerCrypto Not Found at org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFactory.java:203) at org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:95) at org.apache.rampart.util.RampartUtil.getSignatureCrypto(RampartUtil.java:390) at org.apache.rampart.RampartEngine.process(RampartEngine.java:166) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:93) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:415) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) 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)

1. Deploy the attached CAR file in Micro EI and start.
2. Load the attached jmx script
3. In the HTTP Request section, set the file path of the attached XML file as the File Path of Files Upload tab
4. Once the request is sent above exception will happen.
5. When the issue is fixed the below exception will come as the backend service is unavailable.

[EI-Core] WARN - ConnectCallback Connection refused or failed for : netty:8688

Related Issues:
[1] wso2/performance-ei#10

Currently the org.wso2.carbon.micro.integrator.extensions module has to be manually built and copied to the distribution resources. This need to be automated.

Information can be found in https://docs.docker.com/docker-hub/official_images/

Getting started guide

• Add section on monitoring
• Add section on tracing

Description:
The document working with MI [1] instructs to create MI from EI using profile-creator script and proceed. We need to update this as it is available now as a separate run time.

[1] - https://docs.wso2.com/display/EI6xx/Working+with+the+Micro+Integrator

Also we need to update the folder paths in that document since we have restructured it.

In case, if we are going only with git docs, we may need to remove the above docs since it is no more valid.

Description:
Remove open saml bundle from feature generation.

Currently, the version used for MI CLI is different from the product version. Shall we use the same version for CLI too since it is easier to correlate?

We need to make sure the CLI version upgrade also happens whenever we do an MI release.

Description:

Currently it is disabled by default in promethus-conf.xml and we have to edit this file to enable it.

<PrometheusPublishingConfig>
    <Enabled>false</Enabled>
</PrometheusPublishingConfig>

We need this to be facilitated via a system property in order to have seamless integration with docker for MI.

Description:

At server start-up following exception getting printed in osgi configuration logs,

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at org.wso2.carbon.event.processor.manager.core.internal.CarbonEventManagementService.init(CarbonEventManagementService.java:228)
at org.wso2.carbon.event.processor.manager.core.internal.ds.EventManagementServiceDS.setConfigurationContextService(EventManagementServiceDS.java:73)

Description:

Currently, a client program to connect to micro integrator and observe details is being written. I would like if we can simulate what mysql is doing here.

We can run a container for mysql like below.

- docker run --name=myContainer -d mysql/mysql-server

And then mysql client can be run like below in the same container

docker exec -it mysqlDataStore mysql -uroot -p

At the very first time you start, server will generate a random password for the client to connect. It will be on logs of the server.

User need to get that password and connect when prompted. Then he can reset the password like below.

ALTER USER 'root'@'localhost' IDENTIFIED BY 'root';

So the improvements suggested here are

1. The client for micro integrator should be able to run using docker exec -it <container name>
2. We can use above password handling mechanism for security.
3. User does not need to pull any additional image to run the client.
4. User does not need to enable anything on server specifically to do this.

Affected Product Version:

1.0.0

OS, DB, other environment details and versions:

Docker platform .

We need to make sure,

• the distribution runs on JDK 11 (can be compiled with JDK 8)
• the distribution can be built and run using JDK 11

Commands to list and show artifacts deployed in the micro-integrator

Tasks

• Carbon Application

  • List
  • Show

• APIs

  • List
  • Show

• Endpoints

  • List
  • Show

• Inbound Endpoint

  • List
  • Show

• Sequences

  • List
  • Show

• Proxy Services

  • List
  • Show

• Tasks

  • List
  • Show

Description:
The following WARN log is printed during micro-integrator startup during VFS listener initialization

WARN - PollTableEntry transport.vfs.FileURI parameter is missing in the proxy service configuration

Currently, the file structure in the distribution is very similar to the one we had with the micro integrator profile. Since we are creating a separate build for micro integrator we can move most of these files to top level.

• Document folder structure
  • Update micro-integrator/doc/working-with-the-micro-integrator.md

We need to add Prometheus support to MI as well. We have done it for integrator profile in wso2/product-ei#3399.

• Doc updates
  • Update Getting started guide with details (related to #133)
  • Update Working with the Micro Integrator

Description:

Following doc

It states to execute command

$ docker build -t wso2/mi-order-process-be .

But it did not states from where it needs to run this. By inspecting I could find it needs to run from

/micro-integrator/examples/getting-started/order-process-be

It is not clear in the document

This can be a very basic scenario to showcase the developer workflow with micro integrator.

Description:

docker exec -it <containerIdOrName> bash

should give access to bash of micro integrator image. But it gives below error once executed.

OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown

Description:

We deploy to micro integrator via EI Tooling. EI tooling always creates a CAPP which is deployable to Micro Integrator.

As there is no Web UI or any place we can create and deploy individual artifacts. Thus better to remove synapse-configs folder altogether and keep carbonapps folder only.

There are some more deployment specific folders like axis2modules, axis2services etc which is not relevant to MI usecase.

There are two libthrift jars (libthrift_0.12.0.wso2v1.jar and libthrift_0.9.2.wso2v1.jar) in wso2/components/plugins folder.

libthrift_0.12.0.wso2v1.jar is coming from the carbon-mediation dependencies. libthrift_0.9.2.wso2v1.jar is from the analytics-common. We could not upgrade the libthrift version in analytics-common due to some failures in IS analytics components.

Related PRs

• https://github.com/wso2/analytics-is/issues/461
• wso2/carbon-analytics-common#603

Description

The binaries generated for the CLI tool are platform dependent. Need a proper way of distributing the binaries

Description:

Message processors are not started

Affected Product Version:

wso2mi-1.0.0-m6-SNAPSHOT

OS, DB, other environment details and versions:

Steps to reproduce:

1. Edit conf/jndi.properties to have

queue.testQueue=testQueue

2. Copy following jar files to /lib folder

-rw-r--r--@ 1 hasitha  wheel   2.2M Apr 29 18:56 andes-client-3.2.97.jar
-rw-r--r--@ 1 hasitha  wheel    28K Apr 29 18:56 geronimo-jms_1.1_spec-1.1.0.wso2v1.jar
-rw-r--r--@ 1 hasitha  wheel    78K Apr 29 18:57 org.wso2.securevault-1.0.0-wso2v2.jar

3. Copy the attached CAR file with MS/MP

4. Start MI. You will see below on logs.

[2019-04-29 19:54:21,128] [micro-integrator]  INFO - NioSelectorPool Using a shared selector for servlet write/read
[2019-04-29 19:54:21,135] [micro-integrator]  INFO - StartupFinalizerServiceComponent WSO2 Micro Integrator started in 6 sec
[2019-04-29 19:54:21,253] [micro-integrator]  INFO - AbstractQuartzTaskManager Task scheduled: [-1234][ESB_TASK][MSMP_myMP0][Paused]
[2019-04-29 19:54:21,254] [micro-integrator]  INFO - ScheduledMessageProcessor Started message processor. [myMP].
[2019-04-29 19:54:21,256] [micro-integrator]  INFO - AbstractQuartzTaskManager Task scheduled: [-1234][ESB_TASK][fileInbound-FILE--SYNAPSE_INBOUND_ENDPOINT]

The consumer is not created at the broker side.

When executed the micro-integrator.sh stop gives and pause without returning the command prompt.

/home/asanka/wso2mi-1.0.0-m3-SNAPSHOT/wso2/micro-integrator/bin/wso2server.sh: line 135: warning: command substitution: ignored null byte in input
/home/asanka/wso2mi-1.0.0-m3-SNAPSHOT/wso2/micro-integrator/bin/wso2server.sh: line 188: warning: command substitution: ignored null byte in input
/home/asanka/wso2mi-1.0.0-m3-SNAPSHOT/wso2/micro-integrator/bin/wso2server.sh: line 135: warning: command substitution: ignored null byte in input
/home/asanka/wso2mi-1.0.0-m3-SNAPSHOT/wso2/micro-integrator/bin/wso2server.sh: line 188: warning: command substitution: ignored null byte in input
/home/asanka/wso2mi-1.0.0-m3-SNAPSHOT/wso2/micro-integrator/bin/wso2server.sh: line 188: kill: (31586) - No such process

Ideally, the command prompt should return without any errors.

Description:
Review and improve the WSO2 Micro Integrator Docker resources (i.e. Dockerfile and etc.) based on the best practices associated with implementing Dockerfiles [1].

[1]: Best practices for writing Dockerfiles

Suggested Labels:
Type/Improvement

Suggested Assignees:
chirangaalwis

Affected Product Version:
WSO2 Micro Integrator 1.0.0-M5

We could not do it in #74 due to build failures.

Description:
The number of log statements that we have for integrator is too much. Please cut it down to one or two mandatory statements (e.g. which ports that it runs and what artifacts that got deployed).

OS platform

• Ubuntu
• Alpine
• Centos