October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7405) Message counters doesn't work correctly without server reload after enabling statistics

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7405?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6700 to WFLY-7405: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7405 (was: JBEAP-6700) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) > Message counters doesn't work correctly without server reload after enabling statistics > --------------------------------------------------------------------------------------- > > Key: WFLY-7405 > URL: https://issues.jboss.org/browse/WFLY-7405 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > Server is started with queue deployed. Attribute {{statistics-enabled}} is then set to true in messaging server. This operation doesn't require reload. Start sending messages and look at outputs of operation {{list-message-counter-as-json}} or {{list-message-counter-as-html}} at queue you are using to send messages. ({{message-counter-sample-period}} is set to 10s by default, so give it some time). > {code:title=list-message-counter-as-json output} > [standalone@localhost:9990 jms-queue=q] :list-message-counter-as-json > { > "outcome" => "success", > "result" => "{\"destinationName\":\"q\",\"destinationSubscription\":null,\"destinationDurable\":true,\"count\":0,\"countDelta\":0,\"messageCount\":47064,\"messageCountDelta\":809,\"lastAddTimestamp\":\"1/1/70 1:00:00 AM\",\"updateTimestamp\":\"1/1/70 1:00:00 AM\"}" > } > {code} > Only attributes {{messageCount}}, {{messageCountDelta}} contain updated values . Other attributes are either null, 0 or default timestamp. > Output of {{list-message-counter-history-as-json}} is also not correctly updated > {code:title=list-message-counter-history-as-json output} > [standalone@localhost:9990 jms-queue=q] :list-message-counter-history-as-json > { > "outcome" => "success", > "result" => "{\"dayCounters\":[{\"date\":\"10/27/16\",\"counters\":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,0,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1]}]}" > } > {code} > After server {{reload}}, output of operations updates and starts working as expected. > {code:title=Output after reload} > [standalone@localhost:9990 jms-queue=q] :list-message-counter-history-as-json > { > "outcome" => "success", > "result" => "{\"dayCounters\":[{\"date\":\"10/27/16\",\"counters\":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,60015,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1]}]}" > } > [standalone@localhost:9990 jms-queue=q] :list-message-counter-as-json > { > "outcome" => "success", > "result" => "{\"destinationName\":\"q\",\"destinationSubscription\":null,\"destinationDurable\":true,\"count\":60015,\"countDelta\":60015,\"messageCount\":60015,\"messageCountDelta\":60015,\"lastAddTimestamp\":\"10/27/16 11:34:39 AM\",\"updateTimestamp\":\"10/27/16 11:35:29 AM\"}" > } > {code} > Values are also correctly updated when new messages are sent now. > As administrator, I would like to be able to turn on/off statistics also without server reload. Although it is possible with messaging subsystem, it is not working correctly until reload. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1382) AS fails to start with colon in path

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1382?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1382: -------------------------------- Component/s: Modules (was: Scripts) > AS fails to start with colon in path > ------------------------------------ > > Key: WFCORE-1382 > URL: https://issues.jboss.org/browse/WFCORE-1382 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Reporter: James Livingston > > standalone.sh and domain.sh create the module path passed to JBoss Modules -mp option with: > JBOSS_MODULEPATH="$JBOSS_HOME/modules" > The value passed to -mp is a File.pathSeparator (colon on Linux and semicolon on Windows) delimited list of paths, not a single path, so this does not work correctly when JBOSS_HOME contains a colon on Linux, which is a legal but rare character to use in a path. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1382) AS fails to start with colon in path

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1382?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1382: -------------------------------- Priority: Optional (was: Major) > AS fails to start with colon in path > ------------------------------------ > > Key: WFCORE-1382 > URL: https://issues.jboss.org/browse/WFCORE-1382 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Reporter: James Livingston > Priority: Optional > > standalone.sh and domain.sh create the module path passed to JBoss Modules -mp option with: > JBOSS_MODULEPATH="$JBOSS_HOME/modules" > The value passed to -mp is a File.pathSeparator (colon on Linux and semicolon on Windows) delimited list of paths, not a single path, so this does not work correctly when JBOSS_HOME contains a colon on Linux, which is a legal but rare character to use in a path. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-7398: ----------------------------------- Here's all the service code at the time that I hit the issue: https://github.com/wildfly/wildfly-core/pull/1866/commits/9c648ddae228082... > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-7398: ----------------------------------- I'm not certain when the invalid characters actually appear. I assume it must be after I tab, but that's really a guess (there's no visual on-screen indicator that the character is there, at least not on my terminal). > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-697) Add client authentication method to authenticate a TLS peer using a security domain

by David Lloyd (JIRA)

David Lloyd created ELY-697: ------------------------------- Summary: Add client authentication method to authenticate a TLS peer using a security domain Key: ELY-697 URL: https://issues.jboss.org/browse/ELY-697 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: David Lloyd Priority: Minor When a client connects to a remote peer, the authentication protocol in use may support true mutual authentication, where the remote peer (server) has to authenticate itself to the client. Specifically, in the TLS case the client may want to perform client-cert-style authentication with the server certificate, acquiring a SecurityIdentity in return. The client authentication API should have a way to specify that TLS certificate authentication should happen against a specific security domain. It should provide a means to acquire the SecurityIdentity from the SSL session (the same way as a server does, if possible). A server authenticating to a client does not require LoginPermission. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise commented on WFLY-7398: -------------------------------------------- Thank you for your time, in case you have some more free cycles,... As soon as you use tab you get the '\0' right? Whatever the operation? What about /deployment=toto:add(content=[{url=<TAB> Any chance to get the services value-type? Perhaps we have strange values there. Thanks. JF > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-7398: ----------------------------------- Honestly I just tab without even thinking about it so I'm not sure what the exact sequence is but I think I had done: * Type ...add( * Tab * Tab gives ...add(services=[{ * Tab * Tab gives ...add(services=[{uri= * Tab * Tab * Tab... etc. > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1348) Unwanted firing modifying an event over a window:time

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1348: ----------------------------------- Summary: Unwanted firing modifying an event over a window:time Key: DROOLS-1348 URL: https://issues.jboss.org/browse/DROOLS-1348 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco Fix For: 7.0.0.Beta3 Steps to reproduce: 1. In a first rule pattern match on an event over window:time 2. In the consequence of the rule change the value of a field of that event 3. Have a second rule that shouldn't match the value of the field changed by the former rule 4. This second rule fires even if it shouldn't -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1346) Unwanted firing modifying an event over a window:time

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1346?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1346. --------------------------------- Fix Version/s: 7.0.0.Beta3 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/06f5244dfb9be520e8767571f116b... > Unwanted firing modifying an event over a window:time > ----------------------------------------------------- > > Key: DROOLS-1346 > URL: https://issues.jboss.org/browse/DROOLS-1346 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.0.0.Beta3 > > > Steps to reproduce: > 1. In a first rule pattern match on an event over window:time > 2. In the consequence of the rule change the value of a field of that event > 3. Have a second rule that shouldn't match the value of the field changed by the former rule > 4. This second rule fires even if it shouldn't -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 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 October 2016