February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2993) Core: jboss.sh fails to start with org.picketbox module not found

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2993?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-2993: ----------------------------------- adding the org.picketbox module to the distro fixes the issue (jboss-cli really needs it as CliConfigImpl imports org.jboss.security.vault.SecurityVaultException provided by picketbox) > Core: jboss.sh fails to start with org.picketbox module not found > ----------------------------------------------------------------- > > Key: WFLY-2993 > URL: https://issues.jboss.org/browse/WFLY-2993 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > Note that the issue occurs only when using the WildFly 8 *core distribution*, the regular distribution is fine. > {noformat} > wildfly-core-8.0.0.Final$ ./bin/jboss-cli.sh -c > org.jboss.modules.ModuleNotFoundException: org.picketbox:main > at org.jboss.modules.Module.addPaths(Module.java:1030) > at org.jboss.modules.Module.link(Module.java:1386) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1414) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) > at org.jboss.modules.Main.main(Main.java:385) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2993) Core: jboss.sh fails to start with org.picketbox module not found

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-2993: --------------------------------- Summary: Core: jboss.sh fails to start with org.picketbox module not found Key: WFLY-2993 URL: https://issues.jboss.org/browse/WFLY-2993 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: CLI Affects Versions: 8.0.0.Final Reporter: Jeff Mesnil Assignee: Alexey Loubyansky Fix For: 9.0.0.CR1 Note that the issue occurs only when using the WildFly 8 *core distribution*, the regular distribution is fine. {noformat} wildfly-core-8.0.0.Final$ ./bin/jboss-cli.sh -c org.jboss.modules.ModuleNotFoundException: org.picketbox:main at org.jboss.modules.Module.addPaths(Module.java:1030) at org.jboss.modules.Module.link(Module.java:1386) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1414) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) at org.jboss.modules.Main.main(Main.java:385) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2993) Core: jboss.sh fails to start with org.picketbox module not found

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2993?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-2993: --------------------------------- Assignee: Tomaz Cerar (was: Alexey Loubyansky) > Core: jboss.sh fails to start with org.picketbox module not found > ----------------------------------------------------------------- > > Key: WFLY-2993 > URL: https://issues.jboss.org/browse/WFLY-2993 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > Note that the issue occurs only when using the WildFly 8 *core distribution*, the regular distribution is fine. > {noformat} > wildfly-core-8.0.0.Final$ ./bin/jboss-cli.sh -c > org.jboss.modules.ModuleNotFoundException: org.picketbox:main > at org.jboss.modules.Module.addPaths(Module.java:1030) > at org.jboss.modules.Module.link(Module.java:1386) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1414) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) > at org.jboss.modules.Main.main(Main.java:385) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2992) HttpServerLogger.errorContextModuleNotFound() is skipped

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2992: -------------------------------------- Summary: HttpServerLogger.errorContextModuleNotFound() is skipped Key: WFLY-2992 URL: https://issues.jboss.org/browse/WFLY-2992 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 8.0.1.Final HttpServerLogger.errorContextModuleNotFound(String slot) was added but the code that should call it doesn't, it just calls logger.error(slot). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-822) MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-822?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-822: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1054972|https://bugzilla.redhat.com/show_bug.cgi?id=1054972] from POST to MODIFIED > MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL > --------------------------------------------------------------------------------------------------- > > Key: WFLY-822 > URL: https://issues.jboss.org/browse/WFLY-822 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading, Server > Environment: Java 6u31 > Reporter: Zachary Bedell > Assignee: jaikiran pai > Labels: classloader, mbean, modules > Fix For: 8.0.0.Alpha3 > > Attachments: SarTcclTst.tbz > > > When an MBean is loaded from jboss-service.xml within an EAR, the TCCL should point to the EAR deployment so that config files and other resources can be classloaded from the EAR. Under JBoss 7.1.1.Final, the TCCL in a module loaded MBean's start() method is the module's ClassLoader. No reference to the EAR deployment's classloader is available, thus EAR resources are not available within the MBean. > It appears that org.jboss.as.service.AbstractService::invokeLifecycleMethod() incorrectly sets the TCCL to the module's defining classloader rather than the EAR's: > {{{ > protected void invokeLifecycleMethod(final Method method) throws InvocationTargetException, IllegalAccessException { > if (method != null) { > final ClassLoader old = SecurityActions.setThreadContextClassLoader(mBeanInstance.getClass().getClassLoader()); > try { > method.invoke(mBeanInstance); > } finally { > SecurityActions.resetThreadContextClassLoader(old); > } > } > } > }}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-772) SPNEGOLoginModule does not always respect removeRealmFromPrincipal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-772?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-772: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1039955|https://bugzilla.redhat.com/show_bug.cgi?id=1039955] from ASSIGNED to MODIFIED > SPNEGOLoginModule does not always respect removeRealmFromPrincipal > ------------------------------------------------------------------ > > Key: SECURITY-772 > URL: https://issues.jboss.org/browse/SECURITY-772 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_6 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > Priority: Minor > Fix For: Negotiation_2_2_7 > > > org.jboss.security.negotiation.spnego.SPNEGOLoginModule > private class AcceptSecContext: > if (gssContext.isEstablished()) > { > log.warn("Authentication was performed despite already being authenticated!"); > // TODO - Refactor to only do this once. > setIdentity(new KerberosPrincipal(gssContext.getSrcName().toString())); > The last line should obey the "removeRealmFromPrincipal" flag similarly as a bit further down: > setIdentity(createIdentity(gssContext.getSrcName().toString())); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1039955|https://bugzilla.redhat.com/show_bug.cgi?id=1039955] from ASSIGNED to MODIFIED > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBEE-147) QueryTagSupport does not close prepared statements and result sets correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBEE-147?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBEE-147: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1065854|https://bugzilla.redhat.com/show_bug.cgi?id=1065854] from NEW to MODIFIED > QueryTagSupport does not close prepared statements and result sets correctly > ---------------------------------------------------------------------------- > > Key: JBEE-147 > URL: https://issues.jboss.org/browse/JBEE-147 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jstl-api > Reporter: James Livingston > Assignee: Shelly McGowan > Fix For: jboss-jstl-api_1.2_spec-1.0.5.Final, jboss-jstl-api_1.2_spec-1.1.0.Final > > > The JSTL spec artifact contain implementation code forked from the Apache taglib project. > One bug fixed upstreak since the fork is https://issues.apache.org/bugzilla/show_bug.cgi?id=17388, which can cause prepared statement and/or result set objects not to be closed correctly. > The fix can be cherry-picked from (http://svn.apache.org/viewvc/jakarta/taglibs/proper/standard/trunk/src/or...), unless there was a plan to rebase on the recently released upstream 1.2.1 which includes the fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-822) MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-822?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-822: ---------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1054984|https://bugzilla.redhat.com/show_bug.cgi?id=1054984] from POST to MODIFIED > MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL > --------------------------------------------------------------------------------------------------- > > Key: WFLY-822 > URL: https://issues.jboss.org/browse/WFLY-822 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading, Server > Environment: Java 6u31 > Reporter: Zachary Bedell > Assignee: jaikiran pai > Labels: classloader, mbean, modules > Fix For: 8.0.0.Alpha3 > > Attachments: SarTcclTst.tbz > > > When an MBean is loaded from jboss-service.xml within an EAR, the TCCL should point to the EAR deployment so that config files and other resources can be classloaded from the EAR. Under JBoss 7.1.1.Final, the TCCL in a module loaded MBean's start() method is the module's ClassLoader. No reference to the EAR deployment's classloader is available, thus EAR resources are not available within the MBean. > It appears that org.jboss.as.service.AbstractService::invokeLifecycleMethod() incorrectly sets the TCCL to the module's defining classloader rather than the EAR's: > {{{ > protected void invokeLifecycleMethod(final Method method) throws InvocationTargetException, IllegalAccessException { > if (method != null) { > final ClassLoader old = SecurityActions.setThreadContextClassLoader(mBeanInstance.getClass().getClassLoader()); > try { > method.invoke(mBeanInstance); > } finally { > SecurityActions.resetThreadContextClassLoader(old); > } > } > } > }}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1065513|https://bugzilla.redhat.com/show_bug.cgi?id=1065513] from ASSIGNED to MODIFIED > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 February 2014