May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4472) Upgrade Undertow to 2.0.21.Final

by Lin Gao (Jira)

Lin Gao created WFCORE-4472: ------------------------------- Summary: Upgrade Undertow to 2.0.21.Final Key: WFCORE-4472 URL: https://issues.jboss.org/browse/WFCORE-4472 Project: WildFly Core Issue Type: Component Upgrade Reporter: Lin Gao Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6684) JMS Bridge should display statistics about messages that have been processed.

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-6684?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6684: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12179 (was: https://github.com/wildfly/wildfly/pull/12000) > JMS Bridge should display statistics about messages that have been processed. > ----------------------------------------------------------------------------- > > Key: WFLY-6684 > URL: https://issues.jboss.org/browse/WFLY-6684 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Environment: JBoss EAP 7 > Reporter: Chen Maoqian > Assignee: Emmanuel Hugonnet > Priority: Major > Attachments: JBEAP-4653.patch > > > The JMS bridge should show some statistics about messages that have been processed through the bridge for example: > - number of messages successfully committed > - number of messages aborted/rollback -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-655) Customizable Console Log Viewer

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-655?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-655. -------------------------------- Resolution: Won't Do I'm closing this as won't do because it was intentional that the log viewer only works on the {{jboss.server.log.dir}} path. > Customizable Console Log Viewer > ------------------------------- > > Key: WFCORE-655 > URL: https://issues.jboss.org/browse/WFCORE-655 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Carlton Zachary > Assignee: James Perkins > Priority: Optional > > Currently the Console log viewer only points to jboss.server.log.dir. In our Domain environment we have our server.log write to a non-default location. This is defined in the host-slave.xml as: > <paths> > <path name="custom.jboss.server.log.dir" path="/apps/logs/server1"/> > </paths> > it is then referenced in the domain.xml file logging subsystem as: > <file relative-to="custom.jboss.server.log.dir" path="server.log"/> > Can the Console logviewer be enhanced to allow it to be configured to point to a custom server.log location? > https://bugzilla.redhat.com/show_bug.cgi?id=1191180 > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-246) Wildfly 16 incorrect working log zip rotator

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-246?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-246: -------------------------------------- I can duplicate this in WildFly. I'll attempt to create a test for the log manager that reproduces this issue as well so a fix can be worked on. > Wildfly 16 incorrect working log zip rotator > -------------------------------------------- > > Key: LOGMGR-246 > URL: https://issues.jboss.org/browse/LOGMGR-246 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Environment: Windows, > Oracle JDK 8 > Reporter: Igor Dmitriev > Assignee: James Perkins > Priority: Major > > My logging profile configuration is: > 1) > {code:xml} > <periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true"> > <level name="ALL"/> > <file relative-to="jboss.server.log.dir" path="corp.log"/> > <rotate-size value="300k"/> > <max-backup-index value="10000"/> > <suffix value=".yyyy-MM-dd.zip"/> > <append value="true"/> > </periodic-size-rotating-file-handler> > {code} > File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size. > 2) > {code:xml} > <periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true"> > <level name="ALL"/> > <file relative-to="jboss.server.log.dir" path="corp.log"/> > <rotate-size value="300k"/> > <max-backup-index value="10000"/> > <suffix value=".yyyy-MM-dd.zip"/> > <append value="false"/> > </periodic-size-rotating-file-handler> > {code} > All work as expected, except each time corp.log reach 300k, appear pair .zip files with same content? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3997) [DMN Designer] Included Model Name marshalling issues depending on imported model name

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3997?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3997: --------------------------------------- [~dadossan] [~karreiro] I am confused why a whitespace in the name would cause any problem? Whitespaces are valid characters in names. > [DMN Designer] Included Model Name marshalling issues depending on imported model name > -------------------------------------------------------------------------------------- > > Key: DROOLS-3997 > URL: https://issues.jboss.org/browse/DROOLS-3997 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-05-10 08-20-54.png, Screenshot from 2019-05-10 08-28-42.png > > > There is issue in marshalling, if the included model name contains *whitespace* character. In such case xml editor is opened instead of the dmn editor. See the attached picture and steps to reproduce for more details. > Issue spotted during review of DROOLS-3720 and DROOLS-3721. However it is probably not related. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3674: ------------------------------------------ [~zhutaojiajia] [~uxdlc] The last version with this popover is available for you to see on any of the server here http://kieci-02.lab.eng.brq.redhat.com:8080/kie-docker-ui-webapp/ so you may have an idea by yourself. As per keyboard trigger, I think there is none currently. If needed, we'll take care of that. > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11907) NPE trying to use Resteasy Client inside CDI Async Event

by Cody Lerum (Jira)

[ https://issues.jboss.org/browse/WFLY-11907?page=com.atlassian.jira.plugin... ] Cody Lerum commented on WFLY-11907: ----------------------------------- [~ron_sigal] Do you need me to create a RESTEASY issue for this as well? I would hate for this to miss the WFLY 17 window and be broken for another quarter. > NPE trying to use Resteasy Client inside CDI Async Event > -------------------------------------------------------- > > Key: WFLY-11907 > URL: https://issues.jboss.org/browse/WFLY-11907 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 14.0.0.Final, 16.0.0.Final > Reporter: Cody Lerum > Assignee: Ronald Sigal > Priority: Major > > When attempting to use the Resteasy Client inside a CDI Async Event a NPE is thrown. > {code} > 12:49:33,513 ERROR [stderr] (Weld Thread Pool -- 4) java.lang.RuntimeException: java.lang.NullPointerException > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:49) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.getProviderFactory(ResteasyClientBuilder.java:362) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:395) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:38) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.load(ResteasyClientEventObserver.java:28) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.observeAsync(ResteasyClientEventObserver.java:23) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.reflect.Method.invoke(Method.java:498) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.MethodInvocationStrategy$DefaultMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:109) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124) > 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.util.Observers.notify(Observers.java:166) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.notifyAsyncObserver(ObserverNotifier.java:413) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$notifyAsyncObservers$5(ObserverNotifier.java:356) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$null$8(ObserverNotifier.java:438) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.security.spi.SecurityServices.lambda$getSecurityContextAssociator$0(SecurityServices.java:80) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$createSupplier$9(ObserverNotifier.java:435) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1590) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.Thread.run(Thread.java:748) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.threads.JBossThread.run(JBossThread.java:485) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) Caused by: java.lang.NullPointerException > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProviders(RegisterBuiltin.java:60) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:45) > 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) ... 28 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3674: ---------------------------------------- [~uxdlc] Is the Wikipedia popover link correct?!? I'd be surprised if the scesim editor baked tasty pastries. > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3674: ------------------------------------------- [~danielezonca][~gabriolo] Question does is behave more like the hover tips here: https://en.wikipedia.org/wiki/Popover. or more like the hover tips here: https://www.patternfly.org/pattern-library/widgets/#tooltip. Are there any keyboard triggers for the popovers? > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4471) Bump the Elytron subsystem version

by Farah Juma (Jira)

Farah Juma created WFCORE-4471: ---------------------------------- Summary: Bump the Elytron subsystem version Key: WFCORE-4471 URL: https://issues.jboss.org/browse/WFCORE-4471 Project: WildFly Core Issue Type: Task Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 10.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019