April 2008 - jboss-jira - Jboss List Archives

[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

[JBoss JIRA] Created: (JBAS-5197) Add "RetryInterceptor" functionality to all clustered proxies

by Brian Stansberry (JIRA)

Add "RetryInterceptor" functionality to all clustered proxies ------------------------------------------------------------- Key: JBAS-5197 URL: http://jira.jboss.com/jira/browse/JBAS-5197 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.1.0.CR1 Container issue for ensuring "RetryInterceptor" functionality is added to all clustered proxies. "RetryInterceptor" functionality consists of adding an interceptor that is able to access the cluster (currently via JNDI) and get an updated set of cluster targets when all current targets have failed. Needed when a complete cluster restart has occurred since the current list of targets was deserialized on the client. We currently have this for EJB2 proxies; need it for EJB3, HA-JNDI and generic AOP-based and ProxyFactoryHA-based proxies. -- 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

4
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1074) Circular @EJB3 references in session beans fail to deploy.

by Gunnar Grim (JIRA)

Circular @EJB3 references in session beans fail to deploy. ---------------------------------------------------------- Key: EJBTHREE-1074 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA Reporter: Gunnar Grim The following circular references makes the application undeployable: In ArchiveBrokerBean: @EJB private SeriesBrokerLocal itsSeriesBroker; In SeriesBrokerBean @EJB private ArchiveBrokerLocal itsArchiveBroker; Circular references like these work fine in Glassfish but JBoss shows the following error message: ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU Depends On Me: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU Depends On Me: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3 ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU -- 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

10
11
0 / 0

[JBoss JIRA] Created: (JGRP-747) RELAY: replication between data centers

by Bela Ban (JIRA)

RELAY: replication between data centers --------------------------------------- Key: JGRP-747 URL: http://jira.jboss.com/jira/browse/JGRP-747 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x [from JGroups/doc/design/DataCenterReplication.txt] Replication between data centers ================================ Author: Bela Ban Version: $Id: DataCenterReplication.txt,v 1.6 2008/04/25 15:54:30 belaban Exp $ We have data centers in New York (NYC) and San Francisco (SFO). The idea is to replicate traffic from NYC to SFO asynchronously. In case of a site failure of NYC, all clients can be switched over to SFO and continue working with (almost) up-to-date data. The failing over of clients to SFO is outside the scope of this proposal, and could be done for example by changing DNS entries, load balancers etc. There is no replication going on from SFO to NYC by default, only when SFO becomes the primary site. The assumption is that there is no message between data centers which requires a response. This would require NAT functionlity, which we may provide in a future version. For the example, we assume that each site uses a UDP based stack, and replication between the sites use a TCP based stack, see figure DataCenterReplication.png. There is a local cluster, based on UDP, at each site and one global cluster, based on TCP, which connects the two sites. Each coordinator of the local cluster is also a member of the global cluster, e.g. member E in NYC (assuming it is the coordinator) is also member X of the TCP cluster. This is called a *relay* member. A relay member is always member of the local and global cluster. A relay member has a UDP stack which additionally contains a protocol RELAY at the top (shown in the bottom part of the figure). RELAY has a JChannel which connects to the TCP group, but *only* when it is (or becomes) coordinator of the local cluster. The configuration of the TCP channel is done via a property in RELAY. Any *multicast* message (we don't relay unicast messages) that is received by RELAY traveling up the stack is sent via the TCP channel to the other site. When received there, the corresponding RELAY protocol changes the destination of the message to null (those are multicast messages after all) and leaves the src (which might point to X if sent from NYC), then it sends the message down the stack, where it will get multicast to all members of the local cluster (including the sender). When a response is received which points to any non-local address (e.g. X), RELAY simply drops it. When forwarding a message to the local cluster, RELAY adds a header. When it receives the multicast message it forwarded itself, and a header is present, it does *not* relay it back to the other site but simply drops it. Otherwise, we would have a cycle. When a coordinator crashes or leaves, the next-in-line becomes coordinator and activates the RELAY protocol, connecting to the TCP channel and starting to relay messages. However, if we receive messages from the local cluster while the coordinator has crashed and the new one hasn't taken over yet, we'd lose messages. Therefore, we need additional functionality in RELAY which buffers the last N messages (or M bytes, or for T seconds) and numbers all messages sent. This is done by the second-in-line. When there is a coordinator failover, the new coordinator communicates briefly with the other site to determine which was the highest message relayed by it. It then forwards buffered messages with lower numbers and removes the remaining messages in the buffer. During this replay, message relaying is suspended. Therefore, a relay has to handle 3 types of messages from the global (TCP) cluster: (1) Regular multicast messages (2) A message asking for the highest sequence number received from another relay, and the response to this (3) A message stating that the other side will go down gracefully (no need to replay buffered messages) Example walkthrough ------------------- - C (in the NYC cluster, with coordinator E) multicasts a message - A, B, C, D and E receive the multicast - D (second-in-line) buffer the message (bounded buffer) - E is the relay. The byte buffer is extracted and a new message M is created. M's source is C, the dest is null (= send to all). Note that the original headers are *not* sent with M. If this is needed, we need to revisit. - X receives M, drops it (because it is the sender, determined by the header). - Y receives M, adds a RELAY header and sends it down the stack - T, U, V, W and S receive M and deliver it - Y does not relay M because M has a header - Should some member reply (to X), then RELAY at Y will drop the message -- 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
8
0 / 0

