March 2016 - jboss-jira - Jboss List Archives

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

9 years, 9 months

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)

9 years, 9 months

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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4441) JPA hibernate.cache.region_prefix property fails JConsole to connect to JBoss

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4441?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4441: ---------------------------------------------- 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 > JPA hibernate.cache.region_prefix property fails JConsole to connect to JBoss > ----------------------------------------------------------------------------- > > Key: AS7-4441 > URL: https://issues.jboss.org/browse/AS7-4441 > Project: Application Server 7 > Issue Type: Bug > Components: JMX, JPA / Hibernate, Server > Affects Versions: 7.1.1.Final > Environment: Windows Vista 64 bit, JDK 1.6.0_18 > Reporter: Osten Forshed > Assignee: Scott Marlow > Priority: Minor > Fix For: 7.1.2.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > > > If a web app is deployed (standalone) with a persistence.xml containing: > <property name="hibernate.cache.region_prefix" value=""/> > Then it is not possible to connect to the MBean Server with JConsole using instructions here: > https://community.jboss.org/wiki/UsingJconsoleToConnectToJMXOnAS7 > Following stack trace is written to JBoss log: > 12:27:03,406 WARN [org.jboss.remotingjmx.protocol.v1.ServerProxy] (pool-5-thread-16) Unexpected internal error: java.lang.NullPointerException > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39) > at org.jboss.as.jmx.model.ModelControllerMBeanHelper.queryNames(ModelControllerMBeanHelper.java:136) > at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.queryNames(ModelControllerMBeanServerPlugin.java:124) > at org.jboss.as.jmx.PluggableMBeanServerImpl.queryNames(PluggableMBeanServerImpl.java:280) > at org.jboss.remotingjmx.protocol.v1.ServerProxy$QueryNamesHandler.handle(ServerProxy.java:1197) > at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_18] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_18] > at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_18] > If property is removed from persistence.xml it is possible to connect using JConsole and browse the MBeans. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3849) logging improvement to WFLYSEC0015 (vault security exception)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3849?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3849: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1073603|https://bugzilla.redhat.com/show_bug.cgi?id=1073603] from MODIFIED to POST > logging improvement to WFLYSEC0015 (vault security exception) > ------------------------------------------------------------- > > Key: WFLY-3849 > URL: https://issues.jboss.org/browse/WFLY-3849 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 9.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > Description of problem (taken from bz1073603): > Include which vault property resolution has failed in following error message: > java.lang.SecurityException: JBAS013311: Security Exception > at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:104) > For example, this would be helpful: > java.lang.SecurityException: JBAS013311: Security Exception (Error resolving vault property: ${VAULT:example:example:1} > How reproducible: > Using a vault property that doesn't exist will give this error message. > Steps to Reproduce: > 1. setup vault as normal > 2. use a vault property that doesn't exist > Actual results: > Get: > java.lang.SecurityException: JBAS013311: Security Exception > at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:104) > Expected results: > log message that show the property that failed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-761) Not possible to overlay non existing file in WAR

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-761?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-761: ------------------------------------------------ Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1287732|https://bugzilla.redhat.com/show_bug.cgi?id=1287732] from MODIFIED to POST > Not possible to overlay non existing file in WAR > ------------------------------------------------ > > Key: WFCORE-761 > URL: https://issues.jboss.org/browse/WFCORE-761 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Bartosz Baranowski > Assignee: Dimitris Andreadis > Priority: Critical > > It is either bug in how deployments are treated or how overlay/vfs work. > Steps to reproduce: > 1. deploy undexploded war with jar inside > 2. add overlay that will add non existing file in jar > Result: exception: > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt > Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}} > at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67) > at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37) > at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76) > at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67) > Expectation: > should work. It actually does work, if war is really exploded or > 'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6294) Session draining always takes maximum configured timeout

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6294?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6294: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1314792|https://bugzilla.redhat.com/show_bug.cgi?id=1314792] from MODIFIED to POST > Session draining always takes maximum configured timeout > -------------------------------------------------------- > > Key: WFLY-6294 > URL: https://issues.jboss.org/browse/WFLY-6294 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Aaron Ogburn > Assignee: Radoslav Husar > Priority: Minor > > The mod_cluster session drain wait is not ending as expected. mod_cluster adds a session listener to be notified of session destruction. That is fired appropriately, but when the listener is invoked, the infinispan session manager still reports the session as active. Thus, this drain loop doesn't end after the notify because it still sees the active session: > {code} > while ((remainingSessions > 0) && (noTimeout || (timeout > 0))) { > ModClusterLogger.LOGGER.drainSessions(remainingSessions, context.getHost(), context); > listener.wait(noTimeout ? 0 : timeout); > current = System.currentTimeMillis(); > timeout = end - current; > remainingSessions = context.getActiveSessionCount(); > } > {code} > Can the listeners be invoked when the session is fully removed and no longer considered active? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3809) JDR incorrectly sets JBOSS_HOME path name in the jar file on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3809?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3809: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 917683|https://bugzilla.redhat.com/show_bug.cgi?id=917683] from MODIFIED to POST > JDR incorrectly sets JBOSS_HOME path name in the jar file on Windows > -------------------------------------------------------------------- > > Key: WFLY-3809 > URL: https://issues.jboss.org/browse/WFLY-3809 > Project: WildFly > Issue Type: Bug > Components: JDR > Environment: All modes on Windows > Reporter: Jesse Jaggars > Assignee: Jesse Jaggars > > JDR replaces $JBOSS_HOME with the text `JBOSS_HOME` in the generated zipfile. On windows the path is improperly constructed. For example if JBOSS_HOME=/foo/bar/baz, when the file /foo/bar/baz/example.txt is copied into the JDR archive the path will be: > JBOSS_HOMEz/example.txt > It should be: > JBOSS_HOME/example.txt -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-161) BeanELResolver does not support methods that use varargs

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBEE-161?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBEE-161: ---------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1292891|https://bugzilla.redhat.com/show_bug.cgi?id=1292891] from MODIFIED to POST > BeanELResolver does not support methods that use varargs > -------------------------------------------------------- > > Key: JBEE-161 > URL: https://issues.jboss.org/browse/JBEE-161 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-el-api > Environment: jboss-el-api_2.2_spec-1.0.4.Final-redhat-1 > Reporter: Ingo Weiss > Assignee: Scott Marlow > Labels: el > Fix For: jboss-el-api_3.0_spec-1.0.6.Final > > Attachments: beanELResolver4VarArgs.zip > > > When passing BeanELResolver a method that uses varargs, BeanELResolver throws the following exception: > {code} > java.lang.IllegalArgumentException: wrong number of arguments > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at javax.el.BeanELResolver.invokeMethod(BeanELResolver.java:834) > at javax.el.BeanELResolver.invoke(BeanELResolver.java:527) > at org.apache.el.parser.AstValue.getValue(AstValue.java:156) > at BeanELResolverTest.readExpressionValue(BeanELResolverTest.java:32) > at BeanELResolverTest.testMethodWithFixArgumentList(BeanELResolverTest.java:21) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4133: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1147948|https://bugzilla.redhat.com/show_bug.cgi?id=1147948] from MODIFIED to POST > Hanging EJB threads because of a persistent timer and failed deployment > ------------------------------------------------------------------------ > > Key: WFLY-4133 > URL: https://issues.jboss.org/browse/WFLY-4133 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 9.0.0.Beta1 > > > When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

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 March 2016