March 2010 - jboss-jira - Jboss List Archives

[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

14 years, 9 months

3
13
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

14 years, 9 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

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-481) SecurityAssociation->getContextInfo and setContextInfo methods to take in Object key for backwards compatibility

by Anil Saldhana (JIRA)

SecurityAssociation->getContextInfo and setContextInfo methods to take in Object key for backwards compatibility ---------------------------------------------------------------------------------------------------------------- Key: SECURITY-481 URL: https://jira.jboss.org/jira/browse/SECURITY-481 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta4 Classes to change: SecurityAssociation.java and LegacySecurityAssociationUnitTestCase -- 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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-39) TCLMCFilter does not work with AsyncAppender

by Alexis Hassker (JIRA)

TCLMCFilter does not work with AsyncAppender -------------------------------------------- Key: JBLOGGING-39 URL: https://jira.jboss.org/jira/browse/JBLOGGING-39 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-log4j Affects Versions: 2.1.1.GA-jboss-logging Environment: Linux Ubuntu 9.10, JBoss 5.1.0, Logging 2.1.1, JDK 6 Reporter: Alexis Hassker Assignee: David Lloyd I followed http://community.jboss.org/wiki/SeparatingApplicationLogs to use the new TCLMCFilter in JBoss 5.1.0. It works fine when I associate the appender directly to the root logger. When I associate the appender to a AsyncAppender, there is no more log. -- 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

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1796) Dead locak while simultaneously shutdown of nodes in a cluster

by Howard Gao (JIRA)

Dead locak while simultaneously shutdown of nodes in a cluster -------------------------------------------------------------- Key: JBMESSAGING-1796 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1796 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.6.GA, 1.4.0.SP3.CP10 Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.0.SP3.CP11, 1.4.6.GA.SP1 -- 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

14 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-7829) Port org.jboss.jmx.adaptor.html.ClusteredConsoleServlet to use the JSR-160 client API

by David Lloyd (JIRA)

Port org.jboss.jmx.adaptor.html.ClusteredConsoleServlet to use the JSR-160 client API ------------------------------------------------------------------------------------- Key: JBAS-7829 URL: https://jira.jboss.org/jira/browse/JBAS-7829 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: JBossAS-6.0.0.M3 Also move it out of the org.jboss.jmx.adaptor package. -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-38) Enforce JDK6+ compiler

by Andrew Lee Rubinger (JIRA)

Enforce JDK6+ compiler ---------------------- Key: JBLOGGING-38 URL: https://jira.jboss.org/jira/browse/JBLOGGING-38 Project: JBoss Logging Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-logmanager Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Using JDK5 leads to: [INFO] Compilation failure /home/alr/business/jboss/wc/common/jboss-logmanager/trunk/src/main/java/org/jboss/logmanager/PropertyConfigurator.java:[78,22] load(java.io.InputStream) in java.util.Properties cannot be applied to (java.io.InputStreamReader) /home/alr/business/jboss/wc/common/jboss-logmanager/trunk/src/main/java/org/jboss/logmanager/PropertyConfigurator.java:[78,22] load(java.io.InputStream) in java.util.Properties cannot be applied to (java.io.InputStreamReader) Enforce the environment. -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-42) Include version information in stack traces

by Randall Hauch (JIRA)

Include version information in stack traces ------------------------------------------- Key: JBLOGGING-42 URL: https://jira.jboss.org/jira/browse/JBLOGGING-42 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Randall Hauch Assignee: David Lloyd Priority: Minor Including JAR and version information for each class in a stack trace provides a lot of useful information. For example (taken from the LogBack documentation): 14:28:48.835 [btpool0-7] INFO c.q.l.demo.prime.PrimeAction - 99 is not a valid value java.lang.Exception: 99 is invalid at ch.qos.logback.demo.prime.PrimeAction.execute(PrimeAction.java:28) [classes/:na] at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) [struts-1.2.9.jar:1.2.9] at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) [struts-1.2.9.jar:1.2.9] at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) [struts-1.2.9.jar:1.2.9] at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [servlet-api-2.5-6.1.12.jar:6.1.12] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) [jetty-6.1.12.jar:6.1.12] at ch.qos.logback.demo.UserServletFilter.doFilter(UserServletFilter.java:44) [classes/:na] at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) [jetty-6.1.12.jar:6.1.12] -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6292) Documentation should include transitioning from AS 4.2 to AS 5.0

by Bruce Link (JIRA)

Documentation should include transitioning from AS 4.2 to AS 5.0 ---------------------------------------------------------------- Key: JBAS-6292 URL: https://jira.jboss.org/jira/browse/JBAS-6292 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Affects Versions: JBossAS-5.0.0.GA Environment: Not applicable Reporter: Bruce Link Assignee: Samson Kittoli The installation and getting started guide should have a chapter on transitioning applications from JBoss AS 4.2 to JBoss AS 5.0. Examples discussed might be changes in build class path and configuration documents. For example, when using EJB3, the persistence.xml seems to need to specify a JBoss schema. The release notes is vague in this area. -- 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

14 years, 9 months

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010