November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1591) Re-implement client-side asynchronous support

by Andrew Lee Rubinger (JIRA)

Re-implement client-side asynchronous support --------------------------------------------- Key: EJBTHREE-1591 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1591 Project: EJB 3.0 Issue Type: Task Components: common Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-Beta7 We need a mechanism allowing clients to invoke an operation asynchronously. This was previously provided by jboss-ejb3-async as part of the proxy code, but has now been decouped. Build on top of the runtime mixin as supplied by EJBTHREE-1589. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6039) Change JGroups thread pool rejection policy to 'Discard'

by Brian Stansberry (JIRA)

Change JGroups thread pool rejection policy to 'Discard' -------------------------------------------------------- Key: JBAS-6039 URL: https://jira.jboss.org/jira/browse/JBAS-6039 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Reporter: Brian Stansberry Fix For: JBossAS-5.0.0.GA Change the standard stacks so thread_pool.rejection_policy="Discard" rather than 'Run'. Run allows the packet reader thread to pass messages up the stack and possibly block, leading to a disfunctional channel. The http session replication soak tests Radoslav Husar is doing were able to generate sufficient load to cause this. At the same time I'll look at the thread pool min sizes. -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3916) Update source code headers.

by Dimitris Andreadis (JIRA)

Update source code headers. --------------------------- Key: JBAS-3916 URL: http://jira.jboss.com/jira/browse/JBAS-3916 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta2 Update the source code headers, like it was done for Branch_4_0 in JBAS-3601 -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1843) NPE when debugging rules with "from" clause

by Edson Tirelli (JIRA)

NPE when debugging rules with "from" clause ------------------------------------------- Key: JBRULES-1843 URL: https://jira.jboss.org/jira/browse/JBRULES-1843 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.M2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.0.0.M3 -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1774) CMS metadata is lost on export

by Martin Putz (JIRA)

CMS metadata is lost on export ------------------------------ Key: JBPORTAL-1774 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1774 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.2 Final, 2.4.1 SP1 Reporter: Martin Putz Assigned To: Sohil Shah CMS metadata, such as title or description, is not being exported. If you do an export/import cycle of CMS data, you will therefore lose information. -- 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

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1841) If any global is a declared type it makes the test scenarios fail.

by Toni Rikkola (JIRA)

If any global is a declared type it makes the test scenarios fail. ------------------------------------------------------------------ Key: JBRULES-1841 URL: https://jira.jboss.org/jira/browse/JBRULES-1841 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Toni Rikkola Assignee: Toni Rikkola Fix For: 5.0.0.M3 -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5908) ClientUserTransactionObjectFactory is inefficient

by Adrian Brock (JIRA)

ClientUserTransactionObjectFactory is inefficient ------------------------------------------------- Key: JBAS-5908 URL: https://jira.jboss.org/jira/browse/JBAS-5908 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Manager (JBossTM) Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1 Reporter: Adrian Brock Assignee: Galder Zamarreno Fix For: JBossAS-5.0.0.CR2, JBossAS-4.2.4.GA The ClientUserTransactionObjectFactory is inefficient. 1) It is doing initialisation based on a static cached instance Since nothing holds a hard reference to this class, it can be garbage collected meaning the initialisation can be done multiple times. 2) The determination and resolving of the ServerVMClientUserTransaction does the lookup for the transaction twice. Once when initialising the singleton and again to see whether it should use the singleton. Both issues could be resolved by simplifying ClientUserTransactionObjectFactory.getUserTransaction() to be something (which removes the need for the cached object) static private UserTransaction getUserTransaction() { ServerVMClientUserTransaction serverUserTransaction = ServerVMClientUserTransaction.getSingleton(); if (serverUserTranasction.isServer()) return serverUserTransaction; else return ClientUserTransaction.getSingleton(); } This would require a new method on ServerVMClientUserTransaction to detect whether it can be used, i.e. it can locate a local transaction manager. public boolean isServer() { return tm != null; } -- 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

15 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-6194) Move transaction sticky logic in proxy to interceptors to avoid bottleneck

by Galder Zamarreno (JIRA)

Move transaction sticky logic in proxy to interceptors to avoid bottleneck -------------------------------------------------------------------------- Key: JBAS-6194 URL: https://jira.jboss.org/jira/browse/JBAS-6194 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Transaction Manager (JBossTM) Affects Versions: JBossAS-5.0.0.CR2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: JBossAS-5.0.0.GA With the current user transaction sticky tpc retrieval method, a bottleneck can be formed when invocation returns are too big. To avoid such bottleneck, we'll separate the transaction sticky logic in proxy into two separate interceptors, one for EJBs, one for ClientUserTransactionService's clustered proxy. By doing this, we're able to provide a cleaner solution, separating this logic from the proxy, and making it even more optional, reducing the risks of affecting normal (non user transaction sticky) invocations. Another interesting idea for the future would be to use a synchronised version of a weak IdentiyHashMap. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1582) EJB 2.1 home getHomeHandle() returns null and getEJBMetaData() has null home handle

by Carlo de Wolf (JIRA)

EJB 2.1 home getHomeHandle() returns null and getEJBMetaData() has null home handle ----------------------------------------------------------------------------------- Key: EJBTHREE-1582 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1582 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: 1.0.0-Beta6 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 1.0.0-Beta7 -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1578) A security-identity element with run-as in descriptor is ignored

by Carlo de Wolf (JIRA)

A security-identity element with run-as in descriptor is ignored ---------------------------------------------------------------- Key: EJBTHREE-1578 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1578 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: 1.0.0-Beta6 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 1.0.0-Beta7 -- 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

15 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008