December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2913) Failed to remove long running pool config

by Heiko Braun (Created) (JIRA)

Failed to remove long running pool config ----------------------------------------- Key: AS7-2913 URL: https://issues.jboss.org/browse/AS7-2913 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.CR1 Removing a long-running pool config yields a server side exception: {noformat} [INFO] { [INFO] "address" => [ [INFO] ("subsystem" => "jca"), [INFO] ("workmanager" => "custom"), [INFO] ("long-running-threads" => "long-running-pool") [INFO] ], [INFO] "operation" => "remove" [INFO] } {noformat} {noformat} Caused by: java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.asProperty(ModelValue.java:96) [jboss-dmr-1.1.1.Final.jar:] at org.jboss.dmr.ObjectModelValue.asProperty(ObjectModelValue.java:151) [jboss-dmr-1.1.1.Final.jar:] at org.jboss.dmr.ModelNode.asProperty(ModelNode.java:348) [jboss-dmr-1.1.1.Final.jar:] at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.writeWorkManagers(JcaExtension.java:242) at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.writeContent(JcaExtension.java:186) at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.writeContent(JcaExtension.java:173) at org.jboss.as.server.parsing.StandaloneXml.writeServerProfile(StandaloneXml.java:933) at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:851) at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:96) at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:78) [staxmapper-1.0.0.Final.jar:] at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:73) [staxmapper-1.0.0.Final.jar:] at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:102) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] {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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-2879) Failed to marshal JCA poll config

by Heiko Braun (Created) (JIRA)

Failed to marshal JCA poll config --------------------------------- Key: AS7-2879 URL: https://issues.jboss.org/browse/AS7-2879 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.CR1 {noformat} [INFO] { [INFO] "name" => "custom2", [INFO] "blocking" => false, [INFO] "max-threads" => { [INFO] "count" => 2, [INFO] "per-cpu" => 1 [INFO] }, [INFO] "allow-core-timeout" => false, [INFO] "queue-length" => { [INFO] "count" => 2, [INFO] "per-cpu" => 1 [INFO] }, [INFO] "address" => [ [INFO] ("subsystem" => "jca"), [INFO] ("workmanager" => "default"), [INFO] ("short-running-threads" => "custom2") [INFO] ], [INFO] "operation" => "add" [INFO] } {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, 5 months

3
2
0 / 0

[JBoss JIRA] (AS7-2911) NPE in EJB3 subsystem views

by Heiko Braun (Created) (JIRA)

NPE in EJB3 subsystem views --------------------------- Key: AS7-2911 URL: https://issues.jboss.org/browse/AS7-2911 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: David Bosschaert Fix For: 7.1.0.CR1 {noformat} [ERROR] java.lang.NullPointerException [ERROR] at com.google.gwt.view.client.ListDataProvider$ListWrapper.<init>(ListDataProvider.java:202) [ERROR] at com.google.gwt.view.client.ListDataProvider.setList(ListDataProvider.java:517) [ERROR] at org.jboss.as.console.client.shared.subsys.ejb3.EESubsystemView.updateFrom(EESubsystemView.java:156) [ERROR] at org.jboss.as.console.client.shared.subsys.ejb3.EEPresenter$2.onSuccess(EEPresenter.java:200) [ERROR] at org.jboss.as.console.client.shared.subsys.ejb3.EEPresenter$2.onSuccess(EEPresenter.java:1) {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, 5 months

3
2
0 / 0

[JBoss JIRA] (AS7-2854) JSR88 does not validate deployment descriptors

by Thomas Diesler (Created) (JIRA)

JSR88 does not validate deployment descriptors ---------------------------------------------- Key: AS7-2854 URL: https://issues.jboss.org/browse/AS7-2854 Project: Application Server 7 Issue Type: Bug Components: JSR-88 Reporter: Thomas Diesler Java EE Platform Specification EE8.5: The deployment tools for Java EE containers must validate the deployment descriptors against the Java EE deployment descriptor schemas or DTDs that correspond to the deployment descriptors being processed. The appropriate schema or DTD is chosen by analyzing the deployment descriptor to determine which version it claims to conform to. Validation errors must cause an error to be reported to the Deployer. -- 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, 5 months

7
12
0 / 0

[JBoss JIRA] (AS7-2539) Class-Path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR are not supported

