July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1175) Upgrade Infinispan to 5.0.0.CR7

by Paul Ferraro (JIRA)

Upgrade Infinispan to 5.0.0.CR7 ------------------------------- Key: AS7-1175 URL: https://issues.jboss.org/browse/AS7-1175 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.0.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.0.Final Contains yet another minor API change affecting EvictionListeners -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1170) support configuration of number of virtual nodes

by Michal Linhard (JIRA)

support configuration of number of virtual nodes ------------------------------------------------ Key: AS7-1170 URL: https://issues.jboss.org/browse/AS7-1170 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Affects Versions: 7.0.0.CR1 Reporter: Michal Linhard Assignee: Paul Ferraro Priority: Critical I recently played with consistent hash function implementation and produced various performance statistics. It shows that number of virtual nodes (configuration parameter I98 in https://docspace.corp.redhat.com/docs/DOC-69249) has substantial effect on performance. (it makes distribution of data among nodes in the cluster much more even and thus avoids overstressing of one particular node, that would then hinder performance of the whole cluster) If the next EDG6 Alpha build will take configuration from infinispan subsystem, we'll need to have this configurable, otherwise we won't be able to execute some very important performance comparisons. it applies to the level of subsystem.cache-container.distributed-cache so I propose addition of configuration parameter: subsystem.cache-container.distributed-cache.numVirtualNodes that would have the same effect as I98 infinispan.configuration.clustering.hash.numVirtualNodes -- 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

[JBoss JIRA] Created: (JBLOGGING-54) MDC entries do not appear in jboss log

by Chris Jansen (JIRA)

MDC entries do not appear in jboss log -------------------------------------- Key: JBLOGGING-54 URL: https://issues.jboss.org/browse/JBLOGGING-54 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-spi Affects Versions: 3.0.0.Beta4-jboss-logging Environment: 64bit Linux, JDK1.6.0_23 Reporter: Chris Jansen Assignee: David Lloyd As per title, MDC entries do not appear in jboss log when using the log pattern "%d %-5p [%c] (%t) [%X{user} %X{task}] - %s%E%n" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (AS7-1192) Classloader Thread.currentThread().getContextClassLoader() no longer inspects WEB-INF/lib

by Gerry Matte (JIRA)

Classloader Thread.currentThread().getContextClassLoader() no longer inspects WEB-INF/lib ----------------------------------------------------------------------------------------- Key: AS7-1192 URL: https://issues.jboss.org/browse/AS7-1192 Project: Application Server 7 Issue Type: Bug Components: Naming, Web Affects Versions: 7.0.0.CR1 Environment: Windows 7 64 bit with java 1.6 U24 installed (both 64 bit - default version) and with 32 bit installed. Eclipse Indigo 32 bit running with 32 bit jvm by using command line option -vm C:\s\java32\bin\javaw.exe JBoss Tools 3.3.0-M2 installed within Eclipse Jboss AS 7.0.0.CR1 running using 64 bit JVM from Dos using unmodified standalone.bat Also when started via Eclipse server runtime. Reporter: Gerry Matte Web applications on JBoss AS 6 and earlier could use the class loader to find and load a properties file stored in WEB/lib Jboss 7 seems to not find the properties file. Until now I believed that this folder was considered to be part of the classpath for a webapp. Perhaps it is not ? I will attach a test eclipse project and a war file either to this bug report or to the forum posting. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1165) Improve error message(s) of deployment failures

by jaikiran pai (JIRA)

Improve error message(s) of deployment failures ------------------------------------------------ Key: AS7-1165 URL: https://issues.jboss.org/browse/AS7-1165 Project: Application Server 7 Issue Type: Enhancement Affects Versions: 7.0.0.CR1 Reporter: jaikiran pai Fix For: 7.1.0.Alpha1 The error reporting in 7.0.0.CR1 for deployment failures due to missing dependencies is very complex and almost cannot be understood. Here are a couple of examples: http://community.jboss.org/message/612943#612943 http://community.jboss.org/message/612555#612555 This needs to be improved in later versions. I'm marking this as "Fix Version" 7.1.0.Alpha1 because I guess this isn't an easy change to incorporate in 7.0.0.Final. If it's possible to get this in for 7.0.0.Final then please change it accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1150) Asynchronous logging doesn't work.

by Andrig Miller (JIRA)

Asynchronous logging doesn't work. ---------------------------------- Key: AS7-1150 URL: https://issues.jboss.org/browse/AS7-1150 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.CR1 Reporter: Andrig Miller Priority: Critical Fix For: 7.0.0.Final Asynchronous logging writes nothing to the server.log. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBLOGGING-67) ASYNC logging logs nothing to the server.log

