November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3753) HAParititonImpl implements org.jgroups.ChannelListener

by Brian Stansberry (JIRA)

HAParititonImpl implements org.jgroups.ChannelListener ------------------------------------------------------ Key: JBAS-3753 URL: http://jira.jboss.com/jira/browse/JBAS-3753 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 Currently if a JChannel is shunned and disconnects, higher level services are unaware of this and can't take any remedial action. We need to do something like implement ChannelListener so an HAPartition is aware when the events on the underlying channel occur. Then devise a scheme to propagate some of the events to user code. Preferably this will follow as much as possible the existing notification scheme; i.e. pass a new view to HAMembershipListener impls that doesn't include the current node. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-139) Create a general purpose group RPC API

by Brian Stansberry (JIRA)

Create a general purpose group RPC API -------------------------------------- Key: JBCLUSTER-139 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-139 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Abstraction on top of JGroups RpcDispatcher. Start with HAPartition as a base, but minus DRM and DS. Consider what Messaging has done as well as JBCACHE-311. Consider separating the group membership API from the RPC API. RPC API would probably be a subinterface of the group membership one, as group RPC implies being aware of who the group is. This is lower priority, as, except for AS, its an internal implementation detail that can be changed. But, AS exposes HAPartition as an API for end-user code. -- 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, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-3813) BaseWrapperManagedConnectionFactory.isStaleConnection creates new class every call

by Elias Ross (JIRA)

BaseWrapperManagedConnectionFactory.isStaleConnection creates new class every call ---------------------------------------------------------------------------------- Key: JBAS-3813 URL: http://jira.jboss.com/jira/browse/JBAS-3813 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta Reporter: Elias Ross Priority: Minor } boolean isStaleConnection(SQLException e) { boolean isStale = false; if(staleConnectionChecker != null) { isStale = staleConnectionChecker.isStaleConnection(e); } if(staleConnectionCheckerClassName != null) { should change to: -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-324) Ethereal plugin for JGroups

by Bela Ban (JIRA)

Ethereal plugin for JGroups --------------------------- Key: JGRP-324 URL: http://jira.jboss.com/jira/browse/JGRP-324 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.x Write a C implementation of an ethereal plugin which understands the JGroups wire format and displays information about the JGroups messages (e.g. sender, receiver, headers) in ethereal. -- 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, 4 months

3
14
0 / 0

[JBoss JIRA] Created: (JBAS-3594) Allow HAPartitionStateTransfer subscribers to get state after HAPartition start() is called.

by Brian Stansberry (JIRA)

Allow HAPartitionStateTransfer subscribers to get state after HAPartition start() is called. -------------------------------------------------------------------------------------------- Key: JBAS-3594 URL: http://jira.jboss.com/jira/browse/JBAS-3594 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.0.1.CR1 Use the JGroups partial state transfer API for this. Remove the need for dependent services to register as a subscriber before HAPartition.start() is called. Having services interact with HAPartition before start() is contrary to the intended lifecycle semantics. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3633) Tidyup logging when transaction is no longer active

by Adrian Brock (JIRA)

Tidyup logging when transaction is no longer active --------------------------------------------------- Key: JBAS-3633 URL: http://jira.jboss.com/jira/browse/JBAS-3633 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JB5-Transaction Manager Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Priority: Minor Since JBossTM rollsback transactions at transaction timeout, we need to tidyup the transaction demarcation code (commit/rollback/setRollbackOnly, etc) such that the logging is more information and not so noisy. We still need to communicate that the transaction rolled back even if it is not the transaction demarcation point that does the rollback. Currrently, you get errors/warnings about not being able to setRollbackOnly or rollback, because the transaction is already ended. -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JGRP-278) Externalization of socket creation in TCP/TCP_NIO (BasicTCP)

by Bela Ban (JIRA)

