[Red Hat JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-2254?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-2254:
-----------------------------------
Fix Version/s: (was: 7.45.0.Final)
> Automate .proto files rebuild in pom.xml
> ----------------------------------------
>
> Key: DROOLS-2254
> URL: https://issues.redhat.com/browse/DROOLS-2254
> Project: Drools
> Issue Type: Task
> Components: tools
> Affects Versions: 7.5.0.Final
> Reporter: Dmitry Volodin
> Assignee: Dmitry Volodin
> Priority: Minor
>
> According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files.
> This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (JGRP-2430) GossipRouter: more efficient routing
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2430?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2430:
--------------------------------
There are 2 types of input/output: InputStream/OutputStream (TCP) and ByteBuffer (TCP_NIO2).
* InputStream: there is no native way of transferring N bytes from input to outout for 1-1 messages. Ditto for 1-m messages; even if there was, we can't pass the same InputStream transfer to multiple OutputStreams, as reading off of the input stream advances the read pointer
* ByteBuffer: here, we can pass the ByteBuffer read from the input to multiple outputs, but - as reading advances the {{position}} of a ByteBuffer, we need to call {{duplicate()}} on the ByteBuffer before passing it to the output.
All in all, these are rather modest improvements...
> GossipRouter: more efficient routing
> ------------------------------------
>
> Key: JGRP-2430
> URL: https://issues.redhat.com/browse/JGRP-2430
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.1
>
>
> GossipRouter supports both NIO (ByteBuffer) and TCP (stream-based) connections. In both cases, however, the entire message is read and then routed to the destination address.
> It would be better to only read the cluster name and target address, and then use efficient stream-to-stream (or channel-to-channel) _transfer mechanisms_, which avoids temporary copies of data and the full reading of messages.
> Also look into routing of entire message _batches_.
> Investigate whether this is possible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5670) DMN produce programmatically Swagger/OpenAPI components type info
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5670?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5670:
-----------------------------------
Labels: kogito (was: )
> DMN produce programmatically Swagger/OpenAPI components type info
> -----------------------------------------------------------------
>
> Key: DROOLS-5670
> URL: https://issues.redhat.com/browse/DROOLS-5670
> Project: Drools
> Issue Type: Story
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Labels: kogito
>
> *Motivation*: generating Swagger definitions from annotation proved limiting
> *Goals*: generate JSONSchema Component for Swagger/OpenAPI programmatically from the DMN model definition, since this gives fine tuned control would overcome the current limitation from annotation based strategies.
> *Impacts*: none --eventually Kogito, Kie7, etc. can make use of this later
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5670) DMN produce programmatically Swagger/OpenAPI components type info
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5670?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5670:
-----------------------------------
Fix Version/s: 7.46.0.Final
> DMN produce programmatically Swagger/OpenAPI components type info
> -----------------------------------------------------------------
>
> Key: DROOLS-5670
> URL: https://issues.redhat.com/browse/DROOLS-5670
> Project: Drools
> Issue Type: Story
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Labels: kogito
> Fix For: 7.46.0.Final
>
>
> *Motivation*: generating Swagger definitions from annotation proved limiting
> *Goals*: generate JSONSchema Component for Swagger/OpenAPI programmatically from the DMN model definition, since this gives fine tuned control would overcome the current limitation from annotation based strategies.
> *Impacts*: none --eventually Kogito, Kie7, etc. can make use of this later
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5727) DMN OAS decision service support and refactorings
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5727?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5727:
-----------------------------------
Description:
in this fina iteration for [DROOLS-5670] :
* decision service support
* avoid naming collisions
* refactoring
was:in this first iteration for [DROOLS-5670] it focus on generating all OAS/JSONSchema definitions for DMN types and input/output of the whole model
> DMN OAS decision service support and refactorings
> -------------------------------------------------
>
> Key: DROOLS-5727
> URL: https://issues.redhat.com/browse/DROOLS-5727
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
>
> in this fina iteration for [DROOLS-5670] :
> * decision service support
> * avoid naming collisions
> * refactoring
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5727) DMN OAS decision service support and refactorings
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5727?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5727:
-----------------------------------
Description:
in this final iteration for [DROOLS-5670] :
* decision service support
* avoid naming collisions
* refactoring
was:
in this fina iteration for [DROOLS-5670] :
* decision service support
* avoid naming collisions
* refactoring
> DMN OAS decision service support and refactorings
> -------------------------------------------------
>
> Key: DROOLS-5727
> URL: https://issues.redhat.com/browse/DROOLS-5727
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
>
> in this final iteration for [DROOLS-5670] :
> * decision service support
> * avoid naming collisions
> * refactoring
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5727) DMN OAS decision service support and refactorings
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5727:
--------------------------------------
Summary: DMN OAS decision service support and refactorings
Key: DROOLS-5727
URL: https://issues.redhat.com/browse/DROOLS-5727
Project: Drools
Issue Type: Feature Request
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
in this first iteration for [DROOLS-5670] it focus on generating all OAS/JSONSchema definitions for DMN types and input/output of the whole model
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5725) kie-plugins-testing in droolsjbpm-integration tries to resolve a 1.0.0 version of kie
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5725?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5725:
---------------------------------
Description:
And fails after a timeout.
```
2020-10-14 10:31:35,426 [main] INFO Asking for kjar kjar-11-simple-kjar-with-droolsmodelcompiler [-Dorg.kie.version=7.45.0-SNAPSHOT, -DgenerateModel=NO] [clean, install]
2020-10-14 10:31:35,821 [main] INFO Compiling kjar kjar-11-simple-kjar-with-droolsmodelcompiler 3.3.9 [clean, install]
2020-10-14 10:31:49,806 [main] WARN Unable to resolve artifact: org.kie:kie-api:1.0.0.Final
2020-10-14 10:31:51,496 [main] WARN Unable to resolve artifact: org.kie:kie-api:pom:1.0.0.Final
2020-10-14 10:31:53,045 [main] WARN Unable to resolve artifact: org.kie:kie-api:1.0.0.Final
2020-10-14 10:31:54,588 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:1.0.0.Final
2020-10-14 10:31:56,100 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:pom:1.0.0.Final
2020-10-14 10:31:57,684 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:1.0.0.Final
2020-10-14 10:31:59,250 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:1.0.0.Final
2020-10-14 10:32:00,848 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:pom:1.0.0.Final
2020-10-14 10:32:02,402 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:1.0.0.Final
```
This doesn't affect the test correctness, but it slows the build.
Check also the other integration tests
One solution could be to use maven-invoker
was:
And fails after a timeout.
```
2020-10-14 10:31:35,426 [main] INFO Asking for kjar kjar-11-simple-kjar-with-droolsmodelcompiler [-Dorg.kie.version=7.45.0-SNAPSHOT, -DgenerateModel=NO] [clean, install]
2020-10-14 10:31:35,821 [main] INFO Compiling kjar kjar-11-simple-kjar-with-droolsmodelcompiler 3.3.9 [clean, install]
2020-10-14 10:31:49,806 [main] WARN Unable to resolve artifact: org.kie:kie-api:1.0.0.Final
2020-10-14 10:31:51,496 [main] WARN Unable to resolve artifact: org.kie:kie-api:pom:1.0.0.Final
2020-10-14 10:31:53,045 [main] WARN Unable to resolve artifact: org.kie:kie-api:1.0.0.Final
2020-10-14 10:31:54,588 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:1.0.0.Final
2020-10-14 10:31:56,100 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:pom:1.0.0.Final
2020-10-14 10:31:57,684 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:1.0.0.Final
2020-10-14 10:31:59,250 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:1.0.0.Final
2020-10-14 10:32:00,848 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:pom:1.0.0.Final
2020-10-14 10:32:02,402 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:1.0.0.Final
```
This doesn't affect the test correctness, but it slows the build.
Check also the other integration tests
> kie-plugins-testing in droolsjbpm-integration tries to resolve a 1.0.0 version of kie
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-5725
> URL: https://issues.redhat.com/browse/DROOLS-5725
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> And fails after a timeout.
> ```
> 2020-10-14 10:31:35,426 [main] INFO Asking for kjar kjar-11-simple-kjar-with-droolsmodelcompiler [-Dorg.kie.version=7.45.0-SNAPSHOT, -DgenerateModel=NO] [clean, install]
> 2020-10-14 10:31:35,821 [main] INFO Compiling kjar kjar-11-simple-kjar-with-droolsmodelcompiler 3.3.9 [clean, install]
> 2020-10-14 10:31:49,806 [main] WARN Unable to resolve artifact: org.kie:kie-api:1.0.0.Final
> 2020-10-14 10:31:51,496 [main] WARN Unable to resolve artifact: org.kie:kie-api:pom:1.0.0.Final
> 2020-10-14 10:31:53,045 [main] WARN Unable to resolve artifact: org.kie:kie-api:1.0.0.Final
> 2020-10-14 10:31:54,588 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:1.0.0.Final
> 2020-10-14 10:31:56,100 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:pom:1.0.0.Final
> 2020-10-14 10:31:57,684 [main] WARN Unable to resolve artifact: org.drools:drools-model-compiler:1.0.0.Final
> 2020-10-14 10:31:59,250 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:1.0.0.Final
> 2020-10-14 10:32:00,848 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:pom:1.0.0.Final
> 2020-10-14 10:32:02,402 [main] WARN Unable to resolve artifact: org.drools:drools-canonical-model:1.0.0.Final
> ```
> This doesn't affect the test correctness, but it slows the build.
> Check also the other integration tests
>
> One solution could be to use maven-invoker
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[Red Hat JIRA] (WFCORE-5146) WFLYPRT0057 message handling improvement
by Katarína Hermanová (Jira)
[ https://issues.redhat.com/browse/WFCORE-5146?page=com.atlassian.jira.plug... ]
Katarína Hermanová updated WFCORE-5146:
---------------------------------------
Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/4364)
> WFLYPRT0057 message handling improvement
> ----------------------------------------
>
> Key: WFCORE-5146
> URL: https://issues.redhat.com/browse/WFCORE-5146
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI, Management, Remoting
> Reporter: Katarína Hermanová
> Assignee: Katarína Hermanová
> Priority: Major
>
> WFLYPRT0057 message may or may not be output.
> This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_).
> {code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java}
> 126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable {
> --- snip ---
> 135 @Override
> 136 public Cancellable cancel() {
> 137 if (cancellable && cancelled.compareAndSet(false, true)) {
> 138 final Thread thread = this.thread;
> 139 if(thread != null) {
> 140 thread.interrupt();
> 141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread);
> 142 }
> 143 }
> 144 return this;
> 145 }
> --- snip ---
> 152 @Override
> 153 public void run() {
> 154 if (cancellable && cancelled.get()) {
> 155 Thread.currentThread().interrupt();
> 156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName());
> 157 }
> 158 this.thread = Thread.currentThread();
> 159 try {
> 160 doExecute();
> 161 } finally {
> 162 this.thread = null;
> 163 }
> 164 }
> {code}
> The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_).
> This is just a timing, we cannot determine the need for this message.
> {noformat}
> - Thread dump
> "management task-2" #139 prio=5 os_prio=0 tid=0x0000562c38351800 nid=0x3626 at breakpoint[0x00007facf3098000]
> java.lang.Thread.State: RUNNABLE
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.cancel(ManagementRequestContextImpl.java:141)
> at org.jboss.as.protocol.mgmt.ActiveOperationImpl.asyncCancel(ActiveOperationImpl.java:150)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.cancelAllActiveOperations(AbstractMessageHandler.java:441)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.shutdownNow(AbstractMessageHandler.java:150)
> at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:181)
> at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:178)
> at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:520)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:425)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:150)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleEnd(ManagementChannelReceiver.java:129)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:273)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$$Lambda$737/243506564.run(Unknown Source)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor$$Lambda$720/801134859.run(Unknown Source)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> "management-handler-thread - 3" #145 prio=5 os_prio=0 tid=0x0000562c38d5b000 nid=0x3b80 at breakpoint[0x00007facf416f000]
> java.lang.Thread.State: RUNNABLE
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:162)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> - log
> 09:45:24,686 INFO [org.jboss.as.protocol] (management task-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 3,5,management-handler-thread]{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months