by Andrig Miller (JIRA)

ASYNC logging logs nothing to the server.log -------------------------------------------- Key: JBLOGGING-67 URL: https://issues.jboss.org/browse/JBLOGGING-67 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR1 Reporter: Andrig Miller Assignee: David Lloyd Priority: Critical Fix For: 3.0.0.CR2 I configured AS 7 CR 1 to use Asynchronous logging as that release had the fix in it to have it parse the configuration correctly, but nothing ever gets written to the server.log. My configuration is as follows: <subsystem xmlns="urn:jboss:domain:logging:1.0"> <async-handler name="ASYNC"> <level name="INFO"/> <queue-length value="1024"/> <overflow-action value="BLOCK"/> <subhandlers> <handler name="FILE"/> </subhandlers> </async-handler> <periodic-rotating-file-handler name="FILE" autoflush="true"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> </periodic-rotating-file-handler> <logger category="com.arjuna"> <level name="WARN"/> </logger> <logger category="org.apache.tomcat.util.modeler"> <level name="WARN"/> </logger> <logger category="sun.rmi"> <level name="WARN"/> </logger> <root-logger> <level name="INFO"/> <handlers> <handler name="ASYNC"/> </handlers> </root-logger> </subsystem> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1148) After startup and shutdown of the AS 7 CR 1 release, the async-handler configuration gets overwritten with improper element (subhandlers are changed to handlers), and it won't start again with editing the configuration.

by Andrig Miller (JIRA)

After startup and shutdown of the AS 7 CR 1 release, the async-handler configuration gets overwritten with improper element (subhandlers are changed to handlers), and it won't start again with editing the configuration. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-1148 URL: https://issues.jboss.org/browse/AS7-1148 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Andrig Miller Priority: Critical Fix For: 7.0.0.Final I created a configuration to use asynchronous logging in standalone-ha.xml, and after successfully starting the server, running a test, and shutting it down, I could no longer restart the server without a parse error in standalone-ha.xml. What is happening, is the file is being rewritten, and it is replacing the subhandlers element with a handlers element which is incorrect. So, my configuration, that looks like this when I start the server: <subsystem xmlns="urn:jboss:domain:logging:1.0"> <async-handler name="ASYNC"> <level name="INFO"/> <queue-length value="1024"/> <overflow-action value="BLOCK"/> <subhandlers> <handler name="FILE"/> </subhandlers> </async-handler> <periodic-rotating-file-handler name="FILE" autoflush="true"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> </periodic-rotating-file-handler> <logger category="com.arjuna"> <level name="WARN"/> </logger> <logger category="org.apache.tomcat.util.modeler"> <level name="WARN"/> </logger> <logger category="sun.rmi"> <level name="WARN"/> </logger> <root-logger> <level name="INFO"/> <handlers> <handler name="ASYNC"/> </handlers> </root-logger> </subsystem> ends up looking like this: <subsystem xmlns="urn:jboss:domain:logging:1.0"> <async-handler name="ASYNC"> <level name="INFO"/> <queue-length value="1024"/> <overflow-action value="BLOCK"/> <handlers> <handler name="FILE"/> </handlers> </async-handler> <periodic-rotating-file-handler name="FILE" autoflush="true"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> </periodic-rotating-file-handler> <logger category="com.arjuna"> <level name="WARN"/> </logger> <logger category="org.apache.tomcat.util.modeler"> <level name="WARN"/> </logger> <logger category="sun.rmi"> <level name="WARN"/> </logger> <root-logger> <level name="INFO"/> <handlers> <handler name="ASYNC"/> </handlers> </root-logger> </subsystem> Which is wrong and fails parsing, which prevents the server from starting again, unless I hand edit the file again to correct it. -- 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

[JBoss JIRA] Created: (AS7-1145) Composite operation with only one member fails

by Heiko Rupp (JIRA)

Composite operation with only one member fails ---------------------------------------------- Key: AS7-1145 URL: https://issues.jboss.org/browse/AS7-1145 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Heiko Rupp Priority: Critical I am trying to issue /deployment=foo:add as one step within a composite operation. When the composite operation has more than one member, this works. If it only has this one member operation, it fails with {"outcome":"failed","failure-description":"No handler for operation add at address [(\"deployment\" => \"test.war\")]","rolled-back":true} The failing upload test is in testUploadComposite2 - while all other combinations in that test class work. http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=blob;f=modules/plugins/j... The code in question used to work for a long time - I suspect the new-controller work to have broken it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1187) parsing server paths fails

by Emanuel Muckenhuber (JIRA)

parsing server paths fails -------------------------- Key: AS7-1187 URL: https://issues.jboss.org/browse/AS7-1187 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.CR1 Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 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 July 2011