April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2072) Remove references to jboss logging appenders (and levels) from log4j.xml files of testsuite

by jaikiran pai (JIRA)

Remove references to jboss logging appenders (and levels) from log4j.xml files of testsuite ------------------------------------------------------------------------------------------- Key: EJBTHREE-2072 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2072 Project: EJB 3.0 Issue Type: Task Components: testsuite Reporter: jaikiran pai Assignee: jaikiran pai With the upgrade to 3.0.0.Beta2 of jboss-logging in AS trunk, we have started seeing: [junit] log4j:ERROR Could not create level [TRACE]. Reported error follows. [junit] java.lang.ClassNotFoundException: org.jboss.logging.XLevel [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:307) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:252) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:169) [junit] at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178) [junit] at org.apache.log4j.xml.DOMConfigurator.parseLevel(DOMConfigurator.java:519) [junit] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:438) [junit] at org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:345) [junit] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:827) [junit] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) [junit] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) [junit] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470) [junit] at org.apache.log4j.LogManager.<clinit>(LogManager.java:122) [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:247) [junit] at org.jboss.logging.LoggerProviders.findProvider(LoggerProviders.java:37) [junit] at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:28) [junit] at org.jboss.logging.Logger.getI18nLogger(Logger.java:2124) [junit] at org.jboss.logging.Logger.getLogger(Logger.java:2162) [junit] at org.jboss.logging.Logger.getLogger(Logger.java:2187) [junit] at org.jboss.test.AbstractTestCase.<clinit>(AbstractTestCase.java:50) [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:169) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:335) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768) [junit] log4j:ERROR Could not create an Appender. Reported error follows. [junit] java.lang.ClassNotFoundException: org.jboss.logging.appender.DailyRollingFileAppender These classes no longer exist in this version of jboss-logging. Effectively, there's no logging going on, on the client side. In any case, we don't need any JBoss specific appenders in that log4j.xml. Just falling back on log4j specific appenders and log4j specific appenders should be enough. Update the log4j.xml file accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-263) Use interfaces and generics in HAPartition method signatures.

by Brian Stansberry (JIRA)

Use interfaces and generics in HAPartition method signatures. ------------------------------------------------------------- Key: JBCLUSTER-263 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-263 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Server-API Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Server-API 2.0.0.Beta1 Get down w/ JDK 5 Convert RPC return values from ArrayList to List<Object> Use List<ClusterNode> in place of Vector. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-220) HAPartition.callMethodOnCluster() is not reentrant

by Fol de Rol (JIRA)

HAPartition.callMethodOnCluster() is not reentrant -------------------------------------------------- Key: JBCLUSTER-220 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-220 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: HA-Server-API Reporter: Fol de Rol Assignee: Brian Stansberry Priority: Blocker An RPC handler of callMethodOnCluster() cannot in its turn call callMethodOnCluster() querying other services. The second call blocks until timeout is reached and returns without results. The same relates to facilities based on this method like Distributed Replicant Manager. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-262) Clean up use of methodTimeout in HAPartition

by Brian Stansberry (JIRA)

Clean up use of methodTimeout in HAPartition -------------------------------------------- Key: JBCLUSTER-262 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-262 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Client Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Client 2.0.0.BETA1 It's exposed as a param in some async methods where it's irrelevant. Then add overloaded versions of the sync RPC methods where it's not there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-225) HAPartition's HAExtendedMembershipListener exposes JGroups internals

by Brian Stansberry (JIRA)

HAPartition's HAExtendedMembershipListener exposes JGroups internals -------------------------------------------------------------------- Key: JBCLUSTER-225 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-225 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.1.0.GA, HA-Server-API 1.2.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Server-API 2.0.0.Beta1 The actual type of the "originatingGroups" param is Vector<org.jgroups.View>. It should be Vector<List<ClusterNode>> or better yet List<List<ClusterNode>>. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2108) A rule does not fire for all objects satisfying the rule code.

by Andrey Nechaev (JIRA)

A rule does not fire for all objects satisfying the rule code. -------------------------------------------------------------- Key: JBRULES-2108 URL: https://jira.jboss.org/jira/browse/JBRULES-2108 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 4.0.7 Reporter: Andrey Nechaev Assignee: Mark Proctor The following code shows the problem: public class DroolsTest { private final static int NUM_FACTS = 20; private final static String rule = "" + "package test\n" + "import com.test.DroolsTest;\n" + "import com.test.DroolsTest.Foo;\n" + "import com.test.DroolsTest.Bar;\n" + "rule test\n" + "\twhen\n" + "\t\tFoo($p : id < " + Integer.toString(NUM_FACTS) + ") && Bar(id == $p)\n" + "\tthen\n" + "\t\tDroolsTest.incCounter();\n" + "end"; private static int counter; public static class Foo { private final int id; Foo(int id) { this.id = id; } public int getId() { return id; } } public static class Bar { private final int id; Bar(int id) { this.id = id; } public int getId() { return id; } } public static void main(String[] args) throws Exception { RuleBase rb; WorkingMemory wm; counter = 0; rb = RuleBaseFactory.newRuleBase(); wm = rb.newStatefulSession(); for(int i = 0; i < NUM_FACTS; i++) { wm.insert(new Foo(i)); wm.insert(new Bar(i)); } PackageBuilder bld = new PackageBuilder(); bld.addPackageFromDrl(new StringReader(rule)); rb.addPackage(bld.getPackage()); System.out.println(counter == NUM_FACTS ? "passed" : "failed"); } public static void incCounter() { ++counter; } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-264) Genericize DRM

by Brian Stansberry (JIRA)

Genericize DRM -------------- Key: JBCLUSTER-264 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-264 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Server-API Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Server-API 1.1.1GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-501) Security Managers for authentication, authz, Mapping and Audit should prune the passed security domain

by Anil Saldhana (JIRA)

Security Managers for authentication, authz,Mapping and Audit should prune the passed security domain ----------------------------------------------------------------------------------------------------- Key: SECURITY-501 URL: https://jira.jboss.org/jira/browse/SECURITY-501 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta4, JBossSecurity_2.0.4.SP3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta5 There may be cases where we may see: 11:32:58,049 TRACE [org.jboss.security.plugins.mapping.JBossMappingManager] Application Policy not found for domain=java:/jaas/cts.Mapping framework will use the default domain:other As you can see, the security domain the mapping manager is expecting is "cts" and we have the java:/jaas prefix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-500) JBossMappingManager has loadClass bottleneck

by Anil Saldhana (JIRA)

JBossMappingManager has loadClass bottleneck -------------------------------------------- Key: SECURITY-500 URL: https://jira.jboss.org/jira/browse/SECURITY-500 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta4, JBossSecurity_2.0.4.SP3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-499) JBossAuditManager has loadClass bottleneck

by Anil Saldhana (JIRA)

JBossAuditManager has loadClass bottleneck ------------------------------------------ Key: SECURITY-499 URL: https://jira.jboss.org/jira/browse/SECURITY-499 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta4, JBossSecurity_2.0.4.SP3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 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 April 2010