August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (LOGMGR-21) Getting a logger resets its level, often to INFO

by David Lloyd (JIRA)

Getting a logger resets its level, often to INFO ------------------------------------------------ Key: LOGMGR-21 URL: https://jira.jboss.org/browse/LOGMGR-21 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.0.CR4 Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.0.CR5 Part of LOGMGR-17 included the change where levels are associated with a logger node, not a logger. However loggers are still configured to initialize level on every create, which happens frequently (especially in light of LOGMGR-20). Fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (LOGMGR-22) Improve initial log manager error handling

by David Lloyd (JIRA)

Improve initial log manager error handling ------------------------------------------ Key: LOGMGR-22 URL: https://jira.jboss.org/browse/LOGMGR-22 Project: JBoss Log Manager Issue Type: Task Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.0.CR4 Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.0.CR5 When processing logger.properties, be a bit more tolerant of errors. If an error occurs, print it to stderr and proceed rather than blowing up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (LOGMGR-20) Resource lookup cascades to parent loggers even though parent loggers will never have resources

by David Lloyd (JIRA)

Resource lookup cascades to parent loggers even though parent loggers will never have resources ----------------------------------------------------------------------------------------------- Key: LOGMGR-20 URL: https://jira.jboss.org/browse/LOGMGR-20 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.0.CR4 Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.0.CR5 The fix for LOGMGR-17 implies that resource bundles can't be inherited from parent loggers (which makes sense considering that parent loggers can go away at any time). Stop wasting time (a lot of time) creating parent loggers only to have them immediately GC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2145) StackOverFlowError while resolving jndi name from ScopedEJBReferenceResolver

by jaikiran pai (JIRA)

StackOverFlowError while resolving jndi name from ScopedEJBReferenceResolver ---------------------------------------------------------------------------- Key: EJBTHREE-2145 URL: https://jira.jboss.org/browse/EJBTHREE-2145 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: bom-eap5-0.1.3, EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai If a deployment unit contains more than 2 child units then the ScopedEJBReferenceResolver can run into StackOverFlowError while resolving the jndi name. Please refer to the referenced forum thread for the complete details. Here's just a part of the stacktrace: at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:72) at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:80) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-799) Remove VFS 3 changes from 2.1 branch

by Kabir Khan (JIRA)

Remove VFS 3 changes from 2.1 branch ------------------------------------ Key: JBAOP-799 URL: https://jira.jboss.org/browse/JBAOP-799 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.1.9.GA The VFS3 changes added in 2.1.9.Alpha1 were for testing a given version in AS to see that VFS3 and AOP played nicely. The VFS3 work done in 2.1.9.Alpha1 went GA in 2.2.0.GA since VFS 3 introduces some backwards compatibiliy. The 2.1 branch which _might_ be used for bug fixes for EAP 5.x should continue using VFS 2 2.2 onwards uses VFS 3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-798) Need privileged block in ClassProxyFactory.populateMethodTables()

by Kabir Khan (JIRA)

Need privileged block in ClassProxyFactory.populateMethodTables() ----------------------------------------------------------------- Key: JBAOP-798 URL: https://jira.jboss.org/browse/JBAOP-798 Project: JBoss AOP Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: 2.1.6.GA Reporter: Kabir Khan Assignee: Kabir Khan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (GPD-399) switching between source and diagram duplicates text tag

by Veiko Vaade (JIRA)

switching between source and diagram duplicates text tag -------------------------------------------------------- Key: GPD-399 URL: https://jira.jboss.org/browse/GPD-399 Project: jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM jPDL Designer 4.4 Environment: Eclipse 3.6, Windows 7 Reporter: Veiko Vaade Assignee: Koen Aers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8331) Make AS Embedded example using 6.0.0.M4

by Andrew Lee Rubinger (JIRA)

Make AS Embedded example using 6.0.0.M4 --------------------------------------- Key: JBAS-8331 URL: https://jira.jboss.org/browse/JBAS-8331 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M4 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 6.0.0.M4 Create a tag for Embedded usage examples using AS 6.0.0.M4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2581) Reference manuals: fix layouting issues (some surfacing by switch to jbossorg style)

by Geoffrey De Smet (JIRA)

Reference manuals: fix layouting issues (some surfacing by switch to jbossorg style) ------------------------------------------------------------------------------------ Key: JBRULES-2581 URL: https://jira.jboss.org/browse/JBRULES-2581 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-docs, drools-docs-expert, drools-docs-flow, drools-docs-fusion, drools-docs-solver Affects Versions: 5.1.0.M2 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: 5.1.0.CR1 Problems include: * <kw> in red * bullet item that starts with an empty line -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (SECURITY-515) JavaEE Authorization Helpers have methods with long signatures

by Anil Saldhana (JIRA)

JavaEE Authorization Helpers have methods with long signatures -------------------------------------------------------------- Key: SECURITY-515 URL: https://jira.jboss.org/browse/SECURITY-515 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, PicketBox, Security SPI Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta6 The authorization helpers in AS5 from security project have long signatures (greater than 7 parameters). Need to have api methods that take in wrapper/holder objects and deprecate the previous methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
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 August 2010