Externalization of socket creation in TCP/TCP_NIO (BasicTCP) ------------------------------------------------------------ Key: JGRP-278 URL: http://jira.jboss.com/jira/browse/JGRP-278 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 User configures a socket factory which creates client and server sockets. There is always 1 default factory configured. This allows developers to override socket creation, e.g. for use with SSL sockets. This way, TCP and TCP_NIO can be used with SSL. -- 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, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBRULES-535) allow for plugeable query result handlers

by Mark Proctor (JIRA)

allow for plugeable query result handlers ------------------------------------------- Key: JBRULES-535 URL: http://jira.jboss.com/jira/browse/JBRULES-535 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 Queries should be able to specify how the results are processed once they reach the terminal node. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-706) NullPointerException in RunAsSecurityInterceptorFactory when there is no SecurityDomain annotation

by Roland R?z (JIRA)

NullPointerException in RunAsSecurityInterceptorFactory when there is no SecurityDomain annotation -------------------------------------------------------------------------------------------------- Key: EJBTHREE-706 URL: http://jira.jboss.com/jira/browse/EJBTHREE-706 Project: EJB 3.0 Issue Type: Bug Components: Security Reporter: Roland R?z Priority: Minor The class org.jboss.ejb3.security.RunAsSecurityInterceptorFactory throws in createPerClass() a NullPointerException when there is no SecurityDomain annotation. Possible Fix: if (securityAnnotation != null) { domain = ctx.lookup("java:/jaas/" + securityAnnotation.value()); } -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-724) persistence.xml jar-file processing

by Heiko W. Rupp (JIRA)

persistence.xml jar-file processing ----------------------------------- Key: EJBTHREE-724 URL: http://jira.jboss.com/jira/browse/EJBTHREE-724 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Heiko W. Rupp EJB 3 persistence spec says in 6.2.1.6, 2nd paragraph about <jar-file> "Such JAR files are specified relative to the root of the persistence unit (e.g.,utils/myUtils.jar)" When I have a persistence.xml like this: <persistence> <persistence-unit name="jon"> <jta-data-source>java:/JONDS</jta-data-source> <jar-file>lib/on-enterprise-server-2.0-SNAPSHOT.jar</jar-file> </persistence-unit> </persistence> The PersistenceUnitDeployment gives file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar] but the root of the PersistenceUnit is file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/ 2006-10-04 18:00:43,537 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] Found persistence.xml file in EJB3 jar 2006-10-04 18:00:43,538 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] adding JarFile URL: file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar 2006-10-04 18:00:43,586 INFO [org.hibernate.ejb.Version] Hibernate EntityManager 3.2.0.CR2 2006-10-04 18:00:43,625 INFO [org.hibernate.cfg.annotations.Version] Hibernate Annotations 3.2.0.CR2 2006-10-04 18:00:43,638 INFO [org.hibernate.cfg.Environment] Hibernate 3.2 cr4 2006-10-04 18:00:43,649 INFO [org.hibernate.cfg.Environment] hibernate.properties not found 2006-10-04 18:00:43,654 INFO [org.hibernate.cfg.Environment] Bytecode provider name : javassist 2006-10-04 18:00:43,666 INFO [org.hibernate.cfg.Environment] using JDK 1.4 java.sql.Timestamp handling 2006-10-04 18:00:43,906 DEBUG [org.hibernate.ejb.Ejb3Configuration] Processing PersistenceUnitInfo [ name: jon persistence provider classname: org.hibernate.ejb.HibernatePersistence classloader: org.jboss.mx.loading.UnifiedClassLoader3@3b31a6{ url=file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/ ,addedOrder=43} Temporary classloader: null excludeUnlistedClasses: false JTA datasource: org.jboss.resource.adapter.jdbc.WrapperDataSource@c90acb Non JTA datasource: null Transaction type: JTA PU root URL: file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/ Jar files URLs [ file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar] Managed classes names [] Mapping files names [] Properties [ -- 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, 6 months

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006