March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-263) Cancelling management op on slave HC tree is broken

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-263?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-263: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1202610|https://bugzilla.redhat.com/show_bug.cgi?id=1202610] from NEW to CLOSED > Cancelling management op on slave HC tree is broken > --------------------------------------------------- > > Key: WFCORE-263 > URL: https://issues.jboss.org/browse/WFCORE-263 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 1.0.0.Alpha9 > Reporter: James Livingston > Assignee: Brian Stansberry > Priority: Major > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > Attachments: unundeployable.zip > > > If you have a DC with a slave HC, and perform a management operation which gets stuck, non-progressing operations will be reported for both the DC and the slave HC via: > /host=master/core-service=management/service=management-operations:find-non-progressing-operation > /host=slave/core-service=management/service=management-operations:find-non-progressing-operation > Cancelling the operation under /host=master works as expected, pushing the cancellation down to the slave and the controllers become responsive again. > If however you attempt to cancel the operation under /host=slave, it goes bad. { "outcome" => "success", "result" => undefined } is reported in the CLI, but the controllers are still unresponsive. > Running :find-non-progressing-operation against the slave will report the {outcome=success,result=undefined} rather than that no non-progressing operations were found, and active-operation=*:read-resource() shows it as not cancelled. > Once you attempt to cancel it on a slave, attempting to cancel it under /host=master will report success, but leave the slave op in a weird state, and things requiring the controller lock (such as the web UI) will still not respond. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-489) The "access-mechanism" field in the active-operation resources is always undefined

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-489?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-489: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1202610|https://bugzilla.redhat.com/show_bug.cgi?id=1202610] from NEW to CLOSED > The "access-mechanism" field in the active-operation resources is always undefined > ---------------------------------------------------------------------------------- > > Key: WFCORE-489 > URL: https://issues.jboss.org/browse/WFCORE-489 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 1.0.0.Beta4 > > > The "access-mechanism" field in core-service=management/service=active-operations/active-operation=* is always undefined. The code that sets it is using the wrong var: > {code} > ModelNode accessMechanismNode = model.get(ACCESS_MECHANISM); > if (accessMechanism != null) { > accessMechanismNode.set(accessMechanismNode.toString()); > } > {code} > It should be accessMechanism.toString() -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-67) method-params containing an array not correctly processed for EJB2.1 with CMT

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-67?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-67: --------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1180571|https://bugzilla.redhat.com/show_bug.cgi?id=1180571] from NEW to CLOSED > method-params containing an array not correctly processed for EJB2.1 with CMT > ----------------------------------------------------------------------------- > > Key: WFLY-67 > URL: https://issues.jboss.org/browse/WFLY-67 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: JBoss 7.2.0-Final Prerelease (Commit 4ed76c) and JBoss 7.1.3.Final on Win7/64 JDK 1.7.0_09 > Reporter: Robert Panzer > Assignee: Ondrej Zizka > Priority: Major > Fix For: 8.0.0.Alpha1 > > Attachments: cmt-never-array-params.zip > > > It seems that the method-params for container transactions are not matched correctly if the contain arrays. > I've got an EJB "First" that calls another EJB "Second". Both have the same interface containing a method void test(String[]); > If I define the transaction attribute NEVER including method-params for "First" and without params for "Second" the test fails with > JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6) > I define the container transaction like this: > <container-transaction> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>java.lang.String[]</method-param> > </method-params> > </method> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>java.lang.String</method-param> > </method-params> > </method> > <method> > <ejb-name>FirstWithParams</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > <method-params> > <method-param>int</method-param> > </method-params> > </method> > <method> > <ejb-name>Second</ejb-name> > <method-intf>Local</method-intf> > <method-name>test</method-name> > </method> > <trans-attribute>Never</trans-attribute> > </container-transaction> > I will attach a test case that fails at the call to test(String[]) but successfully call test(String) and test(int). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-284) Rewrite CLI FileArgumentTestCase

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-284?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-284: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 900632|https://bugzilla.redhat.com/show_bug.cgi?id=900632] from NEW to CLOSED > Rewrite CLI FileArgumentTestCase > -------------------------------- > > Key: WFCORE-284 > URL: https://issues.jboss.org/browse/WFCORE-284 > Project: WildFly Core > Issue Type: Task > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > > The test has been failing sporadically for awhile. One of the problems is to figure out the conditions under which the test fails. They haven't been determined so far. Perhaps, attempts to simplify and clean up the logic in the test will help. > The test is org.jboss.as.test.integration.management.cli.FileArgumentTestCase -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-486?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-486: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1173615|https://bugzilla.redhat.com/show_bug.cgi?id=1173615] from NEW to CLOSED > cli echo command should not output the result in columns > -------------------------------------------------------- > > Key: WFCORE-486 > URL: https://issues.jboss.org/browse/WFCORE-486 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > Fix For: 1.0.0.Alpha15 > > > Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-437) Add config option to fail deployment if private API is used

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-437?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-437: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1018260|https://bugzilla.redhat.com/show_bug.cgi?id=1018260] from NEW to CLOSED > Add config option to fail deployment if private API is used > ----------------------------------------------------------- > > Key: WFCORE-437 > URL: https://issues.jboss.org/browse/WFCORE-437 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Pete Muir > Priority: Major > > This would allow users to have continuous integration jobs check if their app uses a private API by mistake, and have the job fail if it does. > Needed to automate the check that quickstarts only use public API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4235) JDR capture OS version

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-4235?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4235: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1195516|https://bugzilla.redhat.com/show_bug.cgi?id=1195516] from NEW to CLOSED > JDR capture OS version > ---------------------- > > Key: WFLY-4235 > URL: https://issues.jboss.org/browse/WFLY-4235 > Project: WildFly > Issue Type: Feature Request > Components: JDR > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Major > > JDR should capture OS version if available -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1073) Replicating JNDI tree to another server

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-1073?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1073: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 913618|https://bugzilla.redhat.com/show_bug.cgi?id=913618] from NEW to CLOSED > Replicating JNDI tree to another server > ---------------------------------------- > > Key: WFLY-1073 > URL: https://issues.jboss.org/browse/WFLY-1073 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Miroslav Novak > Priority: Major > > Description of problem: > This use case is taken from one of our user which we were able to handle using HA-JNDI in EAP 5: > 1. JMS Client will create Context with two URL (node1, node2) (java.naming.provider.url property) > 2. For some reason client is connected to node2 first which will have no JMS admin objects registered in JNDI (this happens when this node is configured as HornetQ backup) > 3. Node2 has replicated JNDI tree from node1. So connection factory will connect client to node1 and queue/topics are deployed on node1. > Can be this functionality provided in EAP 6, please? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4239) WARN if system-property is already set and is being overridden

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-4239?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-4239: ------------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1654454|https://bugzilla.redhat.com/show_bug.cgi?id=1654454] from NEW to ASSIGNED > WARN if system-property is already set and is being overridden > -------------------------------------------------------------- > > Key: WFCORE-4239 > URL: https://issues.jboss.org/browse/WFCORE-4239 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brad Maxwell > Assignee: Chao Wang > Priority: Major > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > WARN if system-property is already set and is being overridden > If user sets a system property using the java opts or on the command line and the same system property is defined in the standalone.xml, then the standalone.xml value overrides that passed on the commandline/JAVA_OPTS, a warning would be useful as looking at the logs (and ps), it shows value1 passed on the command line and nothing indicating that the value was changed later. > JAVA_OPTS="$JAVA_OPTS -Dmy.system.property=value1" > {code} > <system-properties> > <property name="my.system.property" value="value2"/> > </system-properties> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3659: ---------------------------------------- Thanks [~tdolphine] I missed the "Print" button! :-) > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3659-documentation.mp4 > > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019