January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3341) Upgrade Infinispan to 5.1.0.CR4

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3341: --------------------------------- Summary: Upgrade Infinispan to 5.1.0.CR4 Key: AS7-3341 URL: https://issues.jboss.org/browse/AS7-3341 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.0.Final -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-809) Convert modules to use JBoss Logging and message bundles

by James Perkins (JIRA)

Convert modules to use JBoss Logging and message bundles -------------------------------------------------------- Key: AS7-809 URL: https://issues.jboss.org/browse/AS7-809 Project: Application Server 7 Issue Type: Task Reporter: James Perkins Assignee: James Perkins Fix For: 7.0.0.CR1 Use JBoss Logging 3 to create annotated interfaces for messages and logging. Also include the tooling to generate the concrete classes at compile time for the interfaces. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
6
0 / 0

[JBoss JIRA] (AS7-3396) org.w3c.dom.html.HTMLDOMImplementation in both jython-standalone-2.5.2.jar , xercesImpl-2.9.1-jbossas-1.jar

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3396: --------------------------------- Summary: org.w3c.dom.html.HTMLDOMImplementation in both jython-standalone-2.5.2.jar , xercesImpl-2.9.1-jbossas-1.jar Key: AS7-3396 URL: https://issues.jboss.org/browse/AS7-3396 Project: Application Server 7 Issue Type: Quality Risk Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-333) Context is lost if a service fails to start for a 'random' reason

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-333?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-333: --------------------------------- Component/s: Domain Management > Context is lost if a service fails to start for a 'random' reason > ----------------------------------------------------------------- > > Key: AS7-333 > URL: https://issues.jboss.org/browse/AS7-333 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Carlo de Wolf > Assignee: David Lloyd > Priority: Minor > Fix For: 7.1.0.Final > > > The error message only contains "Failed to start service" it would be nice if the optional causing message is also appended. > {noformat} > 13:58:53,058 INFO [org.jboss.as.server] (MSC service thread 1-9) Service status report > Services which failed to start: > service jboss.deployment.unit."welcome.war": org.jboss.msc.service.StartException in service jboss.deployment.unit."welcome.war": Failed to start service > {noformat} > https://github.com/jbossas/jboss-msc/blob/1.0.0.Beta8/src/main/java/org/j... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3394) resteasy-jaxrs-2.3.0.GA.jar and async-http-servlet-3.0-2.3.0.GA.jar both define org.jboss.resteasy.plugins.server.servlet.* classes.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3394: --------------------------------- Summary: resteasy-jaxrs-2.3.0.GA.jar and async-http-servlet-3.0-2.3.0.GA.jar both define org.jboss.resteasy.plugins.server.servlet.* classes. Key: AS7-3394 URL: https://issues.jboss.org/browse/AS7-3394 Project: Application Server 7 Issue Type: Quality Risk Reporter: Ondrej Zizka org.jboss.resteasy.plugins.server.servlet.ConfigurationBootstrap resteasy-jaxrs-2.3.0.GA.jar org.jboss.resteasy.plugins.server.servlet.Filter30Dispatcher async-http-servlet-3.0-2.3.0.GA.jar org.jboss.resteasy.plugins.server.servlet.FilterBootstrap resteasy-jaxrs-2.3.0.GA.jar ... org.jboss.resteasy.plugins.server.servlet.ResteasyContextParameters resteasy-jaxrs-2.3.0.GA.jar org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest async-http-servlet-3.0-2.3.0.GA.jar org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$1 async-http-servlet-3.0-2.3.0.GA.jar org.jboss.resteasy.plugins.server.servlet.ServletBootstrap resteasy-jaxrs-2.3.0.GA.jar org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher resteasy-jaxrs-2.3.0.GA.jar 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

12 years, 8 months

1
1
0 / 0

[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

12 years, 8 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

12 years, 8 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

12 years, 8 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

12 years, 8 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

12 years, 8 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 January 2012