[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Michael Anstis (Jira)
Michael Anstis created DROOLS-3269:
--------------------------------------
Summary: [DMN Designer] Context: Default can be any expression type
Key: DROOLS-3269
URL: https://issues.jboss.org/browse/DROOLS-3269
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.14.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
The "default" box can be any type of expression, specially decision tables and nested contexts.
Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3268) [DMN Designer] Data-types: Check for use of built-in-type should be case sensitive
by Michael Anstis (Jira)
Michael Anstis created DROOLS-3268:
--------------------------------------
Summary: [DMN Designer] Data-types: Check for use of built-in-type should be case sensitive
Key: DROOLS-3268
URL: https://issues.jboss.org/browse/DROOLS-3268
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.14.0.Final
Reporter: Michael Anstis
Assignee: Guilherme Carreiro
On the Data Types dialog, creating a type/field called "Number" with an uppercase "N" should be allowed. FEEL/DMN is type sensitive, and only "number" lower case is reserved word. Check if the problem also happens for other types, except for "Any" and "Null" that have an upper case initial.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10731) core-threads of ManagedScheduledExecutorService limits number of maximal threads
by Jiri Ondrusek (Jira)
[ https://issues.jboss.org/browse/WFLY-10731?page=com.atlassian.jira.plugin... ]
Jiri Ondrusek commented on WFLY-10731:
--------------------------------------
Behavior of server is correct, property "core-threads" should limit min and also max number.
It's probable that misunderstanding was caused by bad description from [1] - {quote}core-threads The minimum number of threads to be used by the scheduled executor{quote}.
But correct meaning of attribute is (e.g. from [2]): {quote}The mandatory core-threads provides the number of threads to keep in the executor's pool, even if they are idle. A value of 0 means there is no limit.{quote}
But there was also a smaller error - there was missing implementation of "A value of 0 means there is no limit". It was added by PR.
[1] https://wildscribe.github.io/WildFly/14.0/subsystem/ee/managed-scheduled-...
[2] https://docs.jboss.org/author/display/WFLY10/EE+Concurrency+Utilities+Con...
> core-threads of ManagedScheduledExecutorService limits number of maximal threads
> --------------------------------------------------------------------------------
>
> Key: WFLY-10731
> URL: https://issues.jboss.org/browse/WFLY-10731
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 12.0.0.Final
> Reporter: gunter zeilinger
> Assignee: Jiri Ondrusek
> Priority: Major
>
> After changing the default configuration:
> {noformat}
> <managed-scheduled-executor-services>
> - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/>
> + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/>
> </managed-scheduled-executor-services>
> {noformat}
> only 2 (= value of core-threads) threads are used by the Scheduled Executer Service:
> {code:bash}
> $ grep ManagedScheduledExecutorService $WILDFLY/standalone/log/server.log | tail
> 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> {code}
> I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 )
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10731) core-threads of ManagedScheduledExecutorService limits number of maximal threads
by Jiri Ondrusek (Jira)
[ https://issues.jboss.org/browse/WFLY-10731?page=com.atlassian.jira.plugin... ]
Jiri Ondrusek edited comment on WFLY-10731 at 11/7/18 4:17 AM:
---------------------------------------------------------------
Behavior of server is correct, property "core-threads" should limit min and also max number.
It's probable that misunderstanding was caused by bad description from [1] - {quote}core-threads The minimum number of threads to be used by the scheduled executor.{quote}
But correct meaning of attribute is (e.g. from [2]): {quote}The mandatory core-threads provides the number of threads to keep in the executor's pool, even if they are idle. A value of 0 means there is no limit.{quote}
But there was also a smaller error - there was missing implementation of "A value of 0 means there is no limit". It was added by PR.
[1] https://wildscribe.github.io/WildFly/14.0/subsystem/ee/managed-scheduled-...
[2] https://docs.jboss.org/author/display/WFLY10/EE+Concurrency+Utilities+Con...
was (Author: jondruse):
Behavior of server is correct, property "core-threads" should limit min and also max number.
It's probable that misunderstanding was caused by bad description from [1] - {quote}core-threads The minimum number of threads to be used by the scheduled executor{quote}.
But correct meaning of attribute is (e.g. from [2]): {quote}The mandatory core-threads provides the number of threads to keep in the executor's pool, even if they are idle. A value of 0 means there is no limit.{quote}
But there was also a smaller error - there was missing implementation of "A value of 0 means there is no limit". It was added by PR.
[1] https://wildscribe.github.io/WildFly/14.0/subsystem/ee/managed-scheduled-...
[2] https://docs.jboss.org/author/display/WFLY10/EE+Concurrency+Utilities+Con...
> core-threads of ManagedScheduledExecutorService limits number of maximal threads
> --------------------------------------------------------------------------------
>
> Key: WFLY-10731
> URL: https://issues.jboss.org/browse/WFLY-10731
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 12.0.0.Final
> Reporter: gunter zeilinger
> Assignee: Jiri Ondrusek
> Priority: Major
>
> After changing the default configuration:
> {noformat}
> <managed-scheduled-executor-services>
> - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/>
> + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/>
> </managed-scheduled-executor-services>
> {noformat}
> only 2 (= value of core-threads) threads are used by the Scheduled Executer Service:
> {code:bash}
> $ grep ManagedScheduledExecutorService $WILDFLY/standalone/log/server.log | tail
> 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> {code}
> I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 )
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-143) Deployment of application (quickstart/helloworld-rs) triggers CDI warnings for io.smallrye.metrics stuff
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-143?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-143:
-----------------------------------
Fix proposed upstream at https://github.com/smallrye/smallrye-metrics/pull/20
> Deployment of application (quickstart/helloworld-rs) triggers CDI warnings for io.smallrye.metrics stuff
> --------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-143
> URL: https://issues.jboss.org/browse/WFWIP-143
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Deployment of application (quickstart/helloworld-rs) triggers CDI warning for io.smallrye.metrics stuff
> {code}
> 13:42:42,723 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricProducer is deprecated from CDI 1.1!
> 13:42:42,734 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MetricNameFactory is deprecated from CDI 1.1!
> 13:42:42,736 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MetricsInterceptor is deprecated from CDI 1.1!
> 13:42:42,741 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricRegistries is deprecated from CDI 1.1!
> 13:42:42,744 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MeteredInterceptor is deprecated from CDI 1.1!
> 13:42:42,750 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.CountedInterceptor is deprecated from CDI 1.1!
> 13:42:42,753 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.TimedInterceptor is deprecated from CDI 1.1!
> 13:42:42,756 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricsRequestHandler is deprecated from CDI 1.1!
> {code}
> These WARN messages must go away by using proper api. Some EAP customers are doing log auditing and analysis for each entry which is INFO+.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10919) INFO message Initialized tracer=JaegerTracer is too verbose
by Juraci Paixão Kröhling (Jira)
[ https://issues.jboss.org/browse/WFLY-10919?page=com.atlassian.jira.plugin... ]
Juraci Paixão Kröhling commented on WFLY-10919:
-----------------------------------------------
I'm sorry, I lost track of this one. I'll schedule this for our next sprint, starting next Monday. This is being tracked on my side via TRACING-313. Sorry about that!
> INFO message Initialized tracer=JaegerTracer is too verbose
> -----------------------------------------------------------
>
> Key: WFLY-10919
> URL: https://issues.jboss.org/browse/WFLY-10919
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Stourac
> Assignee: Juraci Paixão Kröhling
> Priority: Major
>
> Following log message is logged during the deploy operation of a deployment:
> {code}
> 10:52:11,703 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer=JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> This information is too verbose for INFO level. I propose to do one of following:
> # Remove this log message from INFO level - note that very similar message is also logged on DEBUG level:
> {code}
> 10:52:11,714 DEBUG [org.wildfly.microprofile.opentracing.smallrye] (ServerService Thread Pool -- 72) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-0.30.6, serviceName=helloworld-rs.war, reporter=RemoteReporter(sender=UdpSender(), closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-10-40-5-80.brq.redhat.com, jaeger.version=Java-0.30.6, ip=10.40.5.80}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> {code}
> # Simplify the log message on INFO level to something simple, like:
> {code}
> 10:52:11,703 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer for service helloworld-rs.war
> {code}
> This issue is a followup of a WFLY-10904.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months