January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8383) enable xml deployments

by Alexey Loubyansky (JIRA)

enable xml deployments ---------------------- Key: JBAS-8383 URL: https://jira.jboss.org/browse/JBAS-8383 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 At the moment deployments in the domain/standalone are expected to be zip archives. -- 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, 3 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8334) error handling during service deployment

by Alexey Loubyansky (JIRA)

error handling during service deployment ---------------------------------------- Key: JBAS-8334 URL: https://jira.jboss.org/browse/JBAS-8334 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployers Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Errors thrown during service deployment should be properly handled and logged. This task is a main/general one. Each deployment error scenario will be added as a subtask of this one. -- 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, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8335) handling of deployment failed to be added to the MSC batch

by Alexey Loubyansky (JIRA)

handling of deployment failed to be added to the MSC batch ---------------------------------------------------------- Key: JBAS-8335 URL: https://jira.jboss.org/browse/JBAS-8335 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 A deployment can fail to be added to the MSC batch. For example, a service may be attempted to be defined which already exists in the batch (in fact, at present this is the only possible error outside of outright code bugs). In this event, the correct thing to do is to log the error and continue. -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] (AS7-3392) Some org.apache.xml.resolver classes in both jaxb-xjc-2.2.jar , xml-resolver-1.2.jar

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3392: --------------------------------- Summary: Some org.apache.xml.resolver classes in both jaxb-xjc-2.2.jar , xml-resolver-1.2.jar Key: AS7-3392 URL: https://issues.jboss.org/browse/AS7-3392 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Paul Gier These classes are in both modules: org.apache.xml.resolver.Catalog org.apache.xml.resolver.CatalogEntry org.apache.xml.resolver.CatalogException org.apache.xml.resolver.CatalogManager org.apache.xml.resolver.Resolver org.apache.xml.resolver.Version org.apache.xml.resolver.apps.XParseError org.apache.xml.resolver.apps.resolver org.apache.xml.resolver.apps.xparse org.apache.xml.resolver.apps.xread org.apache.xml.resolver.helpers.Debug org.apache.xml.resolver.helpers.Namespaces org.apache.xml.resolver.helpers.PublicId org.apache.xml.resolver.readers.CatalogReader org.apache.xml.resolver.readers.DOMCatalogParser org.apache.xml.resolver.readers.DOMCatalogReader org.apache.xml.resolver.readers.ExtendedXMLCatalogReader org.apache.xml.resolver.readers.OASISXMLCatalogReader org.apache.xml.resolver.readers.SAXCatalogParser org.apache.xml.resolver.readers.SAXCatalogReader org.apache.xml.resolver.readers.SAXParserHandler org.apache.xml.resolver.readers.TR9401CatalogReader org.apache.xml.resolver.readers.TextCatalogReader org.apache.xml.resolver.readers.XCatalogReader org.apache.xml.resolver.tools.CatalogResolver org.apache.xml.resolver.tools.ResolvingParser org.apache.xml.resolver.tools.ResolvingXMLFilter org.apache.xml.resolver.tools.ResolvingXMLReader These are only in xml-resolver: org.apache.xml.resolver.helpers.BootstrapResolver org.apache.xml.resolver.helpers.FileURL See https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3385) "xa-datasource-properties" "Instance" property validation does not allow empty value

by ivan khoosty (JIRA)

ivan khoosty created AS7-3385: --------------------------------- Summary: "xa-datasource-properties" "Instance" property validation does not allow empty value Key: AS7-3385 URL: https://issues.jboss.org/browse/AS7-3385 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.CR1b Reporter: ivan khoosty Assignee: Jesper Pedersen Priority: Minor we have this property parametrised, <xa-datasource-property name="Instance"> ${sql.instance} </xa-datasource-property> so when ${sql.instance} is set to empty/blank/"", the startup falls over with the following error 17:55:00,435 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 26) Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("xa-data-source" => "ImageGenAppsDS"), ("xa-datasource-properties" => "Instance") ]) - failure description: "JBAS014704: '' is an invalid value for parameter value. Values must have a minimum length of 1 characters" This is a change of behaviour from 7.0.2.Final, and seems incorrect according to msdn references. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3320) extend deploy -l to include status and server groups

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3320: -------------------------------------- Summary: extend deploy -l to include status and server groups Key: AS7-3320 URL: https://issues.jboss.org/browse/AS7-3320 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final It'd be useful to see whether the deployment is enabled, which server groups it is deployed to, etc. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3321) data-source command should not use --jndi-name as the identifying property

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3321: -------------------------------------- Summary: data-source command should not use --jndi-name as the identifying property Key: AS7-3321 URL: https://issues.jboss.org/browse/AS7-3321 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final The management model of the datasource has changed. jndi-name is no longer read-only and doesn't necessarily match the name of the datasource in the node address. So, it can't be used as the identifying 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, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3338) Deployment of a WAR archive with malformed web.xml ends up in undefined state

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3338: ------------------------------------- Summary: Deployment of a WAR archive with malformed web.xml ends up in undefined state Key: AS7-3338 URL: https://issues.jboss.org/browse/AS7-3338 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Web Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Brian Stansberry Deployment of a WAR archive with malformed web.xml ends up in undefined state. The undeploy operation of the malformed archive is triggered however it is rolled back. As a result, the deployment is not available however it is listed in the configuration model. 15:05:15,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."deployment2.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."deployment2.war".PARSE: Failed to process phase PARSE of deployment "deployment2.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_b147-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_b147-icedtea] at java.lang.Thread.run(Thread.java:722) [:1.7.0_b147-icedtea] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/deployment2.war/WEB-INF/web.xml" at [1,1] at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:112) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more 15:05:16,001 INFO [org.jboss.as.server] (management-handler-threads - 3) JBAS015856: Undeploy of deployment "deployment2.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"deployment2.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"deployment2.war\".PARSE: Failed to process phase PARSE of deployment \"deployment2.war\""}} 15:05:16,005 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) Stopped deployment deployment2.war in 3ms 15:05:16,006 INFO [org.jboss.as.controller] (management-handler-threads - 3) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."deployment2.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."deployment2.war".PARSE: Failed to process phase PARSE of deployment "deployment2.war" -- 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, 3 months

3
9
0 / 0

[JBoss JIRA] (AS7-3319) failed deployment remains in the repository

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3319: -------------------------------------- Summary: failed deployment remains in the repository Key: AS7-3319 URL: https://issues.jboss.org/browse/AS7-3319 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.CR1b Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final If a deployment passed into the deploy command fails to deploy, it still appears in the list of deployments as disabled. This doesn't happen if the same deploy command is executed in the batch mode though. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3382) Allow repository to resolve local modules/bundles

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3382: ----------------------------------- Summary: Allow repository to resolve local modules/bundles Key: AS7-3382 URL: https://issues.jboss.org/browse/AS7-3382 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Final With the OSGi Repository implementation in place it is possible to provision the system with bundles from a remote maven repository (i.e. nexus). An optimization would be to fetch the artefacts from the local 'modules' or 'bundles' directory in the AS7 distribution. These configured capabilities could be removed {code}  <capability name="org.jboss.netty" startlevel="2"/> <capability name="org.projectodd.stilts" startlevel="2"/> {code} The SimpleStompletTestCase could use the Repository API to provision these bundles on demand. -- 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, 3 months

1
0
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 January 2012