November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6015) Session bean target class around-invoke method called before CDI interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger commented on AS7-6015: -------------------------------------- Added testcase org.jboss.as.test.integration.weld.interceptor.ordering.SessionBeanInterceptorOrderingTest https://github.com/jbossas/jboss-as/pull/3488 https://github.com/jbossas/jboss-as/pull/3489 > Session bean target class around-invoke method called before CDI interceptors > ----------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6015) Session bean target class around-invoke method called before CDI interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger updated AS7-6015: --------------------------------- Summary: Session bean target class around-invoke method called before CDI interceptors (was: Around-invoke method of the target class should be called after all other interceptors) > Session bean target class around-invoke method called before CDI interceptors > ----------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6015) Around-invoke method of the target class should be called after all other interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger moved WELD-1244 to AS7-6015: -------------------------------------------- Project: Application Server 7 (was: Weld) Key: AS7-6015 (was: WELD-1244) Issue Type: Bug (was: Task) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.3.Final (EAP) (was: 2.0.0.Alpha3) Component/s: CDI / Weld EJB (was: Interceptors and Decorators) Fix Version/s: 7.2.0.Alpha1 (was: 2.0.0.Beta1) > Around-invoke method of the target class should be called after all other interceptors > -------------------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5652) POJO subsytem isn't setting the TCCL to the application's class loader

by Michael Vetter (JIRA)

Michael Vetter created AS7-5652: ----------------------------------- Summary: POJO subsytem isn't setting the TCCL to the application's class loader Key: AS7-5652 URL: https://issues.jboss.org/browse/AS7-5652 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.2.0.Alpha1 Reporter: Michael Vetter Assignee: Ales Justin The POJO subsytem isn't setting the TCCL (Thread.currentThread().getContextClassLoader()) to the application's class loader while invoking on the application's lifecycle methods. The TCCL is set to the "ModuleClassLoader for Module "org.jboss.as.pojo:main" from local module loader". It was working in JBoss5.1 to start a bean with an xml file (<deployment xmlns="urn:jboss:bean-deployer:2.0"> ...) and to use the TCCL during deployment to load resources and classes from the ear. With the pojo ModuleClassLoader these resources are not found. -- 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

13 years, 5 months

5
6
0 / 0

[JBoss JIRA] (AS7-6009) JBAS018040: Failed to start context

by B K (JIRA)

B K created AS7-6009: ------------------------ Summary: JBAS018040: Failed to start context Key: AS7-6009 URL: https://issues.jboss.org/browse/AS7-6009 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Environment: Redhat Linux 4 (??). Kernel version is: 2.6.18-194.26.1.el5 Reporter: B K Assignee: Heiko Braun The error found in the server log files was: 13:58:40,009 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./apex: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./apex: JBAS018040: Failed to start context Occurence details: 1. The issue occured following a restart of the application server Analysis details: 1. From the perspective of the JBOSS 7 admin console ... the admin console shows that the "apex.war" application is deployed and "enabled". I believe it should not display "enabled" as the context has failed to start and it is only capable of servicing requests. Details to reproduce: 1. Download Oracle Apex Listener 1.1.4 from: http://www.oracle.com/technetwork/developer-tools/apex-listener/downloads... 2. Unzip the war file e.g jar xvf apex.war 3. Modify the web.xml by adding: <context-param> <param-name>config.dir</param-name> <param-value>/opt/jboss/apex_config_dir</param-value> </context-param> 4. Create the path "/opt/jboss/apex_config_dir". 5. Zip the war file. cd locationContaining the Web-INF directory jar cvf apex.war * 6. Deploy war file and enable via admin console. Stop Server. Start server. 7. Exception occurs. NOTE: there could be an additional step to reproduce. Will detail if above does not work. NOTE2: I can redeploy the above application and get it working again by removing some files that are auto generated by apex.war (so a partial bit of this issue is probably application related). -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] (SECURITY-638) The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or

by Tom Fonteyne (Created) (JIRA)

The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-638 URL: https://issues.jboss.org/browse/SECURITY-638 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: JBossSecurity_2.0.4.SP9 Reporter: Tom Fonteyne Assignee: Anil Saldhana Priority: Minor Fix For: JBossSecurity_2.0.4.SP9 porting https://issues.jboss.org/browse/JBPAPP-7794 to PicketBox -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

7
8
0 / 0

[JBoss JIRA] (SECURITY-661) CertRolesLoginModule does not substitute variables in paths to property files

