April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3005) decision table building => NPE

by Wolfgang Laun (JIRA)

decision table building => NPE ------------------------------ Key: JBRULES-3005 URL: https://issues.jboss.org/browse/JBRULES-3005 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor kBuilder.add( resource, resourceType.DTABLE ); results in a NPE: Exception in thread "main" java.lang.NullPointerException at org.drools.decisiontable.DecisionTableProviderImpl.compileStream(DecisionTableProviderImpl.java:26) at org.drools.decisiontable.DecisionTableProviderImpl.loadFromInputStream(DecisionTableProviderImpl.java:19) at org.drools.compiler.DecisionTableFactory.loadFromInputStream(DecisionTableFactory.java:18) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:497) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at rss.drools.setup.Application.setup(Application.java:47) Notice that a simple DecisionTableConfiguration dtConf = KnowledgeBuilderFactory.newDecisionTableConfiguration(); kBuilder.add( resource, resourceType, dtConf ); is not sufficient, the DecisionTableConfiguration still needs a DecisionTableInputType Expected. there is a reasonable default DecisionTableConfiguration with DecisionTableInputType.XLS being set. The simple call worked fine in 5.1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-9329) Restore persistent configuration changes

by Thomas Diesler (JIRA)

Restore persistent configuration changes ----------------------------------------- Key: JBAS-9329 URL: https://issues.jboss.org/browse/JBAS-9329 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler The ConfigAdminService used the ServerConfigurationPersister in the past. The code is currently commented out -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2297) Enable marshalling of events in drools fusion

by Maciej Prochniak (JIRA)

Enable marshalling of events in drools fusion --------------------------------------------- Key: JBRULES-2297 URL: https://jira.jboss.org/jira/browse/JBRULES-2297 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core, drools-core (fusion) Affects Versions: 5.1.0.M1 Reporter: Maciej Prochniak Assignee: Mark Proctor Currently, when one tries to (un)marshall EventFactHandle an exception is thrown, as default marshaller recognizes only DefaultFactHandle. -- 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, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-9231) Expose platform mxbeans via the domain model

by Brian Stansberry (JIRA)

Expose platform mxbeans via the domain model -------------------------------------------- Key: JBAS-9231 URL: https://issues.jboss.org/browse/JBAS-9231 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Expose the java.lang.managment MXBeans. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation

by Andrew Lee Rubinger (JIRA)

Implement a Graceful Shutdown API and Implementation ----------------------------------------------------- Key: JBBOOT-116 URL: https://jira.jboss.org/jira/browse/JBBOOT-116 Project: JBoss Bootstrap Issue Type: Feature Request Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger As identified by the Summer 2009 AS Meeting. Requirements: * Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies * 2-phase event-listener registration API * May be injected into MC Beans * 1st phase is a concurrent broadcast to all subsystems which have registered: "prepare for shutdown" * When all listeners have reported "ready", fire 2nd phase: "shutdown" -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWEB-171) ClusteredSession.setAttribute() could report the attribute name and/or class FQN when not serializable

by James Livingston (JIRA)

ClusteredSession.setAttribute() could report the attribute name and/or class FQN when not serializable ------------------------------------------------------------------------------------------------------ Key: JBWEB-171 URL: https://jira.jboss.org/browse/JBWEB-171 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cluster Affects Versions: JBossWeb-2.1.3.GA Reporter: James Livingston Assignee: Remy Maucherat Priority: Minor org.jboss.web.tomcat.service.session.ClusteredSession.setAttribute() raises an exception with the clusteredSession.setAttribute.iae message if the attribute can't be replicated (i.e. isn't Serializable or a primitive). It would be nice if it mentioned the attribute name and/or the class FQN in the error message to aid in debugging. -- 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

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-58) Support setting the logging provider explicitly

by Dan Allen (JIRA)

