December 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5555) Rationalize clustering metadata

by Brian Stansberry (JIRA)

Rationalize clustering metadata ------------------------------- Key: JBAS-5555 URL: http://jira.jboss.com/jira/browse/JBAS-5555 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Deployers Reporter: Brian Stansberry Assigned To: Brian Stansberry Clustering metadata is scattered in different metadata objects. Need to rationalize, particularly to support adding clustering aspects to non-JEE beans. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5551) Provide cluster topology info to the DeploymentManager impl

by Brian Stansberry (JIRA)

Provide cluster topology info to the DeploymentManager impl ----------------------------------------------------------- Key: JBAS-5551 URL: http://jira.jboss.com/jira/browse/JBAS-5551 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 DeploymentManager operations create a list of DeploymentTargets. Currently this list only includes the local node. Need to integrate cluster topology information so it can include one DeploymentTarget per node in the cluster (at least if the relevant DeploymentPhase is APPLICATION_CLUSTERED.) -- 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
6
0 / 0

[JBoss JIRA] Created: (JBAS-6933) Review HA design to inlcude Mobicents more easily

by jean deruelle (JIRA)

Review HA design to inlcude Mobicents more easily ------------------------------------------------- Key: JBAS-6933 URL: https://jira.jboss.org/jira/browse/JBAS-6933 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.CR1 Reporter: jean deruelle Assignee: Brian Stansberry Priority: Minor Change the clustering design to allow for extensibility without so much protected methods as per the JBoss Fourm thread http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231472#4231472 -- 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
5
0 / 0

[JBoss JIRA] Created: (JGRP-1256) NakReceiverWindow removeMany infinite loop

by ronald yang (JIRA)

NakReceiverWindow removeMany infinite loop ------------------------------------------ Key: JGRP-1256 URL: https://jira.jboss.org/browse/JGRP-1256 Project: JGroups Issue Type: Bug Affects Versions: 2.8.1 Reporter: ronald yang Assignee: Bela Ban it is possible for the NakReceiverWindow to enter an infinite loop if max_xmit_buf_size has been set. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (JGRP-1258) NAKACK: remove max_xmit_buf_size

by Bela Ban (JIRA)

NAKACK: remove max_xmit_buf_size -------------------------------- Key: JGRP-1258 URL: https://jira.jboss.org/browse/JGRP-1258 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12 This property discards the oldest N message (even undelivered one), to keep the max number of messages buffered for retransmission to max_xmit_buf_size. However, this leads to issues. E.g. when P sent a message M, then discards it because max_xmit_buf_size has been exceeded, and then a member Q asks P for retransmission of M, P won't be able to furnish M ! We don't have a concept of being able to tell Q that it will never receive M and should therefore skip it. This would require quite some code changes, so we don't do it here (maybe later). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1255) AUTH: merging bypasses authorization process

by Bela Ban (JIRA)

AUTH: merging bypasses authorization process -------------------------------------------- Key: JGRP-1255 URL: https://jira.jboss.org/browse/JGRP-1255 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12 AUTH checks admission into the group at JOIN time, but *not* at MERGE time ! To reproduce: - Copy auth.xml from JGroups/conf - Copy auth.xml to auth1.xml - Change the password in auth1.xml from "chris" to "chrissie" - Add <DISCARD use_gui="true"/> just above the transport to *both* auth.xml and auth1.xml - Start the instance A: java org.jgroups.demos.Draw -props ./auth.xml -name A - In the discard dialog box, click on "start discarding" - Start instance B: java org.jgroups.demos.Draw -props ./auth1.xml -name B - A and B will form 2 singleton clusters {A} and {B} - In instance A: click on "stop discarding" in the discard dialog box - A and B will merge into a cluster {A,B} SOLUTION: AUTH also needs to hook into the merge process and prevent a merge if authorization fails -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2212) Regression: @ApplicationException is not properly processed for jars in lib directories

by Carlo de Wolf (JIRA)

Regression: @ApplicationException is not properly processed for jars in lib directories --------------------------------------------------------------------------------------- Key: EJBTHREE-2212 URL: https://jira.jboss.org/browse/EJBTHREE-2212 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1728) Create a JTA profile for use in unit tests

by Carlo de Wolf (JIRA)

Create a JTA profile for use in unit tests ------------------------------------------ Key: EJBTHREE-1728 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1728 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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-1232) A failing commit must not throw a RuntimeException

by Carlo de Wolf (JIRA)

A failing commit must not throw a RuntimeException -------------------------------------------------- Key: EJBTHREE-1232 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1232 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 java.lang.RuntimeException: javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state at org.jboss.aspects.tx.TxPolicy.handleEndTransactionException(TxPolicy.java:198) -- 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
11
0 / 0

[JBoss JIRA] Created: (JBAS-5102) Crossreferencing EJBs using comp-names does not work

by Christian Nolte (JIRA)

Crossreferencing EJBs using comp-names does not work ---------------------------------------------------- Key: JBAS-5102 URL: http://jira.jboss.com/jira/browse/JBAS-5102 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA Reporter: Christian Nolte Assigned To: Carlo de Wolf I have two stateless session beans which are referencing each other like that: @Stateless public class SessionBeanA implements SessionBeanALocal { @EJB private SessionBeanB sessionB; } and @Stateless public class SessionBeanB implement SessionBeanBLocal { @EJB private SessionBeanA sessionA; } When deploying the application on JBoss AS I get --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jar=test.jar,name=SessionBeanA,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:jar=test.jar,name=SessionBeanB,service=EJB3 persistence.units:jar=test.jar,unitName=test.jar Depends On Me: jboss.j2ee:jar=test.jar,name=SessionBeanB,service=EJB3 ObjectName: jboss.j2ee:jar=test.jar,name=SessionBeanB,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:jar=test.jar,name=SessionBeanA,service=EJB3 Depends On Me: jboss.j2ee:jar=test.jar,name=SessionBeanA,service=EJB3 and the deployment fails. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2010