October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2236) A resource-env-ref without injection targets must be bindable

by Carlo de Wolf (Created) (JIRA)

A resource-env-ref without injection targets must be bindable ------------------------------------------------------------- Key: AS7-2236 URL: https://issues.jboss.org/browse/AS7-2236 Project: Application Server 7 Issue Type: Bug Components: EE Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical {noformat} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not determine type for resource-env-ref java:comp/env/dog at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.getResourceEnvRefEntries(ResourceReferenceProcessor.java:86) at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.processDescriptorEntries(ResourceReferenceProcessor.java:55) at org.jboss.as.ee.component.deployers.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:103) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] ... 5 more {noformat} -- 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

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1410) Expose runtime OSGi management configuration through console

by David Bosschaert (JIRA)

Expose runtime OSGi management configuration through console ------------------------------------------------------------ Key: AS7-1410 URL: https://issues.jboss.org/browse/AS7-1410 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: David Bosschaert Assignee: David Bosschaert Fix For: 7.1.0.CR1 Bundle runtime management should be exposed through the console. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-769) Expose transaction manager though web management interface

by Heiko Braun (JIRA)

Expose transaction manager though web management interface ---------------------------------------------------------- Key: AS7-769 URL: https://issues.jboss.org/browse/AS7-769 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, Transactions Reporter: Heiko Braun Assignee: Jason Greene -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
11
0 / 0

[JBoss JIRA] Created: (AS7-1782) Provide management use cases and operations for the transaction subsystem

by Heiko Braun (JIRA)

Provide management use cases and operations for the transaction subsystem ------------------------------------------------------------------------- Key: AS7-1782 URL: https://issues.jboss.org/browse/AS7-1782 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Reporter: Heiko Braun Assignee: Jonathan Halliday Fix For: 7.1.0.Beta1 I cannot identify the use cases not the operation when looking at the current management exposure: {noformat} [standalone@localhost:9999 /] /subsystem=transactions:read-resource(recursive=true) { "outcome" => "success", "result" => { "coordinator-environment" => { "enable-statistics" => undefined, "enable-tsm-status" => undefined, "default-timeout" => 300 }, "core-environment" => { "process-id" => {"uuid" => "uuid"}, "node-identifier" => undefined, "relative-to" => undefined, "path" => undefined }, "object-store" => { "relative-to" => undefined, "path" => undefined }, "recovery-environment" => { "socket-binding" => "txn-recovery-environment", "status-socket-binding" => "txn-status-manager", "recovery-listener" => undefined } } } [standalone@localhost:9999 /] /subsystem=transactions:read-operation- read-operation-description read-operation-names [standalone@localhost:9999 /] /subsystem=transactions:read-operation-names { "outcome" => "success", "result" => [ "add", "read-attribute", "read-children-names", "read-children-resources", "read-children-types", "read-operation-description", "read-operation-names", "read-resource", "read-resource-description", "validate-address", "write-attribute" ] } {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
8
0 / 0

[JBoss JIRA] (AS7-2235) Framework properties not writable

by Thomas Diesler (Created) (JIRA)

Framework properties not writable --------------------------------- Key: AS7-2235 URL: https://issues.jboss.org/browse/AS7-2235 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Beta1 [standalone@localhost:9999 /] /subsystem=osgi/property=org.osgi.framework.startlevel.beginning:write-attribute(name=value,value=2) { "outcome" => "failed", "failure-description" => "Attribute value is not writeable", "rolled-back" => true } -- 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

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-2224) restart-required value only gets transformed for read-write attributes

by David Bosschaert (Created) (JIRA)

