[JBoss JIRA] (WFLY-4533) Port jboss-as-messaging_1_5.xsd from EAP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4533?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4533:
-----------------------------------------------
Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1212941|https://bugzilla.redhat.com/show_bug.cgi?id=1212941] from MODIFIED to POST
> Port jboss-as-messaging_1_5.xsd from EAP
> ----------------------------------------
>
> Key: WFLY-4533
> URL: https://issues.jboss.org/browse/WFLY-4533
> Project: WildFly
> Issue Type: Sub-task
> Components: JMS
> Reporter: Darran Lofthouse
> Assignee: Jeff Mesnil
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
>
> Unfortunately an incompatible change has been introduced in jboss-as-messaging_1_4.xsd within EAP, this Jira issue is to minimise the impact.
> EAP should have a new jboss-as-messaging_1_5.xsd added and the changes to the 1.4 schema reverted. The parser will be updated to support 1.5 and will remain quietly accepting the new element.
> In WildFly we need to forward port this new 1.5 schema and also update the 1.4 parser to quietly accept the new element.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-1121:
-------------------------------------------------
Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1265740|https://bugzilla.redhat.com/show_bug.cgi?id=1265740] from MODIFIED to POST
> Use script name for file related to Wildfly to allow multiple instances easily
> ------------------------------------------------------------------------------
>
> Key: WFCORE-1121
> URL: https://issues.jboss.org/browse/WFCORE-1121
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 2.0.1.Final
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Optional
> Fix For: 3.0.0.Alpha1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances:
> {code:bash}
> # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1
> # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2
> {code}
> And to take the example of the PIDFILE:
> {code:bash}
> JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid
> {code}
> Each links will then look up and creates its own separate file:
> /var/run/wildfly-1/jboss-as-domain.pid
> /var/run/wildfly-2/jboss-as-domain.pid
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-591) revertReloadRequired() throws a NPE is reloadRequired has not been called
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-591?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-591:
------------------------------------------------
Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1294591|https://bugzilla.redhat.com/show_bug.cgi?id=1294591] from MODIFIED to POST
> revertReloadRequired() throws a NPE is reloadRequired has not been called
> -------------------------------------------------------------------------
>
> Key: WFCORE-591
> URL: https://issues.jboss.org/browse/WFCORE-591
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha19
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 1.0.0.Beta1
>
>
> If an operation step handler calls org.jboss.as.controller.OperationContext#revertReloadRequired() when org.jboss.as.controller.OperationContext#reloadRequired() has not been called, it throws a NPE:
> {noformat}
> java.lang.NullPointerException
> at org.jboss.as.controller.ControlledProcessState.revertReloadRequired(ControlledProcessState.java:181)
> at org.jboss.as.controller.AbstractOperationContext.revertReloadRequired(AbstractOperationContext.java:1037)
> at org.jboss.as.controller.test.RevertReloadRequiredTestCase$TestResourceAddHandler.rollbackRuntime(RevertReloadRequiredTestCase.java:98)
> at org.jboss.as.controller.AbstractAddStepHandler$1$1.handleRollback(AbstractAddStepHandler.java:133)
> at org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1419)
> at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1385)
> at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1367)
> at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1323)
> at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1283)
> at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1172)
> at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:929)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:877)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1182)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:205)
> {noformat}
> The NPE is caused by this.activeStep.restartStamp field which is set only when reloadRequired() (or restartRequired()) is called.
> My OSH may call reloadRequired() or not depending on some runtime state and I could add some logic to make sure I call
> I can fix my handle to check that I call context.revertReloadRequired() only I had previously called reloadRequired () first.
> However, in order to make the OperationContext more robust, I think that the revertReloadRequired() method should instead be a no-op if there is no reload required.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1199) CLI Lists in non-interactive mode are erroneously split into multiple commands
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1199?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-1199:
-------------------------------------------------
Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1284885|https://bugzilla.redhat.com/show_bug.cgi?id=1284885] from MODIFIED to POST
> CLI Lists in non-interactive mode are erroneously split into multiple commands
> ------------------------------------------------------------------------------
>
> Key: WFCORE-1199
> URL: https://issues.jboss.org/browse/WFCORE-1199
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Modules, Patching
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 2.0.8.Final
>
>
> The problem arises because commands entered in non-interactive mode are split by the "," character. Therefore, in the case of:
> "./bin/jboss-cli.sh -c --controller=localhost --commands="module add --name=test --resources=test.jar --dependencies=dep1,dep2"
> the cli is incorrectly splitting the request into two distinct commands:
> 1. module add --name=test --resources=test.jar --dependencies=dep1
> 2. dep2
> The reason this behaviour is not observed in interactive mode is because multiple commands can not be specified. However, in non-interactive mode --commands=ls,pwd is valid and should result in the execution of ls followed by pwd.
> This problem is not restricted to the module command, as it affects all commands entered in non-interactive mode that require a comma-separated list as an argument. So far this appears to be PatchHanlder.java, ASModuleHandler.java and DeploymentOverlayHandler.java.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months