March 2016 - jboss-jira - Jboss List Archives

[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)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6163) Remove org.apache.santuario.xmlsec dependency from org.jboss.as.webservices.server.integration module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6163?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6163: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1311733|https://bugzilla.redhat.com/show_bug.cgi?id=1311733] from MODIFIED to POST > Remove org.apache.santuario.xmlsec dependency from org.jboss.as.webservices.server.integration module > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-6163 > URL: https://issues.jboss.org/browse/WFLY-6163 > Project: WildFly > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 10.1.0.Final > > > We can remove org.apache.santuario.xmlsec dependency from org.jboss.as.webservices.server.integration module as Santuario is not needed directly from JBossWS (it's directly used by WSS4J and CXF though). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3483) Improve the ability to use MS Windows keystore for the web servers ssl connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3483?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3483: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1108310|https://bugzilla.redhat.com/show_bug.cgi?id=1108310] from MODIFIED to POST > Improve the ability to use MS Windows keystore for the web servers ssl connector > -------------------------------------------------------------------------------- > > Key: WFLY-3483 > URL: https://issues.jboss.org/browse/WFLY-3483 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.1.0.Final > > > It is possible to configure the web ssl connector to use the Windows certificate keystore (access provided by the SunMSCAPI provider). However, the JSSESocketFactory checks for a keystore file. This check should likely be skipped when the connector is configured to use the Windows keystore. > Here is what the configuration looks like: > {noformat} > <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true"> > <ssl name="https" > key-alias="jbossweb" > keystore-type="Windows-MY" > protocol="TLSv1" > </connector> > {noformat} > This results in an error like this: > 13:54:01,821 ERROR [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003043: Error initializing endpoint: java.io.FileNotFoundException: C:\Users\imauser\.keystore (The system cannot find the file specified) > You can work around this issue by creating this keystore (C:\Users\imauser\.keystore). > More info on using the Windows keystores can be found here: > http://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProvide... > http://www.oracle.com/technetwork/articles/javase/security-137537.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1360) CLI Options missed in WFCORE-1199

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1360?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1360: ------------------------------------------------- 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 Options missed in WFCORE-1199 > --------------------------------- > > Key: WFCORE-1360 > URL: https://issues.jboss.org/browse/WFCORE-1360 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 2.1.0.Final > > > The comma-seperated lists for server-groups in DeployHandler and UndeployHandler were missed in the original commit for WFCORE-1199. The --properties field for ASModuleHandler as also omitted by mistake. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5499) Channel end notification received, closing channel ... should be logged at debug in EjbLogger

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5499?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5499: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1271538|https://bugzilla.redhat.com/show_bug.cgi?id=1271538] from MODIFIED to POST > Channel end notification received, closing channel ... should be logged at debug in EjbLogger > --------------------------------------------------------------------------------------------- > > Key: WFLY-5499 > URL: https://issues.jboss.org/browse/WFLY-5499 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Takayuki Konishi > > Remote naming is logging this at ERROR, though it seems normal and no adverse effects are apparent, we should log it at debug instead of error. > {code} > ERROR [org.jboss.as.ejb3] (Remoting "master@ap02:server-apip" task-2) JBAS014141: Channel end notification received, closing channel Channel ID 6b8f00d7 (inbound) of Remoting connection 36e4f81b to /192.168.1.10:64354 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-903) Differently implemented password-stacking option in ClientLoginModule

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-903?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-903: -------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1254194|https://bugzilla.redhat.com/show_bug.cgi?id=1254194] from MODIFIED to POST > Differently implemented password-stacking option in ClientLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-903 > URL: https://issues.jboss.org/browse/SECURITY-903 > Project: PicketBox > Issue Type: Bug > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: PicketBox_5_0_0.Alpha2 > > > From BZ: > "In case when some login module should use password stacking then value of password-stacking option should be set to useFirstPass. All login modules should respect it. However implemetation of org.jboss.security.ClientLoginModule uses password-stacking differently - it uses password stacking everytime when some value is set for password-stacking option (even value false). It should work same as other login modules. Current behavior can be confusing and can lead to incorrectly set server configuration." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5478) allow custom scoped persistence unit name hint in persistence unit definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5478?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5478: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1262401|https://bugzilla.redhat.com/show_bug.cgi?id=1262401] from MODIFIED to POST > allow custom scoped persistence unit name hint in persistence unit definition > ----------------------------------------------------------------------------- > > Key: WFLY-5478 > URL: https://issues.jboss.org/browse/WFLY-5478 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.1.1.Final, 8.0.0.Final, 9.0.0.Final, 10.0.0.CR2 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR3 > > > Consider allowing applications to override the scoped persistence unit name, so instead of using names like "test2.ear/w2.war#warPUnit_PU", the application can specify a unique (across all deployments on the app server) name. > The idea is that application deployments can include a persistence unit hint "jboss.as.jpa.scopedname" that specifies the unique scoped persistence unit name that will be used for several internal settings (e.g. hibernate.cache.region_prefix will be set to the scopedname value unless the application specifies a different hibernate.cache.region_prefix value). > The WildFly management console does not yet work with applications that specify the jboss.as.jpa.scopedname. Once this change is merged to WildFly, a management console change should be requested. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-927) Option roleRecursion does not work in LdapRolesMappingProvider

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-927?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-927: -------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1269826|https://bugzilla.redhat.com/show_bug.cgi?id=1269826] from MODIFIED to POST > Option roleRecursion does not work in LdapRolesMappingProvider > -------------------------------------------------------------- > > Key: SECURITY-927 > URL: https://issues.jboss.org/browse/SECURITY-927 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: PicketBox_5_0_0.Alpha2 > Reporter: Ondrej Lukas > Assignee: Ryan Emerson > > Option roleRecursion does not work in org.jboss.security.mapping.providers.role.LdapRolesMappingProvider. Only entries without recursion are found. No recursive search is done by LdapRolesMappingProvider since LdapRolesMappingProvider.rolesSearch method tries to make a recursive search with same parameters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2016