November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4225) INFO message Initialized tracer=JaegerTracer is too verbose

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4225?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-10919 to WFCORE-4225: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4225 (was: WFLY-10919) Component/s: Logging (was: MP OpenTracing) Affects Version/s: (was: 14.0.0.Beta2) > INFO message Initialized tracer=JaegerTracer is too verbose > ----------------------------------------------------------- > > Key: WFCORE-4225 > URL: https://issues.jboss.org/browse/WFCORE-4225 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Jan Stourac > Assignee: James Perkins > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10919) INFO message Initialized tracer=JaegerTracer is too verbose

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10919?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10919: -------------------------------------- Okay. I'll assign this to myself and get a PR into today for it then. > 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 > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10919) INFO message Initialized tracer=JaegerTracer is too verbose

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10919?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-10919: ------------------------------------ Assignee: James Perkins (was: Juraci Paixão Kröhling) > 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 > Reporter: Jan Stourac > Assignee: James Perkins > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Daniele Zonca edited comment on DROOLS-3098 at 11/13/18 12:29 PM: ------------------------------------------------------------------ [~uxdlc] Example: I have DO with this structure {code:java} PhoneNumber(String prefix, String number); Contact(String address, List[PhoneNumber] phoneNumbers); ContactList(Map[String, Contact] contacts) {code} I would like to create a column that is mapped to a phone number: ContactList.contacts["ContactName"].phoneNumbers[index].number I cannot do it now because I can only navigate through the tree element in the UI and I have no way to access into contacts *map* and the same which phone number in the *list* I want to use was (Author: danielezonca): [~uxdlc] Example: I have DO with this structure {code:java} PhoneNumber(String prefix, String number); Contact(String address, List[PhoneNumber] phoneNumbers); ContactList(Map[String, Contact] contacts) {code} I would like to create a column that is mapped to a phone number: Agenda.contacts["ContactName"].phoneNumbers[index].number I cannot do it now because I can only navigate through the tree element in the UI and I have no way to access into contacts *map* and the same which phone number in the *list* I want to use > UX: Add support for map and list > -------------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3192) [DMN Designer] Undefined Expression Grid: Re-design 'decision logic' selector

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3192?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3192: ------------------------------------- silence is golden, please feel free to reopen as needed. :) > [DMN Designer] Undefined Expression Grid: Re-design 'decision logic' selector > ----------------------------------------------------------------------------- > > Key: DROOLS-3192 > URL: https://issues.jboss.org/browse/DROOLS-3192 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: drools-tools > Attachments: logic_pop-over.png > > > * The {{UndefinedExpression}} grid "decision logic" selector (menu to select logic type: Literal expression, Context, etc.) currently uses a double-left mouse click to launch the menu. Given the menu is closer in spirit (and intention) to a popover menu - to provide a more consistent and predictable user experience it would be preferable to launch this menu on a single, left mouse click (will be covered by DROOLS-2910). > * Re-design the {{UndefinedExpression}} grid "decision logic" selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3192) [DMN Designer] Undefined Expression Grid: Re-design 'decision logic' selector

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3192?page=com.atlassian.jira.plugi... ] Liz Clayton resolved DROOLS-3192. --------------------------------- Resolution: Done design provided > [DMN Designer] Undefined Expression Grid: Re-design 'decision logic' selector > ----------------------------------------------------------------------------- > > Key: DROOLS-3192 > URL: https://issues.jboss.org/browse/DROOLS-3192 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: drools-tools > Attachments: logic_pop-over.png > > > * The {{UndefinedExpression}} grid "decision logic" selector (menu to select logic type: Literal expression, Context, etc.) currently uses a double-left mouse click to launch the menu. Given the menu is closer in spirit (and intention) to a popover menu - to provide a more consistent and predictable user experience it would be preferable to launch this menu on a single, left mouse click (will be covered by DROOLS-2910). > * Re-design the {{UndefinedExpression}} grid "decision logic" selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3314) Add method to configure WorkItemManagerFactory programmatically

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3314: -------------------------------------- Summary: Add method to configure WorkItemManagerFactory programmatically Key: DROOLS-3314 URL: https://issues.jboss.org/browse/DROOLS-3314 Project: Drools Issue Type: Enhancement Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi Currently only a property can be used. This JIRA is to track adding a simple setter to SessionConfiguration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3212) Scenario simulation can not be closed without a warning if it has been ran

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3212?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3212. ------------------------------------ Resolution: Cannot Reproduce Can not reproduce > Scenario simulation can not be closed without a warning if it has been ran > -------------------------------------------------------------------------- > > Key: DROOLS-3212 > URL: https://issues.jboss.org/browse/DROOLS-3212 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Toni Rikkola > Assignee: Gabriele Cardosi > Priority: Major > > The problem is caused by the fact that running the simulation updates the model. > Steps to reproduce: > Open scesim asset. > Run the scenario. > Close the editor > You get a warning that there are unsaved changes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-151) HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFWIP-151?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated WFWIP-151: ------------------------------------ Issue Type: Enhancement (was: Bug) > HTTP Verb OPTIONS requires to have Accept header defined, response should provide some guidance about this > ---------------------------------------------------------------------------------------------------------- > > Key: WFWIP-151 > URL: https://issues.jboss.org/browse/WFWIP-151 > Project: WildFly WIP > Issue Type: Enhancement > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > HTTP Verb OPTIONS requires to have Accept header defined > {code} > $ curl -X OPTIONS http://127.0.0.1:10090/metrics/vendor > No exporter found for method OPTIONS and media type > {code} > I have to specify json mediatype > {code} > curl -X OPTIONS -H "Accept: application/json" http://127.0.0.1:10090/metrics/vendor > {code} > I was expecting that I get -the json response or at least more- helpful message. > OpenLiberty returns > {code} > Error 406: CWMMC0000I: The accept header format */* is incorrect. > {code} > which at least points user to define proper header > Update: > Spec requires header to be defined, so WF could be a bit more helpful in the response message > {code} > The implementation must return a 406 response code if the request’s HTTP Accept header > for an OPTIONS request does not match application/json. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-152) Metrics endpoint should inform about supported request types, HTTP code change to be considered

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFWIP-152: --------------------------------------- Summary: Metrics endpoint should inform about supported request types, HTTP code change to be considered Key: WFWIP-152 URL: https://issues.jboss.org/browse/WFWIP-152 Project: WildFly WIP Issue Type: Enhancement Components: MP Metrics Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Metrics endpoint could inform about supported request types, current response is {code} curl http://127.0.0.1:10090/metrics/vendor -X PUT No exporter found for method PUT and media type {code} OpenLiberty provide info which HTTP verbs are supported {code} curl https://localhost:9443/metrics/ --insecure -u theUser:thePassword -X PUT Error 405: CWMMC0001I: The method request type must be GET or OPTIONS. {code} Side comment - We return {{< HTTP/1.1 406 Not Acceptable}}, OpenLiberty returns {{< HTTP/1.1 405 Method Not Allowed}} which feels more appropriate. Spec speaks only about 404 and 406. {code} • 404 if a directly-addressed item does not exist. This may be a non-existing sub-tree or non- existing object • 406 if the HTTP Accept Header in the request cannot be handled by the server. {code} But 406 only mentions Accept Header, not the HTTP verb. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018