1、match 为 port=xxxx，没法注入故障 2、match 为 sqlType=insert，包括 select 等在内的所有 mysql 操作都被注入了故障

附录：使用的版本 spec： matchers: - desc: The sql type, for example, select, update and so on. name: sqltype noArgs: false required: false - desc: The database name which used name: database noArgs: false required: false - desc: The database port which used name: port noArgs: false required: false - desc: The database host name: host noArgs: false required: false - desc: The first table name in sql. name: table noArgs: false required: false

Signed-off-by: wufan [email protected]

Describe what this PR does / why we need it

    Provides the ability to match specific business data for injection by getting business data from rpc or implementing the specific spi interface.

Does this pull request fix one issue?

   Fixes #203

Describe how you did it

blade create dubbo throwCustomException --consumer --service=com.qunar.api --version=1.0.0  --b-parms='[{
"key":"a",
"value":"a_value",
“mode”:"spi"
},
{
"key":"b",
"value":"b_value",
“mode”:"spi"
}]’

~/chaosblade-0.0.3 # ./blade prepare jvm --process XXX {"code":604,"success":false,"error":"com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded\n\tat sun.tools.attach.LinuxVirtualMachine.\u003cinit\u003e(LinuxVirtualMachine.java:106)\n\tat sun.tools.attach.LinuxAttachProvider.attachVirtualMachine(LinuxAttachProvider.java:63)\n\tat com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:208)\n\tat com.alibaba.jvm.sandbox.core.CoreLauncher.attachAgent(CoreLauncher.java:59)\n\tat com.alibaba.jvm.sandbox.core.CoreLauncher.\u003cinit\u003e(CoreLauncher.java:20)\n\tat com.alibaba.jvm.sandbox.core.CoreLauncher.main(CoreLauncher.java:43)\nsandbox load jvm failed : Unable to open socket file: target process not responding or HotSpot VM not loaded\n exit status 255","result":"069b4c4004e1c3ff"}

NAME="SLES" VERSION="12-SP2" VERSION_ID="12.2" PRETTY_NAME="SUSE Linux Enterprise Server 12 SP2" ID="sles" ANSI_COLOR="0;32"

Describe what this PR does / why we need it

Does this pull request fix one issue?

#96 fix unable to find non-public method of super class

Describe how you did it

Describe how to verify it

Special notes for reviews

Describe what this PR does / why we need it

Does this pull request fix one issue?

Fixes #49: Dubbo interceptor should support group

Describe how you did it

split dubbo service into group,service and version

Issue Description

Type: feature request

Describe what happened (or what feature you want)

Add support delay for Log framework, such as logback.

Describe what you expected to happen

blade create log delay --time 500 --effect-count 100

Describe what this PR does / why we need it

Fix bug

Does this pull request fix one issue?

Yes

Fixes #8

Describe how you did it

Describe how to verify it

Special notes for reviews

Issue Description

Type: bug report

There is an issue when I throw an self-defined Exception which don't have a with-param constructor.

For example,

1.Self-defined Exception which don't hava a with-param constructor And it will get error when I execute ted or tcd experiment

2.But doing this with an Exception which have a with-param constructor get another result

Issue Description

Type: bug report or feature request

Describe what happened (or what feature you want)

Describe what you expected to happen

Chaosblade-exec-plugin-kafka 拦截点分析

Kafka支持2种基础故障场景注入：Delay 和 throw custom exception

这2种演练场景是JVM框架层通用的故障场景。

针对没有外部网络交互的方法层面的delay，delay的处理逻辑很简单，只需要在指定的方法层面进行注入即可，即在执行到对应方法时进行延时注入； 但是在对有外部网络交互的方法层面的delay模拟时，delay此时的语义应该尽可能模拟网络的超时，实现类似真实网络超时的效果；

因而对于有外部网络交互的Delay应该有这样的语义：

1. 不网卡即可以达到模拟发送超时的目的；
2. 比网卡超时注入有更精确的控制粒度，如超时几次；
3. 尽可能模拟外部超时的现象，最好能够触发和网络超时一样的异常；

基于上述对Delay故障定义的描述 让我们看看如何对Kafka组件进行延时发送故障模拟

Kafka发送的流程是异步解耦的，大致可以分为2部分 消息组装后暂存到Deque； Sender线程从Deque中取出消息添加到InFlightRequests队列中，最后投递出去；

因此我们需要做的是在消息暂存到Deque后进行超时故障的注入，即发送的第二个环节；

再来看Kafka对消息超时的判定：

1. Deque中超时的消息；
2. Inflight中超时的消息；

由此得出以下3种方式：

1. 直接在Deque后注入超时（Sender.run）；
2. 在添加到InflightRequest请求中时进行延时注入；
3. 在将InflightRequest中的请求进行投递时进行超时注入； 分别对3种方式进行探究： 第一种场景，范围较大，相当于sender线程每次需要投递时就休眠对应时间，造成的后果是会影响其他待发送的消息，这样的话影响的消息条数不可控； 第二种场景，在doSend方法中添加到Inflight前进行延时故障注入 因为doSend方法依然是异步的，这是标记write状态，因此如果在这里执行超时，也会影响后续待发送消息； 第三种场景，在执行网络投递时进行延时注入； Kafka真正网络投递的方法是NetworkClient.poll（注意，consumer的ack也是在这里）,如果在这里，会影响消息的ack；

因此综合考虑，基于kafka的批量特性，kafka的发送延时无法实现任何场景下的精确数量命中，不过也能符合大多数场景需求了，暂时就这样吧。 后面我会提个pr，大佬review一下

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?

Describe what this PR does / why we need it

add business param pattern match

Does this pull request fix one issue?

fixes:https://github.com/chaosblade-io/chaosblade-exec-jvm/issues/227

Describe how you did it

Describe how to verify it

Special notes for reviews

Describe what this PR does / why we need it

support jvm return any type

Does this pull request fix one issue?

Fixes:https://github.com/chaosblade-io/chaosblade-exec-jvm/issues/223

Describe how you did it

Describe how to verify it

Special notes for reviews

Issue Description

Type: bug report

Describe what happened (or what feature you want)

servlet modifyCode not support b-params

Describe what you expected to happen

servlet modifyCode support b-params

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Describe what this PR does / why we need it

Does this pull request fix one issue?

fixes:https://github.com/chaosblade-io/chaosblade-exec-jvm/issues/291

Describe how you did it

Describe how to verify it

Special notes for reviews

Issue Description

Type: bug report

Describe what happened (or what feature you want)

在注入oom故障时，每次填充的内存大小并不是严格按照 block参数进行填充。 因为在创建oomObject对象时，使用的是byte[1024*300], 经过new String()后让内存分配翻倍。

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?

Describe what this PR does / why we need it

Does this pull request fix one issue?

fixes:https://github.com/chaosblade-io/chaosblade-exec-jvm/issues/289

Describe how you did it

Describe how to verify it

Special notes for reviews

Issue Description

Type: bug report

Describe what happened (or what feature you want)

    public static Boolean getActionFlag(EnhancerModel enhancerModel, String flagKey, Boolean defaultValue) {
        String value = getActionFlag(enhancerModel, flagKey);
        if (value == null) { return defaultValue; }
        try {
            return Boolean.parseBoolean(flagKey);
        } catch (Exception ex) {
            return defaultValue;
        }
    }

should is return Boolean.parseBoolean(value);

This causes the oom exception wild mode to be invalid

Describe what you expected to happen

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?