March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-37) Add support for specifying logger FQCN

by David Lloyd (Created) (JIRA)

Add support for specifying logger FQCN -------------------------------------- Key: LOGTOOL-37 URL: https://issues.jboss.org/browse/LOGTOOL-37 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.CR4 It should be possible to specify in @LogMessage the value to pass as the loggerFqcn, to replace the default (which would be the implementation method's class). In addition, it should be possible to specify an interface parameter to be a @LoggerFQCN, which would set the logger FQCN from that parameter value, overriding the above and the default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (LOGTOOL-33) Validation of message types fails for out-of-order types

by Sanne Grinovero (Created) (JIRA)

Validation of message types fails for out-of-order types -------------------------------------------------------- Key: LOGTOOL-33 URL: https://issues.jboss.org/browse/LOGTOOL-33 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR2 Reporter: Sanne Grinovero Assignee: David Lloyd >From Infinispan: {code}@LogMessage(level = WARN) @Message(value = "Error committing cache view %2$d for cache %1$s", id = 169) void cacheViewCommitFailure(@Cause Exception e, String cacheName, int committedViewId); {code} {code} Log.java:797: Invalid format for 'Error committing cache view %2$d for cache %1$s' with parameters '[33, JBoss]'. java.util.Formatter Error: d != java.lang.String {code} I think the log message is correct, and the validator should not prevent this from being used. I've a test case ready in a pull request I'm sending now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
5
0 / 0

[JBoss JIRA] (LOGTOOL-34) FQCN methods are not completely correct

by David Lloyd (Created) (JIRA)

FQCN methods are not completely correct --------------------------------------- Key: LOGTOOL-34 URL: https://issues.jboss.org/browse/LOGTOOL-34 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd The generated code looks like this: {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] (JASSIST-161) java.lang.ClassFormatException in certain cases with Java 7

by Joao Carvalho (JIRA)

Joao Carvalho created JASSIST-161: ------------------------------------- Summary: java.lang.ClassFormatException in certain cases with Java 7 Key: JASSIST-161 URL: https://issues.jboss.org/browse/JASSIST-161 Project: Javassist Issue Type: Bug Affects Versions: 3.16.1-GA Environment: Oracle Java 7 on Mac OSX Reporter: Joao Carvalho Assignee: Shigeru Chiba -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1617) Create a MC bean handle in the likes of java.ejb.Handle

by Carlo de Wolf (JIRA)

Create a MC bean handle in the likes of java.ejb.Handle ------------------------------------------------------- Key: EJBTHREE-1617 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1617 Project: EJB 3.0 Issue Type: Feature Request Components: common Reporter: Carlo de Wolf Assignee: Ales Justin Priority: Critical Fix For: 1.0.0-CR1 -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] (AS7-4239) JDR ambiguously collects manifest information

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-4239: ---------------------------------- Summary: JDR ambiguously collects manifest information Key: AS7-4239 URL: https://issues.jboss.org/browse/AS7-4239 Project: Application Server 7 Issue Type: Bug Components: JDR Reporter: Jesse Jaggars Assignee: Jesse Jaggars The manifest report generated by JDR does not take into account Manifest files with newlines. This can lead to ambiguous sections of the JDR output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4234) Timeout when uploading large deployment through the console

by Heiko Braun (JIRA)

Heiko Braun created AS7-4234: -------------------------------- Summary: Timeout when uploading large deployment through the console Key: AS7-4234 URL: https://issues.jboss.org/browse/AS7-4234 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.2.Final While adding content through management console. If the upload does not finish in 15-20 seconds it gets stuck and never completes. We verified last night that the CLI works fine for this, so this indeed looks to be some sort of timeout when using the admin console when a deployment has any appreciable size (17MB was the size last night) or the link is slow enough to trigger the timeout. CLI worked fine with that deployment over a home VPN link. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] (AS7-4229) JBoss AS 7.1 w/ an interface configured to bind to <any-address> causes tests to fail w/ the error: "host must not be null"

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/AS7-4229?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved AS7-4229. -------------------------------- Resolution: Out of Date Upgrading to version 1.0.0.M5 of the jboss-javaee-6.0-with-tools BOM resolved this problem. > JBoss AS 7.1 w/ an interface configured to bind to <any-address> causes tests to fail w/ the error: "host must not be null" > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-4229 > URL: https://issues.jboss.org/browse/AS7-4229 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Reporter: Brian Leathem > > Running a the JBoss AS kitchensink quickstart test again a JBoss AS 7.1 server with an interface configured to bind to <any-address> causes the test to fail with the error: "host must not be null". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4229) JBoss AS 7.1 w/ an interface configured to bind to <any-address> causes tests to fail w/ the error: "host must not be null"

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/AS7-4229?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on AS7-4229: ------------------------------------ Looked into the Arquillian version used, which is specified in a BOM: {quote} <groupId>org.jboss.bom</groupId> <artifactId>jboss-javaee-6.0-with-tools</artifactId> <version>1.0.0.M1</version> {quote} available at: https://repository.jboss.org/nexus/content/groups/public/org/jboss/bom/jb... inherits from: https://repository.jboss.org/nexus/content/groups/public/org/jboss/bom/jb... which states: {quote} <version.org.jboss.arquillian>1.0.0.CR7</version.org.jboss.arquillian> <version.org.jboss.as.arquillian.container>7.1.0.CR1b</version.org.jboss.as.arquillian.container> {quote} > JBoss AS 7.1 w/ an interface configured to bind to <any-address> causes tests to fail w/ the error: "host must not be null" > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-4229 > URL: https://issues.jboss.org/browse/AS7-4229 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Reporter: Brian Leathem > > Running a the JBoss AS kitchensink quickstart test again a JBoss AS 7.1 server with an interface configured to bind to <any-address> causes the test to fail with the error: "host must not be null". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3710) Cannot see classes defined by OSGi bootdelegation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3710: ----------------------------------- Summary: Cannot see classes defined by OSGi bootdelegation Key: AS7-3710 URL: https://issues.jboss.org/browse/AS7-3710 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.1.Final I use a javaagent that does bytecode instrumentation. This injected code needs to be able to see its runtime dependency, which is available from the boot classloader. JBoss appears to ignore the "org.osgi.framework.bootdelegation" property -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
7
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 March 2012