July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8708) Enable validation report generation

by Jesper Pedersen (JIRA)

Enable validation report generation ----------------------------------- Key: JBAS-8708 URL: https://jira.jboss.org/browse/JBAS-8708 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.0.0.Beta1 Enhance our container configuration with a validation report path such that report from the validator chain can be written. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1064) EJBContext.isCallerInRole and EJBContext.getCallerPrincipal do not throw IllegalStateException when not allowed

by Carlo de Wolf (JIRA)

EJBContext.isCallerInRole and EJBContext.getCallerPrincipal do not throw IllegalStateException when not allowed --------------------------------------------------------------------------------------------------------------- Key: AS7-1064 URL: https://issues.jboss.org/browse/AS7-1064 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.0.CR1 Reporter: Carlo de Wolf Priority: Critical Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JGRP-1226) Discovery protocol based on Rackspace

by Bela Ban (JIRA)

Discovery protocol based on Rackspace ------------------------------------- Key: JGRP-1226 URL: https://jira.jboss.org/browse/JGRP-1226 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Similar to S3_PING (Amazon), create a discovery protocol (extending FILE_PING) which uses Rackspace's distributed store -- 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, 6 months

6
7
0 / 0

[JBoss JIRA] Created: (JBLOGGING-30) TCLFilter fails to get correct URLs from classloader in AS-5

by jaikiran pai (JIRA)

TCLFilter fails to get correct URLs from classloader in AS-5 -------------------------------------------------------------- Key: JBLOGGING-30 URL: https://jira.jboss.org/jira/browse/JBLOGGING-30 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-log4j Affects Versions: 2.1.0.GA-jboss-logging Reporter: jaikiran pai Assignee: jaikiran pai As explained in JBAS-6532, the TCLFilter doesn't work in AS-5 because it never attempts to use the URLClassLoader while retrieving the Classloader URLs. A patch is attached to that JIRA (details of the patch are in the forum thread) which needs to be applied in jboss-logging-log4j component to get this working. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
9
0 / 0

[JBoss JIRA] Created: (JBRULES-443) Release drools binaries with debug information

by Juergen none (JIRA)

Release drools binaries with debug information ---------------------------------------------- Key: JBRULES-443 URL: http://jira.jboss.com/jira/browse/JBRULES-443 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Juergen none Assigned To: Mark Proctor Priority: Trivial Would it be possible to supply a debug-build of the binaries in addition to the existing downloads (where at least the drools jar files are without debug-info)? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2251) ThreadlocalPool.discard() memory leak

by Takayoshi Kimura (JIRA)

ThreadlocalPool.discard() memory leak ------------------------------------- Key: EJBTHREE-2251 URL: https://issues.jboss.org/browse/EJBTHREE-2251 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: bom-eap5-1.0.1 Reporter: Takayoshi Kimura ThreadlocalPool internally uses an InfinitePool and the InfinitePool.discard() method doesn't remove the ctx from its LinkedList active field properly thus memory leaked when an exception is thrown from bean method. Need to fix InfinitePool.discard() method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-9075) Ability to specify rollout plans via the CLI

by Brian Stansberry (JIRA)

Ability to specify rollout plans via the CLI -------------------------------------------- Key: JBAS-9075 URL: https://issues.jboss.org/browse/JBAS-9075 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 Handle rollout plans as detailed in http://community.jboss.org/docs/DOC-16336. In Beta1 these would probably work via :some-op(foo=bar,rollout-plan={...complicated DMR...}). This task is to look for something more user friendly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
7
0 / 0

[JBoss JIRA] Created: (JBAS-9090) Ensure all subsystems have a proper "remove" operation

by Brian Stansberry (JIRA)

Ensure all subsystems have a proper "remove" operation ------------------------------------------------------ Key: JBAS-9090 URL: https://issues.jboss.org/browse/JBAS-9090 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 Validate remove handling for all subsystems. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
10
0 / 0

[JBoss JIRA] Created: (JGRP-1002) Merge: make the coordinator remain the same if possible after a merge

by Bela Ban (JIRA)

Merge: make the coordinator remain the same if possible after a merge --------------------------------------------------------------------- Key: JGRP-1002 URL: https://jira.jboss.org/jira/browse/JGRP-1002 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 When we have {C, A, B} and split into {C,A} and {B}, then a merge will produce {A,B,C}. Therefore the coord is moved from C to A. For certain apps, e.g. JBoss singletons, this is not good, as we're moving the singleton services from a perfectly healthy node to a different node. GOAL: come up with a deterministic policy of picking a coord such that we minimize coord switching if the existing coord is still member of the cluster. This depends on or is related to the flexible coord pick policy JIRA issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8698) Datasource XAExceptions leads to corrupt Transaction Context on thread

by Anders Welen (JIRA)

Datasource XAExceptions leads to corrupt Transaction Context on thread ---------------------------------------------------------------------- Key: JBAS-8698 URL: https://jira.jboss.org/browse/JBAS-8698 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Remoting, Transaction Manager Integration (Arjuna) Affects Versions: 6.0.0.CR1, JBossAS-5.1.0.GA, JBossAS-4.2.1.GA Reporter: Anders Welen Assignee: Scott Stark Attachments: TestCase3850.tar When MySQL throws a "com.mysql.jdbc.jdbc2.optional.MysqlXAException" when called from a remote client the server thread doesn't seem to be cleaned up of transaction context data. All calls that reusing the thread will fail with the following exception: org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:e137:4cf78939:68 status: ActionStatus.COMMITTING >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:e137:4cf78939:68 status: ActionStatus.COMMITTING >) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95) at se.redpill.TestCase3850Bean.runTest(TestCase3850Bean.java:22) ... ... ... >From what I can see the "MysqlXAException" (implements XAException) will not be caught in "com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.java". (Can it be some kind of classloading problem?) As the result the thread will not be cleaned of transaction information and "broken" when reused. This seems only to occur for remote clients (If the client calls within the JVM it seems to work) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
6
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 July 2011