[JBoss JIRA] (WFLY-3578) jboss-cli.bat always exits with return code 0 even after a cli failure
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3578?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3578:
-----------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1223877|https://bugzilla.redhat.com/show_bug.cgi?id=1223877] from POST to MODIFIED
> jboss-cli.bat always exits with return code 0 even after a cli failure
> ----------------------------------------------------------------------
>
> Key: WFLY-3578
> URL: https://issues.jboss.org/browse/WFLY-3578
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.1.0.Final
> Environment: Windows
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 9.0.0.Alpha1
>
>
> jboss-cli.bat cannot be reliably controlled by other scripts because it does not report return code from cli execution and always exits with 0 even after a failure.
> It can be solved with the following patch:
> {noformat}
> --- C:/home/JBoss/wildfly-8.1.0.Final/bin/jboss-cli-orig.bat Sat May 31 04:54:25 2014
> +++ C:/home/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.bat Thu Jul 03 10:19:09 2014
> @@ -1,4 +1,5 @@
> @echo off
> +setlocal ENABLEEXTENSIONS
> rem -------------------------------------------------------------------------
> rem JBoss Admin CLI Script for Windows
> rem -------------------------------------------------------------------------
> @@ -48,6 +49,7 @@
> if not exist "%JBOSS_RUNJAR%" (
> echo Could not locate "%JBOSS_RUNJAR%".
> echo Please check that you are in the bin directory when running this script.
> + set /A RC=1
> goto END
> )
>
> @@ -71,5 +73,11 @@
> org.jboss.as.cli ^
> %*
>
> +set /A RC=%errorlevel%
> :END
> if "x%NOPAUSE%" == "x" pause
> +
> +if "x%RC%" == "x" (
> + set /A RC=0
> +)
> +exit /B %RC%
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years
[JBoss JIRA] (WFCORE-102) Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-102?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-102:
------------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1299102|https://bugzilla.redhat.com/show_bug.cgi?id=1299102] from POST to MODIFIED
> Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-102
> URL: https://issues.jboss.org/browse/WFCORE-102
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha9
>
>
> The various base classes OSH authors use to create handlers force the author to deal with ServiceVerificationHandler and, during rollback, with removing any services the OSH added. This task is to have the OperationContext handle these things transparently, removing the need for authors to do so.
> To preserve compatibility, the various API methods authors may have overridden that expose the SVH and the list of added ServiceControllers will be retained (but deprecated), but the SVH and the list of handlers won't be used. The API javadoc will encourage use of method variants that don't use these parameters.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years
[JBoss JIRA] (ELY-703) Introduce LegacyConfiguration SPI in client auth package
by David Lloyd (JIRA)
David Lloyd created ELY-703:
-------------------------------
Summary: Introduce LegacyConfiguration SPI in client auth package
Key: ELY-703
URL: https://issues.jboss.org/browse/ELY-703
Project: WildFly Elytron
Issue Type: Task
Components: Authentication Client
Reporter: David Lloyd
If no client-configuration section is found for Elytron's client configuration, there should be a fallback SPI using java.util.ServiceLoader to allow the legacy EJB client to inject a client configuration. The service interface should yield an AuthenticationContext.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years
[JBoss JIRA] (WFCORE-1915) ParseUtils.parseAttributeValue should not fail due to DMR type conversions
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1915:
----------------------------------------
Summary: ParseUtils.parseAttributeValue should not fail due to DMR type conversions
Key: WFCORE-1915
URL: https://issues.jboss.org/browse/WFCORE-1915
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha11
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 3.0.0.Alpha12
The task of ParseUtils.parseAttributeValue is to convert a string into a ModelNode. The type of the ModelNode is not particularly important, as later code will do type conversion. And, it is *not* the job of this method to do validation; there is other code that does that. So, the type conversion this method does should not be allowed to produce failures. Continuing to try the conversion is ok, although not required, but if a conversion can't succeed the pre-conversion ModelType.STRING node should be returned.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years
[JBoss JIRA] (WFCORE-1198) CLI does not resolve multiple properties if one property is undefined
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1198?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-1198:
-------------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1289316|https://bugzilla.redhat.com/show_bug.cgi?id=1289316] from POST to MODIFIED
> CLI does not resolve multiple properties if one property is undefined
> ---------------------------------------------------------------------
>
> Key: WFCORE-1198
> URL: https://issues.jboss.org/browse/WFCORE-1198
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.4.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Fix For: 2.0.5.Final
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1289316 description:
> {noformat}
> Multiple property substitution is working with EAP 6.4.3+, however, if a variable amongst the multiple variables is empty or has no value, then the subsequent property in the CLI command is not substituted.
> For example :
> cat props.properties
> -----------------------------------------
> PROFILE-NAME=TestProfile
> SERVER-INSTANCE-NUMBER=TestInstance
> APP-VERSION=
> VAR=test
> -----------------------------------------
> cat test.cli :
> ---------------------------------------
> /host=master/server-config=${PROFILE-NAME}${APP-VERSION}${SERVER-INSTANCE-NUMBER}${VAR}:add(auto-start=true, group="${PROFILE-NAME}${APP-VERSION}-server-group")
> ---------------------------------------
> and if I execute "./jboss-cli.sh --connect --file=test.cli --properties=props.properties" then I have the following in the host.xml ":
> ----------
> ...
> <server name="TestProfile${SERVER-INSTANCE-NUMBER}test" group="TestProfile-server-group" auto-start="true"/>
> ...
> -----------
> Note APP-VERSION had no value, and so the subsequent SERVER-INSTANCE-NUMBER was not properly resolved
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years
[JBoss JIRA] (WFLY-7418) Batch deployments with a large number of executed jobs can lock up or slow down the web console
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-7418?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-7418:
-------------------------------------
Excellent, thanks! The web workers approach does look interesting. I assume an approach like that would benefit from having some kind of description on the resource indicating it may be a slow runtime resource.
> Batch deployments with a large number of executed jobs can lock up or slow down the web console
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-7418
> URL: https://issues.jboss.org/browse/WFLY-7418
> Project: WildFly
> Issue Type: Enhancement
> Components: Batch, Web Console
> Reporter: James Perkins
> Assignee: James Perkins
>
> Batch deployments which contain a large number of executed jobs can be extremely slow to process as the {{/deployment=batch.war/subsystem=batch-jberet}} processes each job instance then each job execution of that job instance.
> One possibly helpful option for the web console would be to add a new description attribute to indicate the resource may be slow to process. The web console might be able to run a background task to populate data rather than locking up the UI. There would still be an issue with a large memory footprint here however.
> JBeret might want to consider having a way to archive jobs too rather than just purge them. Some users may want to keep all job execution data. Archiving this data could reduce the size of the current data being retrieved.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years