restart-required value only gets transformed for read-write attributes ---------------------------------------------------------------------- Key: AS7-2224 URL: https://issues.jboss.org/browse/AS7-2224 Project: Application Server 7 Issue Type: Bug Components: Server Reporter: David Bosschaert Assignee: Jason Greene Looking at the output from read-resource-description I noticed that the value of restart-required sometimes is capitalized and in other cases it's not. E.g. take the following subsystem: {code}[standalone@localhost:9999 subsystem=osgi] :read-resource-description(recursive=true) { "outcome" => "success", "result" => { "description" => "The OSGi subsystem configuration.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:osgi:1.0", "attributes" => { "activation" => { "description" => "Activation flag for the OSGi subsystem. Possible values: lazy, eager.", "type" => STRING, "default" => "LAZY", "access-type" => "read-write", "restart-required" => "no-services", "storage" => "configuration" }, "startlevel" => { "description" => "The current Start Level of the OSGi Framework. Changing this value will change the start level of the Framework accordingly. ", "type" => INT, "access-type" => "read-write", "restart-required" => "no-services", "storage" => "runtime" } }, "children" => { "configuration" => { "description" => "A Configuration Admin Service entry. The identity of the entry defines the PID (Persistent Identifier) that the entry is associated with.", "model-description" => {"*" => { "description" => "A Configuration Admin Service entry. The identity of the entry defines the PID (Persistent Identifier) that the entry is associated with.", "attributes" => {"entries" => { "description" => "The list of configuration entries.", "required" => true, "type" => LIST, "value-type" => UNDEFINED, "access-type" => "read-only", "restart-required" => "RESTART_NONE", "storage" => "configuration" }} }} }, ...{code} You can see that for the same AttributeAccess.Flag.RESTART_NONE value in some cases it's transformed into 'no-services' and in other cases it's left the way it is. I isolated this issue to org.jboss.as.controller.operations.global.GlobalOperationHandlers (~line 830) and noticed that only in the case of a read-write attribute this transformation is applied. That seems incorrect... I'm wondering why do we do this translation at all and not simply return the Flag.toString()? -- 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

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1912) Fix or remove @Ignore in EnterpriseDeploymentTestCase

by Thomas Diesler (JIRA)

Fix or remove @Ignore in EnterpriseDeploymentTestCase ----------------------------------------------------- Key: AS7-1912 URL: https://issues.jboss.org/browse/AS7-1912 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] (AS7-2165) Thread context ClassLoader set to unexpected value

by Tim Pesce (Created) (JIRA)

Thread context ClassLoader set to unexpected value -------------------------------------------------- Key: AS7-2165 URL: https://issues.jboss.org/browse/AS7-2165 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.0.2.Final Environment: Java 1.6.0_26, Mac OS 10.6.8 Reporter: Tim Pesce Assignee: Thomas Diesler I am using library code in a BundleActivator that tries to load resources via ClassLoader. The logic in the library looks something like this: # if thread context ClassLoader exists use it # else use ClassLoader for this class The thread context ClassLoader differs from the class ClassLoader. The resources packaged in my bundle are not available to the thread context ClassLoader, but they are available to the class ClassLoader. In 7.0.1 there was no thread context ClassLoader, so the library code used the class ClassLoader and correctly loaded the resources. Here's what toString on the thread context ClassLoader shows: {quote} ModuleClassLoader for Module "org.jboss.as.osgi:main" from local module loader @67d225a7 (roots: /Users/tpesce/Developer/jboss-as-7.0.2.Final/modules) {quote} Here's the toString ont he class ClassLoader: {quote} HostBundleClassLoader for Module "deployment.jboss.osgi.bug:1.0.0" from Service Module Loader {quote} -- 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

12 years, 11 months

8
11
0 / 0

[JBoss JIRA] Created: (AS7-1039) AS fails to boot if hostname is not pingable

by Misty Stanley-Jones (JIRA)

AS fails to boot if hostname is not pingable -------------------------------------------- Key: AS7-1039 URL: https://issues.jboss.org/browse/AS7-1039 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: Open To Community Environment: Fedora 15 Reporter: Misty Stanley-Jones If hostname is not pingable (such as a made-up value like "cheezel" or a FQDN like "dhcp-111-bne.redhat.com"), the AS fails to start in domain mode, with a bindException. If I change the hostname to "localhost", the AS starts fine. AS starts in standalone mode regardless. See the error at http://fpaste.org/xawH/. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

7
9
0 / 0

[JBoss JIRA] (JBWEB-215) CLONE - More than one JSESSIONID cookie headers set in JBoss Web

by Nagai Eiichi (Created) (JIRA)

CLONE - More than one JSESSIONID cookie headers set in JBoss Web ---------------------------------------------------------------- Key: JBWEB-215 URL: https://issues.jboss.org/browse/JBWEB-215 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-2.1.11.GA Reporter: Nagai Eiichi Assignee: Remy Maucherat More than one JSESSIONID cookie headers set if execute following JSP. <% session.invalidate(); session = request.getSession(); session.invalidate(); session = request.getSession(); %> This issue has been reported from Bug 49158[1] in tomcat. [1] Bug 49158 - More than one JSESSIONID cookie headers set https://issues.apache.org/bugzilla/show_bug.cgi?id=49158 http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/catalin... http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/catalin... I guess that same fix is required in JBoss Web. -- 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

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011