[JBoss JIRA] Created: (SECURITY-136) jboss-web defined authenticators in JBoss 4.2.x?

by Darran Lofthouse (JIRA)

jboss-web defined authenticators in JBoss 4.2.x? ------------------------------------------------ Key: SECURITY-136 URL: http://jira.jboss.com/jira/browse/SECURITY-136 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1073) SessionContext.getBusinessObject(...) throws IllegalStateException on @Service EJB

by Michael McKibben (JIRA)

SessionContext.getBusinessObject(...) throws IllegalStateException on @Service EJB ---------------------------------------------------------------------------------- Key: EJBTHREE-1073 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1073 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.1.GA Reporter: Michael McKibben Calling SessionContext.getBusinessObject(...) throws an IllegalStateException within a @Service EJB. This should behave like a Stateless/Stateful EJB no? -- 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
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1370) [M]Bulk change of package, category of asset lists

by Michael Neale (JIRA)

[M]Bulk change of package, category of asset lists -------------------------------------------------- Key: JBRULES-1370 URL: http://jira.jboss.com/jira/browse/JBRULES-1370 Project: JBoss Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 8 months

6
16
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1045) Improve error message when binding fails

by Carlo de Wolf (JIRA)

Improve error message when binding fails ---------------------------------------- Key: EJBTHREE-1045 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.1.GA Reporter: Carlo de Wolf Fix For: AS 4.2.2.GA, EJB 3.0 RC11 - FD 2007-09-03 14:58:50,737 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2 ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3 java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context at org.jboss.util.naming.Util.createSubcontext(Util.java:69) at org.jboss.util.naming.Util.rebind(Util.java:125) at org.jboss.util.naming.Util.rebind(Util.java:113) at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115) In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens. It should say an error message in the likes of: "Can't bind ItemSession/remoteHome, because ItemSession is already bound" -- 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, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-4211) Detecting OutOfMemoryErrors in Servers in the Test Suite

by Ryan Campbell (JIRA)

Detecting OutOfMemoryErrors in Servers in the Test Suite -------------------------------------------------------- Key: JBAS-4211 URL: http://jira.jboss.com/jira/browse/JBAS-4211 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Suite Reporter: Ryan Campbell Assigned To: Martin Vecera Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-4.0.5.SP1 We need a custom test runner which checks for OOME's in any running servers between each test. Optionally, only check for this after a failed test. See the discussion for details. -- 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, 8 months

4
16
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 April 2008