February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-782) DefaultAuthenticationCacheFactory should not use internal Infinispan classes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/WFLY-782?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant commented on WFLY-782: -------------------------------------- This ones needs to be fixed during the 9.x cycle > DefaultAuthenticationCacheFactory should not use internal Infinispan classes > ---------------------------------------------------------------------------- > > Key: WFLY-782 > URL: https://issues.jboss.org/browse/WFLY-782 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Reporter: NadirX > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > The DefaultAuthenticationCacheFactory class (and the AuthenticationCacheEvictionListener class) use internal Infinispan classes which are subject to change without API stability guarantees. The code should be rewritten to use an Infinispan cache instead. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1809) The security subsystem plugins use deprecated Infinispan API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/WFLY-1809?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on WFLY-1809: --------------------------------------- Actually I wrote the PR and it was pulled last August by Brian > The security subsystem plugins use deprecated Infinispan API > ------------------------------------------------------------ > > Key: WFLY-1809 > URL: https://issues.jboss.org/browse/WFLY-1809 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.0.0.Alpha3 > Reporter: NadirX > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 8.0.0.Final > > > org.jboss.as.security.plugins.JNDIBasedSecurityManagement uses a deprecated way of configuring an Infinispan cache which must be removed. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-782) DefaultAuthenticationCacheFactory should not use internal Infinispan classes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/WFLY-782?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant updated WFLY-782: --------------------------------- Fix Version/s: 9.0.0.CR1 > DefaultAuthenticationCacheFactory should not use internal Infinispan classes > ---------------------------------------------------------------------------- > > Key: WFLY-782 > URL: https://issues.jboss.org/browse/WFLY-782 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Reporter: NadirX > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > The DefaultAuthenticationCacheFactory class (and the AuthenticationCacheEvictionListener class) use internal Infinispan classes which are subject to change without API stability guarantees. The code should be rewritten to use an Infinispan cache instead. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2754) Make auditlog syslog appName configurable

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2754?page=com.atlassian.jira.plugin.... ] Kabir Khan reopened WFLY-2754: ------------------------------ > Make auditlog syslog appName configurable > ----------------------------------------- > > Key: WFLY-2754 > URL: https://issues.jboss.org/browse/WFLY-2754 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kyle Lape > Assignee: Kabir Khan > Fix For: 8.0.0.Final > > > Some initial code in my https://github.com/kabir/wildfly/tree/audit-log-facility-mgmt-api branch. Once done the workaround in WFLY-2753 should be removed -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2747) Make auditlog syslog facility configurable

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2747?page=com.atlassian.jira.plugin.... ] Kabir Khan reopened WFLY-2747: ------------------------------ > Make auditlog syslog facility configurable > ------------------------------------------ > > Key: WFLY-2747 > URL: https://issues.jboss.org/browse/WFLY-2747 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Final > > > Some initial code in my https://github.com/kabir/wildfly/tree/audit-log-facility-mgmt-api branch. Once done the workaround in WFLY-2746 should be removed -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1809) The security subsystem plugins use deprecated Infinispan API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/WFLY-1809?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned WFLY-1809: ------------------------------------- Assignee: Tristan Tarrant (was: Paul Ferraro) > The security subsystem plugins use deprecated Infinispan API > ------------------------------------------------------------ > > Key: WFLY-1809 > URL: https://issues.jboss.org/browse/WFLY-1809 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.0.0.Alpha3 > Reporter: NadirX > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 9.0.0.CR1 > > > org.jboss.as.security.plugins.JNDIBasedSecurityManagement uses a deprecated way of configuring an Infinispan cache which must be removed. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated WFLY-943: -------------------------------- Comment: was deleted (was: Dear sir, madam, Thank you, your e-mail has arrived. Unfortunately I am not available to answer your message at the moment. I am out of office, starting from 20-12-2013. As of 02-01-2014, I will be able to answer your e-mail again. Met vriendelijke groet/ Kind regards, ing. Jan-Willem Mulder Head of Back End Development E: jan-willem.mulder(a)isaac.nl<mailto:jan-willem.mulder@isaac.nl> T: 040 215 53 58 - M: 06 11 34 81 48 - F: 040 290 89 80 - W: http://www.isaac.nl/ Marconilaan 16, 5621 AA Eindhoven - The Netherlands Dit e-mailbericht is alleen bestemd voor de geadresseerde(n). Indien dit bericht niet voor u is bedoeld wordt u verzocht de afzender hiervan op de hoogte te stellen door het bericht te retourneren en de inhoud niet te gebruiken. Aan dit bericht kunnen geen rechten worden ontleend. ) > XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ----------------------------------------------------------------------------------- > > Key: WFLY-943 > URL: https://issues.jboss.org/browse/WFLY-943 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.Alpha3 > Reporter: Elias Ross > Fix For: 8.0.0.Final > > Attachments: jboss-deployment-structure.xml > > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1376) HttpServletResponseImpl.getWriter() cannot be called: getOutputStream() already called

