March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-62) Is there anyway to control standalone/tmp/vfs folder incresing size?

by Mahesh Khatal (JIRA)

Mahesh Khatal created LOGMGR-62: ----------------------------------- Summary: Is there anyway to control standalone/tmp/vfs folder incresing size? Key: LOGMGR-62 URL: https://issues.jboss.org/browse/LOGMGR-62 Project: JBoss Log Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Mahesh Khatal Assignee: David Lloyd Hi, my application gets sloved b'coz standalone/tmp/vfs folder size gets incresing. Is there any way to come out of this? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6812) jboss-cli.xml does not support the 1.2 schema correctly

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6812: ----------------------------------- Summary: jboss-cli.xml does not support the 1.2 schema correctly Key: AS7-6812 URL: https://issues.jboss.org/browse/AS7-6812 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Stuart Douglas Assignee: Alexey Loubyansky There is a 1.2 schema however it targets the 1.1 namepsace and the parser only looks for 1.1, we we essentually have two different 1.1 namepsaces. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-121) Tracker JIRA for APIs required by the Java EE 7 Platform Specification

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-121?page=com.atlassian.jira.plugin.s... ] Shelly McGowan edited comment on JBEE-121 at 3/27/13 7:40 PM: -------------------------------------------------------------- Other EE 7 API releases: Bean Validation 1.1: http://repo1.maven.org/maven2/javax/validation/validation-api/1.1.0.CR1/ CDI 1.1: http://repo1.maven.org/maven2/javax/enterprise/cdi-api/1.1-PFD/ JPA 2.1 (Hibernate): https://repository.jboss.org/nexus/content/groups/public/org/hibernate/ja... was (Author: shelly.mcgowan): Other EE 7 API releases: Bean Validation 1.1: http://repo1.maven.org/maven2/javax/validation/validation-api/1.1.0.CR1/ CDI 1.1: http://repo1.maven.org/maven2/javax/enterprise/cdi-api/1.1-PFD/ JPA 2.1 (Hibernate): https://repository.jboss.org/nexus/content/groups/public/org/hibernate/ja... > Tracker JIRA for APIs required by the Java EE 7 Platform Specification > ---------------------------------------------------------------------- > > Key: JBEE-121 > URL: https://issues.jboss.org/browse/JBEE-121 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6596) JSR-907 JTA 1.2 Support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6596?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-6596: ----------------------------- Assignee: (was: Jason Greene) > JSR-907 JTA 1.2 Support > ----------------------- > > Key: AS7-6596 > URL: https://issues.jboss.org/browse/AS7-6596 > Project: Application Server 7 > Issue Type: Sub-task > Components: Transactions > Reporter: David Lloyd > Fix For: 8.0.0.Alpha1 > > > Per Java EE 7 specification, update to JTA 1.2 compliance. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6655) binding subcontexts with <lookup> does not work

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-6655?page=com.atlassian.jira.plugin.s... ] Eduardo Martins commented on AS7-6655: -------------------------------------- Please note, the fix allows this use case to go through, yet it does not introduce any change wrt msc dependencies, which are globally under discussion in the context of AS7-6787 > binding subcontexts with <lookup> does not work > ----------------------------------------------- > > Key: AS7-6655 > URL: https://issues.jboss.org/browse/AS7-6655 > Project: Application Server 7 > Issue Type: Bug > Components: Naming > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Eduardo Martins > > If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. > To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ > In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. > As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-3837) Fix or remove WebSecurityCERTTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-3837?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reopened AS7-3837: ------------------------------ Assignee: Tomaz Cerar (was: Stefan Guilhen) I have fix for this test case on my undertow integration branch > Fix or remove WebSecurityCERTTestCase > ------------------------------------- > > Key: AS7-3837 > URL: https://issues.jboss.org/browse/AS7-3837 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.Final > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Labels: as7-ignored > Fix For: 7.1.2.Final (EAP) > > > This has an @Ignore on it from ages ago noting that it is waiting for Arquillian beta2 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-3837) Fix or remove WebSecurityCERTTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-3837?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-3837: ----------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.1.2.Final (EAP)) > Fix or remove WebSecurityCERTTestCase > ------------------------------------- > > Key: AS7-3837 > URL: https://issues.jboss.org/browse/AS7-3837 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.Final > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Labels: as7-ignored > Fix For: 8.0.0.Alpha1 > > > This has an @Ignore on it from ages ago noting that it is waiting for Arquillian beta2 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6811) Fix & re-enable ignored XCAML tests

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-6811: -------------------------------- Summary: Fix & re-enable ignored XCAML tests Key: AS7-6811 URL: https://issues.jboss.org/browse/AS7-6811 Project: Application Server 7 Issue Type: Sub-task Components: Security, Web Affects Versions: 8.0.0.Alpha1 Reporter: Tomaz Cerar Assignee: Darran Lofthouse Currently ignore tests: {noformat} WebXACMLAuthorizationModuleTestCase {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6810) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Kabir Khan (JIRA)

Kabir Khan created AS7-6810: ------------------------------- Summary: Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> Key: AS7-6810 URL: https://issues.jboss.org/browse/AS7-6810 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.Alpha1 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6809) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

by Kabir Khan (JIRA)

Kabir Khan created AS7-6809: ------------------------------- Summary: Avoid running out of threads when connecting to the DC from a slave to pull down missing data Key: AS7-6809 URL: https://issues.jboss.org/browse/AS7-6809 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.Alpha1 For AS7-6808 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC. The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock -- 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, 9 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 March 2013