February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6587) Use JBoss Logging for resource adapter LogWriter

by Osamu Nagano (JIRA)

[ https://issues.jboss.org/browse/AS7-6587?page=com.atlassian.jira.plugin.s... ] Osamu Nagano commented on AS7-6587: ----------------------------------- Besides the logging system integration, the current stdout log writer is not working properly. It actually outputs nothing. The PrintWriter object should be auto flushed like {{new PrintWriter(System.out, true)}} as a short-term solution. {code:title=https://github.com/jbossas/jboss-as/blob/master/connector/src/main/java/org/jboss/as/connector/services/resourceadapters/deployment/AbstractResourceAdapterDeploymentService.java#L387} @Override protected PrintWriter getLogPrintWriter() { return new PrintWriter(System.out); } {code} > Use JBoss Logging for resource adapter LogWriter > ------------------------------------------------ > > Key: AS7-6587 > URL: https://issues.jboss.org/browse/AS7-6587 > Project: Application Server 7 > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > > Have each resource adapter deployment use JBoss Logging for its LogWriter implementation. > Logging category should include the resource adapter name (eis.rar), and activation id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6603) EAR A auto-start fail with JBAS014777 after EAR B has redeployed, EAR A dependency EAR B.

by pian wang (JIRA)

pian wang created AS7-6603: ------------------------------ Summary: EAR A auto-start fail with JBAS014777 after EAR B has redeployed, EAR A dependency EAR B. Key: AS7-6603 URL: https://issues.jboss.org/browse/AS7-6603 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.1.Final Reporter: pian wang Assignee: David Lloyd EAR A auto-start fail with JBAS014777 after EAR B has redeployed, EAR A dependency EAR B. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6602) Inconsistent output between standalone and domain when invalid command line options is presented

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6602: ------------------------------------- Summary: Inconsistent output between standalone and domain when invalid command line options is presented Key: AS7-6602 URL: https://issues.jboss.org/browse/AS7-6602 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.2.0.Alpha1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.0.Alpha1 Calling [standalone|domain].[sh|bat] with nonsense arguments resulted in the usage message on EAP6.0. The usage message is now presented only for standalone.[sh|bat], but it is missing for domain. $ ./domain.sh foo ... 14:28:24,452 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1 14:28:24,519 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' [Host Controller] 14:28:24,822 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1 [Host Controller] 14:28:24,878 ERROR [stderr] (main) JBAS010961: Invalid option 'foo'. Use domain.sh --help for information on valid command line arguments and their syntax. 14:28:24,886 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 99 14:28:24,891 INFO [org.jboss.as.process] (Thread-6) JBAS012016: Shutting down process controller 14:28:24,892 INFO [org.jboss.as.process] (Thread-6) JBAS012015: All processes finished; exiting Also the line: Invalid option '--foo'Usage: ./standalone.sh [args...] is missing while calling eg. standalone.[sh|bat] --foo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4999) Alllow non persistent configuration(runtime) changes for server groups and domain using CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4999?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-4999: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900636 > Alllow non persistent configuration(runtime) changes for server groups and domain using CLI > ------------------------------------------------------------------------------------------- > > Key: AS7-4999 > URL: https://issues.jboss.org/browse/AS7-4999 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Shay Matasaro > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Using the CLI , It is currently not possible to make runtime config changes to multiple servers , unless you are using a roll-out plan > One example is the ability to disable a mod-cluster context on multiple servers at once. > Since this operation does not affect the persistent server config it is currently not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5884: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 901159|https://bugzilla.redhat.com/show_bug.cgi?id=901159] from NEW to MODIFIED > CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5884 > URL: https://issues.jboss.org/browse/AS7-5884 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Kabir Khan > Priority: Critical > Labels: deployers, domain, eap, jboss > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1. > In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group. > But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available. > The second deployment can be used as long as there is a action to it (e.g. restart). > In that case a FATAL error is thrown: > [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5884: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 901159|https://bugzilla.redhat.com/show_bug.cgi?id=901159] Fixed upstream in November 2012. > CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5884 > URL: https://issues.jboss.org/browse/AS7-5884 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Kabir Khan > Priority: Critical > Labels: deployers, domain, eap, jboss > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1. > In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group. > But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available. > The second deployment can be used as long as there is a action to it (e.g. restart). > In that case a FATAL error is thrown: > [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5976) The command :reload does not check the new configuration, and will cause server crashes if that config is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5976?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5976: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 901192|https://bugzilla.redhat.com/show_bug.cgi?id=901192] from ASSIGNED to MODIFIED > The command :reload does not check the new configuration, and will cause server crashes if that config is broken > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-5976 > URL: https://issues.jboss.org/browse/AS7-5976 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > Priority: Critical > Fix For: 7.2.0.Alpha1 > > > The command :reload does not check the new configuration, and will cause server crashes if that config is broken -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6597) Java Mail 1.5 Support

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6597?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6597: ----------------------------- Description: Per Java EE 7 Specification, update to Java Mail 1.5 API and implementation. Biggest change is introduction of @MailSessionDefinition and @MailSessionDefinitions annotations see: http://kenai.com/bugzilla/show_bug.cgi?id=5743 was:Per Java EE 7 Specification, update to Java Mail 1.5 API and implementation. > Java Mail 1.5 Support > --------------------- > > Key: AS7-6597 > URL: https://issues.jboss.org/browse/AS7-6597 > Project: Application Server 7 > Issue Type: Sub-task > Components: Mail > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 8.0.0.Alpha1 > > > Per Java EE 7 Specification, update to Java Mail 1.5 API and implementation. > Biggest change is introduction of @MailSessionDefinition and @MailSessionDefinitions annotations > see: http://kenai.com/bugzilla/show_bug.cgi?id=5743 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6589) TransformationTargetImpl.getTransformer() does not take ignored resources into account

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6589?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6589: --------------------------------------- The key goal of providing the ignored resource data to the master was so it could aggressively reject the legacy slave if it was unable to perform some transformation on a non-ignored resource. We can't do that with 7.1 slaves, but we can with a 7.2 slave and a > 7.2 master. That said, if we can skip sending the data at all, that's nice, but that's a nice to have. > TransformationTargetImpl.getTransformer() does not take ignored resources into account > -------------------------------------------------------------------------------------- > > Key: AS7-6589 > URL: https://issues.jboss.org/browse/AS7-6589 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 7.3.0.Alpha1 > > > The resources get ignored but not until they are applied on the slave. The intent is that they get ignored on the DC as part of the transformation process and never sent across to the slave. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6601) Increment management model versions for security, messaging, infinispan subsystems

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6601: ------------------------------------- Summary: Increment management model versions for security, messaging, infinispan subsystems Key: AS7-6601 URL: https://issues.jboss.org/browse/AS7-6601 Project: Application Server 7 Issue Type: Task Components: Clustering, Domain Management, JMS, Security Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 7.3.0.Alpha1, 8.0.0.Alpha1 The AS7-6531 fixes have changed the management API for the 3 listed subsystems, and those changes are not expected to be reflected in the 7.2.0.Final tag. As a result, the management model versions need to be incremented. I anticipate using a micro version bump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 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 February 2013