by nathan dennis (JIRA)

[ https://issues.jboss.org/browse/WFLY-1376?page=com.atlassian.jira.plugin.... ] nathan dennis commented on WFLY-1376: ------------------------------------- Actual I believe the bug which I was seeing was WFLY-2688. It has also been fixed in trunk. > HttpServletResponseImpl.getWriter() cannot be called: getOutputStream() already called > -------------------------------------------------------------------------------------- > > Key: WFLY-1376 > URL: https://issues.jboss.org/browse/WFLY-1376 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha2 > > > When I invoke a RESTful web service for a not existing URI (resulting in a 404 error) I'm getting the stacktrace below. This is working fine with EAP 6.1.Beta. > In web.xml I have this declaration for a 404 error and a JSF-based error page: > <error-page> > <error-code>404</error-code> > <location>/error/pageNotFound.jsf</location> > </error-page> > Stacktrace: > 12:36:03,921 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] Error Rendering View[/error/pageNotFound.xhtml]: java.lang.IllegalStateException: UT010006: Cannot call getWriter(), getOutputStream() already called > at io.undertow.servlet.spec.HttpServletResponseImpl.getWriter(HttpServletResponseImpl.java:284) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at com.sun.faces.context.ExternalContextImpl.getResponseOutputWriter(ExternalContextImpl.java:834) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at javax.faces.context.ExternalContextWrapper.getResponseOutputWriter(ExternalContextWrapper.java:785) [jboss-jsf-api_2.2_spec-2.2.0-m13.jar:2.2.0-m13] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.createResponseWriter(FaceletViewHandlingStrategy.java:1166) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:390) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.0-m13.jar:2.2.0-m13] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.0-m13.jar:2.2.0-m13] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) [jsf-impl-2.2.0-m13-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) [jboss-jsf-api_2.2_spec-2.2.0-m13.jar:2.2.0-m13] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:82) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:54) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.server.HttpHandlers.executeHandler(HttpHandlers.java:46) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:116) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:79) > at io.undertow.server.HttpHandlers.executeHandler(HttpHandlers.java:46) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:26) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.server.HttpHandlers.executeHandler(HttpHandlers.java:46) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:26) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:108) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:93) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:367) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:286) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:124) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:106) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.handlers.ServletInitialHandler.handleRequest(ServletInitialHandler.java:83) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:52) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:544) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2855) ejb-annotation-property-replacement attribute has misleading name

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2855?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-2855: ------------------------------------ Assignee: Stuart Douglas > ejb-annotation-property-replacement attribute has misleading name > ----------------------------------------------------------------- > > Key: WFLY-2855 > URL: https://issues.jboss.org/browse/WFLY-2855 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Blocker > > It should be ee-annotation-property-replacement, as it refers to all EE annotations, not just EJB ones. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2856) Classloader leak caused by xnio-file-watcher

by Harald Wellmann (JIRA)

Harald Wellmann created WFLY-2856: ------------------------------------- Summary: Classloader leak caused by xnio-file-watcher Key: WFLY-2856 URL: https://issues.jboss.org/browse/WFLY-2856 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.0.0.CR1 Reporter: Harald Wellmann After redeploying my application from Eclipe/JBoss Tools via "Full Publish" a couple of times in a row, I'm getting a PermGen OutOfMemoryError. In jvisualvm, I can see multiple threads named xnio-file-watcher, each having its context classloader set to the module classloader of my (undeployed) application. Probably the thread should be stopped (but isn't) when the application is undeployed. This leak only occurs with unzipped deployments. I also see these extra threads independent of Eclipse when copying an unzipped deployment to {{standalone/deployments}} and adding/removing the dodeploy/deployed marker files. -- 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

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2014