April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-710) E2E Job Error "Archiving artifacts"

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-710?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-710: ----------------------------------- Assignee: Filip Brychta > E2E Job Error "Archiving artifacts" > ----------------------------------- > > Key: SWSQE-710 > URL: https://issues.jboss.org/browse/SWSQE-710 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > > The E2E job is Erroring with "Archiving artifacts". The job itself does not fail, however the job log contains the following (artifacts are not archived): > Archiving artifacts > java.lang.InterruptedException: no matches found within 10000 > at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:2847) > at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2726) > at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2707) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3086) > Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.16.23.44/10.16.23.44:41046 > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11981) CLI not able to read backslash character correctly

by Saurabh Shriramwar (Jira)

[ https://issues.jboss.org/browse/WFLY-11981?page=com.atlassian.jira.plugin... ] Saurabh Shriramwar updated WFLY-11981: -------------------------------------- Steps to Reproduce: # Start CLI and execute /subsystem=mail/mail-session=default/server=smtp:write-attribute(name=username,value="auth\\SampleUser") # /subsystem=mail/mail-session=default/server=smtp:read-attribute(name=username) {code:java} { "outcome" => "success", "result" => "auth\\SampleUser" } {code} Whereas standalone.xml include the changes properly {code:java} <subsystem xmlns="urn:jboss:domain:mail:3.0"> <mail-session name="default" jndi-name="java:jboss/mail/Default"> <smtp-server outbound-socket-binding-ref="mail-smtp" username="auth\SampleUser"/> </mail-session> ........ {code} was: # Start CLI and execute /subsystem=mail/mail-session=default/server=smtp:write-attribute(name=username,value="auth\\SampleUser") # /subsystem=mail/mail-session=default/server=smtp:read-attribute(name=username) {code:java} { "outcome" => "success", "result" => "auth\\SampleUser" } {code} # Whereas standalone.xml include the changes properly {code:java} <subsystem xmlns="urn:jboss:domain:mail:3.0"> <mail-session name="default" jndi-name="java:jboss/mail/Default"> <smtp-server outbound-socket-binding-ref="mail-smtp" username="auth\SampleUser"/> </mail-session> ........ {code} > CLI not able to read backslash character correctly > -------------------------------------------------- > > Key: WFLY-11981 > URL: https://issues.jboss.org/browse/WFLY-11981 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: Saurabh Shriramwar > Priority: Minor > > The output for CLI read-attribute operation is confusing and not able to read/interpret backslash characters properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11981) CLI not able to read backslash character correctly

by Saurabh Shriramwar (Jira)

[ https://issues.jboss.org/browse/WFLY-11981?page=com.atlassian.jira.plugin... ] Saurabh Shriramwar updated WFLY-11981: -------------------------------------- Steps to Reproduce: # Start CLI and execute /subsystem=mail/mail-session=default/server=smtp:write-attribute(name=username,value="auth\\SampleUser") # /subsystem=mail/mail-session=default/server=smtp:read-attribute(name=username) {code:java} { "outcome" => "success", "result" => "auth\\SampleUser" } {code} # Whereas standalone.xml include the changes properly {code:java} <subsystem xmlns="urn:jboss:domain:mail:3.0"> <mail-session name="default" jndi-name="java:jboss/mail/Default"> <smtp-server outbound-socket-binding-ref="mail-smtp" username="auth\SampleUser"/> </mail-session> ........ {code} was: # Start CLI and execute /subsystem=mail/mail-session=default/server=smtp:write-attribute(name=username,value="auth\\SampleUser") # /subsystem=mail/mail-session=default/server=smtp:read-attribute(name=username) {code:java} { "outcome" => "success", "result" => "auth\\SampleUser" } {code} # Whereas standalone.xml include the changes properly {code:java} <subsystem xmlns="urn:jboss:domain:mail:3.0"> <mail-session name="default" jndi-name="java:jboss/mail/Default"> <smtp-server outbound-socket-binding-ref="mail-smtp" username="auth\SampleUser"/> </mail-session> ........ {code} > CLI not able to read backslash character correctly > -------------------------------------------------- > > Key: WFLY-11981 > URL: https://issues.jboss.org/browse/WFLY-11981 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: Saurabh Shriramwar > Priority: Minor > > The output for CLI read-attribute operation is confusing and not able to read/interpret backslash characters properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11981) CLI not able to read backslash character correctly

by Saurabh Shriramwar (Jira)

Saurabh Shriramwar created WFLY-11981: ----------------------------------------- Summary: CLI not able to read backslash character correctly Key: WFLY-11981 URL: https://issues.jboss.org/browse/WFLY-11981 Project: WildFly Issue Type: Bug Components: CLI Affects Versions: 14.0.0.Final Reporter: Saurabh Shriramwar The output for CLI read-attribute operation is confusing and not able to read/interpret backslash characters properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11981) CLI not able to read backslash character correctly

by Saurabh Shriramwar (Jira)

[ https://issues.jboss.org/browse/WFLY-11981?page=com.atlassian.jira.plugin... ] Saurabh Shriramwar updated WFLY-11981: -------------------------------------- Steps to Reproduce: # Start CLI and execute /subsystem=mail/mail-session=default/server=smtp:write-attribute(name=username,value="auth\\SampleUser") # /subsystem=mail/mail-session=default/server=smtp:read-attribute(name=username) {code:java} { "outcome" => "success", "result" => "auth\\SampleUser" } {code} # Whereas standalone.xml include the changes properly {code:java} <subsystem xmlns="urn:jboss:domain:mail:3.0"> <mail-session name="default" jndi-name="java:jboss/mail/Default"> <smtp-server outbound-socket-binding-ref="mail-smtp" username="auth\SampleUser"/> </mail-session> ........ {code} was: # Start CLI and execute /subsystem=mail/mail-session=default/server=smtp:write-attribute(name=username,value="auth\\SampleUser") # /subsystem=mail/mail-session=default/server=smtp:read-attribute(name=username) {code:java} { "outcome" => "success", "result" => "auth\\SampleUser" } {code} # Whereas standalone.xml include the changes properly {code:java} <subsystem xmlns="urn:jboss:domain:mail:3.0"> <mail-session name="default" jndi-name="java:jboss/mail/Default"> <smtp-server outbound-socket-binding-ref="mail-smtp" username="auth\SampleUser"/> </mail-session> ........ {code} > CLI not able to read backslash character correctly > -------------------------------------------------- > > Key: WFLY-11981 > URL: https://issues.jboss.org/browse/WFLY-11981 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: Saurabh Shriramwar > Priority: Minor > > The output for CLI read-attribute operation is confusing and not able to read/interpret backslash characters properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4061) ApplicationTypeConfigWriteAttributeHandler and SensitivityClassificationWriteAttributeHandler lack rollback handling

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFCORE-4061?page=com.atlassian.jira.plugi... ] Chao Wang reopened WFCORE-4061: ------------------------------- > ApplicationTypeConfigWriteAttributeHandler and SensitivityClassificationWriteAttributeHandler lack rollback handling > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4061 > URL: https://issues.jboss.org/browse/WFCORE-4061 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Chao Wang > Priority: Major > Fix For: 6.0.0.Beta1 > > > ApplicationTypeConfigWriteAttributeHandler and SensitivityClassificationWriteAttributeHandler update the runtime state of the relevant ApplicationTypeConfig or AbstractSensitivity without any logic to revert the change if the op rolls back, e.g. if they are run in a composite or as a domain mode op where rollout fails. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1851) Guided Decision table: Multiple 'otherwise' for sub-group support

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1851?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1851. ------------------------------- Resolution: Rejected [~tkobayashi] thank you for confirmation. > Guided Decision table: Multiple 'otherwise' for sub-group support > ----------------------------------------------------------------- > > Key: DROOLS-1851 > URL: https://issues.jboss.org/browse/DROOLS-1851 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Michael Anstis > Priority: Major > Attachments: otherwise.png, repository_export_otherwise.xml > > > If you set 'otherwise' for a cell, it equals to the rest of all defined values in the column. The request is accepting multiple 'otherwise' and it equals to the rest of all defined values in the sub-group. What is 'sub-group'? The intuitive approach is that Guvnor recognizes 'sub-group' from left to right. So if you have the same value cells (= so you can merge) in the left next column, it is the one sub-group for the 'otherwise'. It might be easier to understand with the image (See attached otherwise.png). > Words from a customer: > ===== > 1. I think the simplest approach to defining sub-groups will be to evaluate conditions from Left to right. So for the example I have provided Flight# will be the first sub-group, Airline the next sub-group. However if a different approach can be provided to create the sub-groups that would be acceptable as long as it is easy to create and visualize the sub-groups, specially for the Business Users. > 2. I think the sub-groups could be the default behavior. When multiple otherwise would be supported for a column an approach would be needed to understand the sub-group to which one otherwise applies, and the sub-group to which the 2nd otherwise applies within the same column. However from a backward compatibility perspective a toggle could be created (since currently otherwise can be on any row in the column). > ===== > I think the key part is if we can implement it without newly introduced meta-data. If you think we need to be more specific, please let me know. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11980) JBJCA-1388 - Validator is created using rar ClassLoader as the TCCL

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-11980?page=com.atlassian.jira.plugin... ] Lin Gao moved JBEAP-16723 to WFLY-11980: ---------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11980 (was: JBEAP-16723) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) Fix Version/s: (was: 7.2.2.GA) > JBJCA-1388 - Validator is created using rar ClassLoader as the TCCL > ------------------------------------------------------------------- > > Key: WFLY-11980 > URL: https://issues.jboss.org/browse/WFLY-11980 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11979) Move EL3 implementation to org.glassfish:jakarta-el 3.02

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11979: --------------------------------------- Summary: Move EL3 implementation to org.glassfish:jakarta-el 3.02 Key: WFLY-11979 URL: https://issues.jboss.org/browse/WFLY-11979 Project: WildFly Issue Type: Component Upgrade Components: EE Reporter: Brian Stansberry Assignee: Brian Stansberry The JBoss fork of javaee/uel-ri[1] has fallen behind the repo it was tracking (we've produced 3.0.1.b08 while the original is up to b11) and that repo in turn has been shutdown and work moved to eclipse[3], which has in turn produced a 3.0.2. The only thing our fork did was allow us to produce the impl jar independent of the API classes. We want that because we have actual code differences in our fork of the API classes. But I'll see if we can if I can use module.xml filters to accomplish the same effect. [1] https://github.com/jboss/uel/ [2] https://github.com/javaee/uel-ri [3] https://github.com/eclipse-ee4j/el-ri -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11978) EAR with 2+ JPA does not shutdown cleanly

by Darryl Miles (Jira)

Darryl Miles created WFLY-11978: ----------------------------------- Summary: EAR with 2+ JPA does not shutdown cleanly Key: WFLY-11978 URL: https://issues.jboss.org/browse/WFLY-11978 Project: WildFly Issue Type: Bug Affects Versions: 16.0.0.Final Environment: Windows JDK8 WF16 Reporter: Darryl Miles Assignee: Brian Stansberry EAR with 2+ JPA does not shutdown cleanly. I see in the logs each JPA project have an entry: WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project1' WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project2' then a few lines later: WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'blah....jpa.project2' I never see the "phase 1 of 2" entry for "jpa.project1" in the log. The container will wait 300 seconds and timeout. The management console during the time shows Operation: undeploy Execution Status: awaiting-stablility. The container is killed and the configuration.xml still contains the EAR deployment info, as undeploy did not complete. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 April 2019