by Martin Gencur (JIRA)

Martin Gencur created SECURITY-661: -------------------------------------- Summary: CertRolesLoginModule does not substitute variables in paths to property files Key: SECURITY-661 URL: https://issues.jboss.org/browse/SECURITY-661 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v4_0_9.Final Reporter: Martin Gencur Assignee: Anil Saldhana Fix For: PicketBox_4_0_10.Final When I use CertificateRoles module in AS7 configuration and specify a path to roles.properties like this: <module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/> ,the server throws the following error: {code} ERROR [org.jboss.security.auth.spi.CertRolesLoginModule] (http-/127.0.0.1:8443-1) Failed to load users/passwords/role files: java.io.IOException: No properties file: ${jboss.server.config.dir}/roles.properties or defaults: defaultRoles.properties found at org.jboss.security.auth.spi.Util.loadProperties(Util.java:228) [picketbox-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.auth.spi.CertRolesLoginModule.loadRoles(CertRolesLoginModule.java:153) [picketbox-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.auth.spi.CertRolesLoginModule.initialize(CertRolesLoginModule.java:108) [picketbox-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [rt.jar:1.6.0_26] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [rt.jar:1.6.0_26] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:449) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:383) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:371) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:160) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:287) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.apache.catalina.authenticator.SSLAuthenticator.authenticate(SSLAuthenticator.java:135) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:455) [jbossweb-7.0.16.Final-redhat-1.jar:] at com.jboss.datagrid.endpoint.RestSecurityContext.invoke(RestSecurityContext.java:143) [jboss-datagrid-server-integration-6.0.0.ER11-redhat-1.jar:6.0.0.ER11-redhat-1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] {code} However, when I put the absolute path to that file, it is found. This is noticeable difference from UsersRoles module where it works as expected. The problem is in class picketbox/security-jboss-sx/jbosssx/src/main/java/org/jboss/security/auth/spi/CertRolesLoginModule.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] (AS7-6011) After redeploy an application to a domain the old content is not removed at slave host

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-6011: ------------------------------------- Summary: After redeploy an application to a domain the old content is not removed at slave host Key: AS7-6011 URL: https://issues.jboss.org/browse/AS7-6011 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.2.0.Alpha1 Environment: OS Fedora17 Two instances in domain mode. DC without server HC with one server Reporter: Wolf-Dieter Fink Assignee: Brian Stansberry If an application deployed on a domain slave HC the content is not removed if a new version of the application is deployed with 'deploy xxx --force' The logfile looks correct and shows: JBAS018565: Replaced deployment "appone.ear" with deployment "appone.ear" JBAS014901: Content removed from location /.../domain/servers/server-one/data/content/5e/c06cd5b58b1b6578188d822b351a14f974804c/content If the folder is checked the file still exists. An undeploy remove the files correct with the same log messages. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5899) UCS-2 CodeSet Interop Issue

by Nick Cross (JIRA)

[ https://issues.jboss.org/browse/AS7-5899?page=com.atlassian.jira.plugin.s... ] Nick Cross reassigned AS7-5899: ------------------------------- Assignee: Brad Maxwell (was: Nick Cross) > UCS-2 CodeSet Interop Issue > --------------------------- > > Key: AS7-5899 > URL: https://issues.jboss.org/browse/AS7-5899 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.2.Final (EAP) > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Labels: jacorb > Fix For: Open To Community > > > Interoperability issue when client in JBoss EAP 6 calls IBM WebSphere. The client in JBoss EAP 6 sends "foo" but the server side IBM WebSphere receives "?foo" -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6004) Inconsistent tab completion behaviour between commands and arguments

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6004: -------------------------------- Summary: Inconsistent tab completion behaviour between commands and arguments Key: AS7-6004 URL: https://issues.jboss.org/browse/AS7-6004 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Jeff Mesnil Assignee: Alexey Loubyansky Priority: Minor When tab is used for completion, the behavior changes when there is only 1 remaining candidate. For commands, when the completion leads to a single candidate, a whitespace is appended and we can proceed to the arguments For arguments using a TabCompleter, when the completion leads to a single candidate, no whitespace is appended and we have to type it to be able to proceed to the next argument Example: * deployment-over<TAB> => will complete to deployment-overlay<WHITESPACE><CURSOR> (a whitespace is appended to the single candidate) * deployment-overlay a<TAB> => will complete to deployment-over add<CURSOR> (no whitespace appended even though add is the only candidate matched) -- 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

13 years, 5 months

2
4
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 November 2012