[JBoss JIRA] (WFLY-13076) Opentracing fails to load on EAR deployment
by Roy Golan (Jira)
[ https://issues.redhat.com/browse/WFLY-13076?page=com.atlassian.jira.plugi... ]
Roy Golan commented on WFLY-13076:
----------------------------------
According to the docs each WAR has its own tracer, so maybe that's the reason my restapi.jar isn't traced by default.
> Opentracing fails to load on EAR deployment
> -------------------------------------------
>
> Key: WFLY-13076
> URL: https://issues.redhat.com/browse/WFLY-13076
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 18.0.1.Final
> Reporter: Roy Golan
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> wildfly 18, an EAR application (ovirt-engine ), I'm trying to enable opentracing, and failing.
> I added this to our xml:
> ```
> <extension module="org.wildfly.extension.microprofile.opentracing-smallrye"/>
> ...
> <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:1.0"/>
> ```
> Exported Jaeger environment vars:
> ```
> export JAEGER_SERVICE_NAME=ovirt-engine
> export JAEGER_REPORTER_LOG_SPANS=true
> export JAEGER_SAMPLER_TYPE=const
> export JAEGER_SAMPLER_PARAM=1
> ```
> And debugged the `TracerProducer` which throws:
> ```
> "Method threw 'org.jboss.weld.exceptions.IllegalStateException' exception. Cannot evaluate org.jboss.weldx.servlet.ServletContext$$Proxy$_$$_WeldClientProxy.toString()"
> ```
> The deployment structure is:
> | engine.ear
> - bll.jar EJB and CDI beans
> - lib/vdsbroker CDI
> | restapi.war JAXRS , also CDI beans
> | Jboss-Modules
> common.jar
> utils.jar
> dal.jar CDI
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13076) Opentracing fails to load on EAR deployment
by Roy Golan (Jira)
[ https://issues.redhat.com/browse/WFLY-13076?page=com.atlassian.jira.plugi... ]
Roy Golan commented on WFLY-13076:
----------------------------------
I can produce an ear and link it, but I think it will be partial.
I also have few observations and a correction to make.
1. the exception I got and reported is probably expected(although should be corrected?) - I @Traced an EJB inside my bll.jar , which is called
internally - thus it doesn't have a servlet context. Must a tracer factory be intialized using servlet context?
2. I removed the `@Traced` EJB and expected that my JAXRS restapi.war to be traced out of the box - but it isn't.
Another thing is that the restapi is not a war at all - it is a jboss module, loading the restapi.jar.
What should I do to trigger the tracing on all the jaxrs resources in that module?
> Opentracing fails to load on EAR deployment
> -------------------------------------------
>
> Key: WFLY-13076
> URL: https://issues.redhat.com/browse/WFLY-13076
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 18.0.1.Final
> Reporter: Roy Golan
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> wildfly 18, an EAR application (ovirt-engine ), I'm trying to enable opentracing, and failing.
> I added this to our xml:
> ```
> <extension module="org.wildfly.extension.microprofile.opentracing-smallrye"/>
> ...
> <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:1.0"/>
> ```
> Exported Jaeger environment vars:
> ```
> export JAEGER_SERVICE_NAME=ovirt-engine
> export JAEGER_REPORTER_LOG_SPANS=true
> export JAEGER_SAMPLER_TYPE=const
> export JAEGER_SAMPLER_PARAM=1
> ```
> And debugged the `TracerProducer` which throws:
> ```
> "Method threw 'org.jboss.weld.exceptions.IllegalStateException' exception. Cannot evaluate org.jboss.weldx.servlet.ServletContext$$Proxy$_$$_WeldClientProxy.toString()"
> ```
> The deployment structure is:
> | engine.ear
> - bll.jar EJB and CDI beans
> - lib/vdsbroker CDI
> | restapi.war JAXRS , also CDI beans
> | Jboss-Modules
> common.jar
> utils.jar
> dal.jar CDI
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-5032:
-----------------------------------
Story Points: 8
Sprint: 2020 Week 07-09 (from Feb 10)
> [DMN Designer] Add support for (un)marshalling disconnected connections
> -----------------------------------------------------------------------
>
> Key: DROOLS-5032
> URL: https://issues.redhat.com/browse/DROOLS-5032
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> Connections leading 'nowhere' are lost after save and reopen the diagram.
> It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node.
> The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4973) Defined DMN collection unary checks do not pass
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4973?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-4973:
--------------------------------
Fix Version/s: 7.33.0.Final
> Defined DMN collection unary checks do not pass
> -----------------------------------------------
>
> Key: DROOLS-4973
> URL: https://issues.redhat.com/browse/DROOLS-4973
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.33.0.Final
>
> Attachments: MySpace_eshop.zip, screenshot-1.png
>
>
> Import the attached project and click Build, then Test.
> The re are defined 2 groups of 2 equivalent tests. In each group one test has a collection unary check defined with UI editor and one test defined a collection unary check with textual editor. The issue is tests with the unary check defined via textual editor do not pass.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5004) Select first cell of Test Scenario
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5004?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5004:
--------------------------------
Fix Version/s: 7.33.0.Final
> Select first cell of Test Scenario
> ----------------------------------
>
> Key: DROOLS-5004
> URL: https://issues.redhat.com/browse/DROOLS-5004
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Blocker
> Labels: drools-tools
> Fix For: 7.33.0.Final
>
>
> Once a Test Scenario file is opened, user is not able to use keyboard to navigate trough the grid. We should fix this by selecting the:
> - First description cell in case of the Model tab
> - First data cell in case of Background tab
> The behavior described above will align behavior of Test Scenario and DMN editors.
> h3. Acceptance criteria
> - User can use keyboard right afterwards opening Test Scenario without need to click to canvas
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5041) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5041:
-----------------------------------
Summary: [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field
Key: DROOLS-5041
URL: https://issues.redhat.com/browse/DROOLS-5041
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.33.0.Final
Reporter: Jozef Marko
Assignee: Guilherme Gomes
Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png
Issue found during DROOLS-4485 review.
When user insert a sibling field in a structure, that contains one field of a structure type, this structure field is expanded, even if it was collapsed before.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months