Support setting the logging provider explicitly ----------------------------------------------- Key: JBLOGGING-58 URL: https://issues.jboss.org/browse/JBLOGGING-58 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Priority: Minor Fix For: 3.0.0.Beta5-jboss-logging Currently, JBoss Logging uses a classloading approach to look for a logging provider based on a hardcoded order of precedence. While this is sufficient for the default case, there should be a way to specify the logger explicitly, in the case that there is more than one concrete logging implementation on the classpath. The override should be part of the API, though a system property could also be supported. The API would take precedence. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBVFS-159) Native memory leak due to ZipEntryInputStream

by Samuel Cai (JIRA)

Native memory leak due to ZipEntryInputStream --------------------------------------------- Key: JBVFS-159 URL: https://jira.jboss.org/browse/JBVFS-159 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.2.GA Environment: Redhat (not sure what version) 2.6.9-78.ELsmp JBoss 5.1.0.GA JDK 1.6.0_20 JVM parameter: -XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -verbose:gc -Dfile.encoding=iso-8859-1 -server -Djava.net.preferIPv4Stack=true -Doracle.jdbc.V8Compatible=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dnetworkaddress.cache.ttl=300 -Xss128k -Xmn500m -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -XX:+PrintGCDetails -XX:PermSize=256m -XX:MaxPermSize=256m -Xms1500m -Xmx1500m -XX:+HeapDumpOnOutOfMemoryError -XX:+UseConcMarkSweepGC Reporter: Samuel Cai Assignee: John Bailey We used to use JBoss 4.2.1.GA and JDK 1.6.0_11, and trying JBoss 5.1.0.GA and JDK 1.6.0_20 these days. I found the process size is more larger than before, 2.5G~2.9G compared to 1.9G. I was thinking this was a bug of JBoss AS, then filed https://jira.jboss.org/browse/JBAS-8066 After these days investigation, I think this is a memory leak in VFS, maybe only happen on our specific environment. I tried a change on class org.jboss.virtual.plugins.context.zip.ZipFileWrapper, method openStream: From: ZipEntryInputStream zis = new ZipEntryInputStream(this, is); return zis; To: //ZipEntryInputStream zis = new ZipEntryInputStream(this, is); //return zis; return is; That is, don't use ZipEntryInputStream, let any class/method invoking openStream to close zipFile's inputStream immediatelly. ZipFile will be in open status, but all steams will be closed well. This makes the process size down to same as JBoss 4's. I tried going through first 3 pages of site, no problems. May need QA team to test more. Btw, I tried updating VFS to 2.1.3.SP1/2.2.0.M4/3.0.0.CR5, first two have same size issue, third one couldn't start. -- 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

14 years, 10 months

6
31
0 / 0

[JBoss JIRA] Created: (JBWEB-168) Limit JspRuntimeContext jsps Map retention

by Mike Millson (JIRA)

Limit JspRuntimeContext jsps Map retention ------------------------------------------ Key: JBWEB-168 URL: https://jira.jboss.org/jira/browse/JBWEB-168 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-3.0.0.Beta1, JBossWeb-2.1.7.GA, JBossWeb-2.0.0.GA_CP10 Reporter: Mike Millson Assignee: Remy Maucherat Applications with a large number of JSP pages or very large JSP page sizes can lead to retention in the JspRuntimeContext jsps Map. Backport the following Tomcat 7 functionality to limit retention: https://issues.apache.org/bugzilla/show_bug.cgi?id=48358 -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBLOGGING-60) Logger#getMessageLogger() should allow category to be specified as class

by Dan Allen (JIRA)

Logger#getMessageLogger() should allow category to be specified as class ------------------------------------------------------------------------ Key: JBLOGGING-60 URL: https://issues.jboss.org/browse/JBLOGGING-60 Project: JBoss Logging Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd To be consistent with the getLogger() method on Logger: static Logger getLogger(String category) static Logger getLogger(Class<?> category) the getMessageLogger() should allow the category to be specified as a class by adding these additional methods static <T> T getMessageLogger(Class<T> type, Class<?> category) static <T> T getMessageLogger(Class<T> type, Class<?> category, Locale locale) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
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 2011