July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-861) resource-description for root-logger in subsystem=looging is incomplete

by Heiko Rupp (JIRA)

resource-description for root-logger in subsystem=looging is incomplete ----------------------------------------------------------------------- Key: AS7-861 URL: https://issues.jboss.org/browse/AS7-861 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp Assignee: Jason Greene [domain@localhost:9999 subsystem=logging] :read-resource-description(recursive=true) { "outcome" => "success", "result" => { "description" => "The configuration of the logging subsystem.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:logging:1.0", "operations" => undefined, "children" => { "root-logger" => {"description" => "Defines the root logger for this log context."}, and [domain@localhost:9999 subsystem=logging] :read-resource(recursive=true) { "outcome" => "success", "result" => { "root-logger" => { "level" => "INFO", "handlers" => [ "CONSOLE", "FILE" ] } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
7
0 / 0

[JBoss JIRA] Created: (AS7-1004) "failed to resolve interface default" if default interface inet-address value set to a local address other than 127.0.0.1

by Marek Schmidt (JIRA)

"failed to resolve interface default" if default interface inet-address value set to a local address other than 127.0.0.1 ------------------------------------------------------------------------------------------------------------------------- Key: AS7-1004 URL: https://issues.jboss.org/browse/AS7-1004 Project: Application Server 7 Issue Type: Bug Environment: Fedora 15, Sun JDK 1.6.0_24-b07, jboss-7.0.0.Beta4-SNAPSHOT-1194, standalone Reporter: Marek Schmidt Setting the "default" interface to, e.g.: {code} <interface name="default"> <inet-address value="127.0.1.1"/> </interface> {code} throws the following exception at startup, even if the 127.0.1.1 address is set up in /etc/hosts (not that it should matter) I have noticed there exists a loopback-address element which seems to work, but I fail to see why this one shouldn't. {quote} 12:06:18,660 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.default: org.jboss.msc.service.StartException in service jboss.network.default: failed to resolve interface default at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:106) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8132) Utility to report on differences in domain configuration between domains

by Brian Stansberry (JIRA)

Utility to report on differences in domain configuration between domains ------------------------------------------------------------------------ Key: JBAS-8132 URL: https://jira.jboss.org/browse/JBAS-8132 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: One of the motivations for the domain controller was to help customers manage drift in their JBoss configurations. Because of operational concerns, specifically datacenter isolation, some customers expect to need to run multiple identical domain controllers. They would then still be faced with drift across domain controllers. A utility to detect this drift would be helpful. -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-851) Add some form of :whoami operation

by Darran Lofthouse (JIRA)

Add some form of :whoami operation ---------------------------------- Key: AS7-851 URL: https://issues.jboss.org/browse/AS7-851 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Jason Greene Fix For: 7.0.0.CR1 Connectivity to the server can make use of authentication automatically handled by either the web broswer or in some cases possibly a CLI using a local Kerberos ticket. This issue is to add a :whoami operation to verify who the connection is running as so the client can see they are connected as the expected user. Later this may also be expanded to make it possible to query what a client can actually do so operations a client can not perform can be potentially hidden / masked. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBEE-45) Release JACC 1.1 APIs built with JDK 1.4

by Shelly McGowan (JIRA)

Release JACC 1.1 APIs built with JDK 1.4 ---------------------------------------- Key: JBEE-45 URL: https://jira.jboss.org/jira/browse/JBEE-45 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 To replace this: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-jacc-api_JDK4/1... which contains a servlet snapshot Needed by Hibernate -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBEE-76) Create JavaEE API aggregate for use with JBoss AS 7

by Shelly McGowan (JIRA)

Create JavaEE API aggregate for use with JBoss AS 7 --------------------------------------------------- Key: JBEE-76 URL: https://issues.jboss.org/browse/JBEE-76 Project: JBoss JavaEE APIs Issue Type: Feature Request Components: javaee6_specs_bom, javaee_6.0_spec Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 2.0.0-Beta1-javaee_6.0, 2.0.0-Beta1-javaee6-specs-bom Started Version 2.0.x series for use with JBoss AS 7. These APIs are compatible but the versions in the specs bom and aggregate align with the versions in the AS 7 distribution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1358) UserTransaction not available to non-EE threads

by Chris Lowe (JIRA)

UserTransaction not available to non-EE threads ----------------------------------------------- Key: AS7-1358 URL: https://issues.jboss.org/browse/AS7-1358 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Affects Versions: 7.0.0.Final Reporter: Chris Lowe Assignee: Jonathan Halliday JBoss Seam offers Asynchronous behaviour for non-EJB environments using a Quartz dispatcher. Asynchronous behaviour may also make use of Seam's @Transactional marker to demarcate tx boundaries. Since testing one of our applications in AS7 I noticed Seam "could not discover transaction status" error messages reported as our application ran async sections of code. Examining the Seam code, I could see that Seam would make two attempts to access a JNDI UserTransaction resource: 1 - context.lookup("java:comp/UserTransaction"); If an NameNotFoundException is thrown, then attempt: 2 - context.lookup("UserTransaction"); Under AS6 and below, the latter attempt would succeed. Under AS7 attempts are currently failing. While looking into this issue I came across the following developer discussion which suggests that it might be possible to add a "java:/jboss/UserTransaction" resource: http://lists.jboss.org/pipermail/jboss-as7-dev/2011-June/002298.html Further discussion on my AS7 user forum thread lead to the suggestion that I myself might add this behaviour. I have followed the implementation hints and light testing has been successful (with appropriate mods to Seam to use the new resource name). I aim to perform some more thorough testing on this shortly and submit a patch against this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
8
0 / 0

[JBoss JIRA] Created: (JBAS-8151) Support CRL Validation in the services

by Anil Saldhana (JIRA)

Support CRL Validation in the services -------------------------------------- Key: JBAS-8151 URL: https://jira.jboss.org/browse/JBAS-8151 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.M4 Tomcat connector can do CRL validation (users can download CRL lists from commercial CAs). I would like to see us document our CRL support for the various services. This may force us to write a separate trust manager. Please research. The key here is to document. -- 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, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-8141) Validate the Principal Mapping Framework is configurable/usable for the various services

by Anil Saldhana (JIRA)

Validate the Principal Mapping Framework is configurable/usable for the various services ---------------------------------------------------------------------------------------- Key: JBAS-8141 URL: https://jira.jboss.org/browse/JBAS-8141 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.Final We need to validate that we can use the principal mapping framework with the following services: web, ejb2 and ejb3 -- 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, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8150) Research OCSP support for all services of the JBoss AS

by Anil Saldhana (JIRA)

Research OCSP support for all services of the JBoss AS ------------------------------------------------------ Key: JBAS-8150 URL: https://jira.jboss.org/browse/JBAS-8150 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.Final I think the tomcat connectors have the capabilities to do ocsp. Not completely sure. But it will be good to have a trust manager that can do ocsp. Starting JDK5, there have been numerous x509 enhancements. We need to document (and beef up the services) to utilize ocsp. -- 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, 8 months

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