April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1235) Fix french translation of org.jboss.as.connector.logging.ConnectorLogger

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1235?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1235: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 955859|https://bugzilla.redhat.com/show_bug.cgi?id=955859] Fix the french translation of org.jboss.as.connector.logging.ConnectorLogger : deployingCompliantJdbcDriver=D\u00E9ploiement du pilote compatible JDCB %s (version %d.%d) deployingNonCompliantJdbcDriver=D\u00E9ploiement du pilote non compatible JDCB %s (version %d.%d) Should say "JDBC" instead of "JDCB" > Fix french translation of org.jboss.as.connector.logging.ConnectorLogger > ------------------------------------------------------------------------ > > Key: WFLY-1235 > URL: https://issues.jboss.org/browse/WFLY-1235 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Dominique Jean-Prost > > Fix french translation of org.jboss.as.connector.logging.ConnectorLogger : > deployingCompliantJdbcDriver=D\u00E9ploiement du pilote compatible JDCB %s (version %d.%d) > deployingNonCompliantJdbcDriver=D\u00E9ploiement du pilote non compatible JDCB %s (version %d.%d) > used JCDB instead of *JDBC* -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1235) Fix french translation of org.jboss.as.connector.logging.ConnectorLogger

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1235?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1235: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=955859 > Fix french translation of org.jboss.as.connector.logging.ConnectorLogger > ------------------------------------------------------------------------ > > Key: WFLY-1235 > URL: https://issues.jboss.org/browse/WFLY-1235 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Dominique Jean-Prost > > Fix french translation of org.jboss.as.connector.logging.ConnectorLogger : > deployingCompliantJdbcDriver=D\u00E9ploiement du pilote compatible JDCB %s (version %d.%d) > deployingNonCompliantJdbcDriver=D\u00E9ploiement du pilote non compatible JDCB %s (version %d.%d) > used JCDB instead of *JDBC* -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-133) Expression Language 3.0 (JSR-341) APIs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-133?page=com.atlassian.jira.plugin.s... ] Shelly McGowan reassigned JBEE-133: ----------------------------------- Assignee: Remy Maucherat (was: Shelly McGowan) The signature tests from the early access EL 3.0 standalone TCK are passing against this repository. Assigning to @Remy for review prior to the 1.0.0.Alpha1 release. > Expression Language 3.0 (JSR-341) APIs > -------------------------------------- > > Key: JBEE-133 > URL: https://issues.jboss.org/browse/JBEE-133 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-javaee-specs > Reporter: Shelly McGowan > Assignee: Remy Maucherat > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-88) Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-88?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-88: --------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 952746|https://bugzilla.redhat.com/show_bug.cgi?id=952746] from NEW to POST > Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC > -------------------------------------------------------------------------------------------- > > Key: WFLY-88 > URL: https://issues.jboss.org/browse/WFLY-88 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Reporter: Ivo Studensky > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: logs_prepareHaltClient.tgz > > > It looks like recovery process is not fully triggered on a distributed transaction when the transaction falls down at prepare phase of 2PC. In the new crash recovery tests over propagated transactions only one of two servers recovers from the crash, but the other keeps an unfinished tx in its tx log. > It corresponds to prepareHaltClient and prepareHaltServer test methods of org.jboss.as.test.jbossts.crashrec.txpropagation.TxPropagationCrashRecoveryTestCase, see JBQA-2604 for general description of the new tests. The prepareHaltClient test crashes the server which initiated the transaction, while as the prepareHaltServer test crashes the second server. > The tests are written against EAP6.x branch, so for reproducing this it is needed a built server from the 7.1 branch of AS7. > Steps to reproduce. > 1. git clone -b as7 git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-transactions.git > 2. cd eap-tests-transactions > 3. git checkout tx_propag_crashrec_tests > 4a. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltClient -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > or > 4b. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltServer -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > The logs of prepareHaltClient run attached to this jira. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-133) Expression Language 3.0 (JSR-341) APIs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-133?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-133: ------------------------------------- Additional updates were made based on the RI 3.0-b08 APIs: https://github.com/jboss/jboss-el-api_spec/commit/0ac8cc1e1dc0459ff25b1dc... This also includes a change to use com.sun.el.ExpressionFactoryImpl: https://github.com/jboss/jboss-el-api_spec/commit/0ac8cc1e1dc0459ff25b1dc... > Expression Language 3.0 (JSR-341) APIs > -------------------------------------- > > Key: JBEE-133 > URL: https://issues.jboss.org/browse/JBEE-133 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-javaee-specs > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1177) Recursive expression resolution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1177?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1177: ----------------------------------- Assignee: Jess Sightler > Recursive expression resolution > ------------------------------- > > Key: WFLY-1177 > URL: https://issues.jboss.org/browse/WFLY-1177 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jess Sightler > > When resolving an expression, keep resolving until the output of the resolution matches the input. > Use case: > ${sys.prop.with.host.specific.value} > resolves to > ${VAULT::xxxxx} > which resolves to > thesecret > Basically, the main mechanism for customizing domain-level configs on a per-host basis is to use expressions and use different values on each host. But this breaks down when a vault expression is added to the mix. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-996) No way to query valid property values for objects of type PROPERTY via cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-996?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-996. ----------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Won't Fix There's nothing we will do about this as a general issue. If a particular resource is using properties instead of exposing fully defined attributes, please file a specific to get that corrected. > No way to query valid property values for objects of type PROPERTY via cli > -------------------------------------------------------------------------- > > Key: WFLY-996 > URL: https://issues.jboss.org/browse/WFLY-996 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: CLI browsing AS 7.1.1.Final model with modcluster enabled via *ha profile. > Reporter: Simeon Pinder > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > If you run the following to browse the resource-description > subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description(operations=true,inherited=false,recursive=false,proxies=false) > You'll encounter Object type = PROPERTY > "property" => { > "description" => "Properties for the metric.", > "type" => PROPERTY, > "required" => false > } > Which has an acceptable list of property values as described here. > http://docs.jboss.org/mod_cluster/1.2.0/html/java.AS7config.html#LoadMetric > There is no way to query the acceptable and currently supported list of property values via cli. You must hard code and risk going out of synch with as7/modclusters supported values. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1014) Enable CORS requests

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1014?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1014: ----------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > Enable CORS requests > -------------------- > > Key: WFLY-1014 > URL: https://issues.jboss.org/browse/WFLY-1014 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Harald Pehl > Assignee: Darran Lofthouse > > We've been prototyping an alternative distribution channel for the console and have setup a demo that leverages the mozilla app store to deliver the AS7 web console to users: > https://marketplace.firefox.com/app/kea/?src=mkt-search > For this to work the AS needs to fully support CORS [1]. The general idea is that you can retrieve the console through a marketplace like the mozilla one (chrome would be another alternative) and connect to any domain controller, wether it runs locally or remotely. > If want to give it shot, point four firefox browser to the marketplace URL, launch the app and connect to our CORS demo instance that runs on EC2: > http://as7-preview.dyndns.org:9990 > user: admin > pass: webstore123! > [1] http://en.wikipedia.org/wiki/Cross-origin_resource_sharing -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-352) EAP 6 Domain Mode Logging for Management is nonexistent.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-352?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-352: ---------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > EAP 6 Domain Mode Logging for Management is nonexistent. > --------------------------------------------------------- > > Key: WFLY-352 > URL: https://issues.jboss.org/browse/WFLY-352 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Eric Rich > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > Attachments: jboss-as-domain-management-7.1.2.Final-redhat-1.jar, log_mgmt_auth_calls.txt > > > When trying to diagnose LDAP or Admin Configuration issue in Domain mode there is currently no logging for any of the authentication information. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1270) Split logging subsystem parser for different schema versions

by James Perkins (JIRA)

James Perkins created WFLY-1270: ----------------------------------- Summary: Split logging subsystem parser for different schema versions Key: WFLY-1270 URL: https://issues.jboss.org/browse/WFLY-1270 Project: WildFly Issue Type: Enhancement Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor The logging subsystem parser currently reads and writes XML for all schema versions. Split the reads out into a different parsers. -- 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

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013