by Abhi S (Created) (JIRA)

Class-Path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR are not supported ---------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-2539 URL: https://issues.jboss.org/browse/AS7-2539 Project: Application Server 7 Issue Type: Bug Components: Deployment, Modules Affects Versions: 7.1.0.Alpha1 Environment: Windows 7 64-bit Reporter: Abhi S Assignee: Thomas Diesler Attachments: jee-app.ear According to the JEE 6 specification, section EE.8.2.1 (Bundled Libraries), Class-path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR could be used by the application developer to add these directories to the classpath of the sub-module. However, this functionality has not yet been implemented in the JBoss AS7.1 (alpha-2 nightly build). *Relevant JEE 6 spec, section EE.8.2.1, quotes:* _Class-Path: list-of-jar-files-or-directories-separated-by-spaces_ _Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension._ This support for this functionality is *required* by the specification for the JBoss AS7.1 to be fully JEE 6 compliant. *Side note:* This functionality is supported in JBoss 5.1, Weblogic, and WebSphere. -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-1988) Please remove zipeinit.jar from tests

by Marek Goldmann (JIRA)

Please remove zipeinit.jar from tests ------------------------------------- Key: AS7-1988 URL: https://issues.jboss.org/browse/AS7-1988 Project: Application Server 7 Issue Type: Task Components: VFS Reporter: Marek Goldmann Assignee: John Bailey This file contains binary files and the license of it is unclear. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1568) MDB component doesn't setup the correct dependencies on the RA service

by jaikiran pai (JIRA)

MDB component doesn't setup the correct dependencies on the RA service ---------------------------------------------------------------------- Key: AS7-1568 URL: https://issues.jboss.org/browse/AS7-1568 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.1.Final Reporter: jaikiran pai Assignee: jaikiran pai A user has reported that he runs into {code} Caused by: java.lang.IllegalStateException: No resource-adapter has been specified for MessageDrivenComponent MqServiceMessageBean at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:171) {code} when he uses a custom RA which is deployed as an deployment (instead of via the subsystem configuration file). Looking at the code, we don't correctly setup the dependencies between the MDB component create service and the RA service, which can lead to issues like these. See referenced thread for more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
3
0 / 0

[JBoss JIRA] (AS7-2783) servlet/http errors reports the server is 7.0.3

by Max Rydahl Andersen (Created) (JIRA)

servlet/http errors reports the server is 7.0.3 ----------------------------------------------- Key: AS7-2783 URL: https://issues.jboss.org/browse/AS7-2783 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Beta1 Reporter: Max Rydahl Andersen Assignee: Remy Maucherat Start AS 7.1.0.Beta1 goto a page that does not exist, i.e. http://localhost:8080/tesla Title says "JBoss Web/7.0.3.Final" Should say "JBoss Web/7.1.0.Beta1" I assume ? -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] (AS7-2904) Cannot execute composite operations on a slave HC

by Brian Stansberry (Created) (JIRA)

Cannot execute composite operations on a slave HC ------------------------------------------------- Key: AS7-2904 URL: https://issues.jboss.org/browse/AS7-2904 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.0.CR1 Trying to execute a composite op on a slave HC results in: { "outcome" => "failed", "failure-description" => "Operation composite for address [] can only handled by the master Domain Controller; this host is not the master Domain Controller", "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, 5 months

2
1
0 / 0

[JBoss JIRA] (AS7-2905) Reduce logging level on non-OFE management API user errors

by Brian Stansberry (Created) (JIRA)

Reduce logging level on non-OFE management API user errors ----------------------------------------------------------- Key: AS7-2905 URL: https://issues.jboss.org/browse/AS7-2905 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.CR1 A number of methods in OperationContext and similar places throw runtime exceptions when error conditions are detected that are really due to user mistakes (e.g. trying to add a resource that's already present.) These are caught and logged at ERROR. It would be better if OperationFailedException were thrown, since those are only logged at DEBUG -- logging client request errors at ERROR in the server log is noisy and will anger admins. Unfortunately, OFE is a checked exception, so we can't throw it without making an incompatible API change that may break subsystems. Solution is to create an OperationFailedRuntimeException and throw that. The logic that catches and handles OFE will do the same thing for OFRE. -- 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, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011