December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-405) Research issue with microcontainer kernel retro builds

by Paul Gier (JIRA)

Research issue with microcontainer kernel retro builds ------------------------------------------------------ Key: JBBUILD-405 URL: http://jira.jboss.com/jira/browse/JBBUILD-405 Project: JBoss Build System Issue Type: Task Components: JBossRetro, Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 The microcontainer kernel is not able to compile with dependency on retroed version of jboss-container. It compiles ok depending on the regular container, but with the retro container, there is a problem with the annotations. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed

by Dominik Pospisil (JIRA)

Upon Shutdown connectors should be stopped before applications are undeployed ----------------------------------------------------------------------------- Key: JBAS-4735 URL: http://jira.jboss.com/jira/browse/JBAS-4735 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Reporter: Dominik Pospisil Assigned To: Brian Stansberry In clustered environment the process of shutting down single AS instance should be transparent to clients. This is not the case since applications are udeployed at first while connectors are still servicing requests. This causes clients not to be redirected to another cluster nodes and to receive resource not avaiable exceptions. >From the client perspective, shutdown process should should work like follows: 1) stop connectors so they refuse servicing new requests 2) complete running requests 3) undeploy applications -- 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, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1097) Cleaning JBM Tables During Startup

by Tyronne Wickramarathne (JIRA)

Cleaning JBM Tables During Startup ---------------------------------- Key: JBMESSAGING-1097 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Persistence Affects Versions: 1.4.0.GA Environment: JBossAS-4.2.0-GA JBossMessaging-1.4.0-GA Reporter: Tyronne Wickramarathne Assigned To: Tim Fox Fix For: 1.4.0.SP1 need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+ during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources. -- 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, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1028) Lazy transaction enlistment is not working

by Carlo de Wolf (JIRA)

Lazy transaction enlistment is not working ------------------------------------------ Key: EJBTHREE-1028 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1028 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-420) Analyze and clean up app server dependencies.

by Paul Gier (JIRA)

Analyze and clean up app server dependencies. --------------------------------------------- Key: JBBUILD-420 URL: http://jira.jboss.com/jira/browse/JBBUILD-420 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - App Server Use the maven dependency plugin to analyze the dependencies in the app server modules. Remove duplicates from app server parent pom. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3624) <security-domain> setting in deployment descriptor populates @SecurityDomain annotation incorrectly on EJB3 session beans

by David Green (JIRA)

<security-domain> setting in deployment descriptor populates @SecurityDomain annotation incorrectly on EJB3 session beans ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3624 URL: http://jira.jboss.com/jira/browse/JBAS-3624 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.4.GA Reporter: David Green Assigned To: Bill Burke Specifying a <security-domain> in the jboss-app.xml incorrectly sets the @SecurityDomain on EJB3 session beans. In the jboss-app.xml the security domain is specified as follows: <jboss-app> <security-domain>java:/jaas/hch</security-domain> </jboss-app> In Ejb3DescriptorHandler the security-domain is copied directly into the SecurityDomainImpl instance as "java:/jaas/hch", however the @SecurityDomain annotation should be populated with the value "hch" (without the leading "java:/jaas/" prefix). This causes the EJB3 session bean authentication to behave unexpectedly, since the authentication for the bean reverts to the default domain instead of the specified one. The only way I've found to workaround this issue is to specify the @SecurityDomain individually on every session bean in the project. -- 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, 9 months

5
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-341) ComponentRefGraphLicenseVisitor needs to externalize the repository url

by Scott M Stark (JIRA)

ComponentRefGraphLicenseVisitor needs to externalize the repository url ----------------------------------------------------------------------- Key: JBBUILD-341 URL: http://jira.jboss.com/jira/browse/JBBUILD-341 Project: JBoss Build System Issue Type: Bug Components: JBossBuild Reporter: Scott M Stark ComponentRefGraphLicenseVisitor always looks to URL("http://repository.jboss.com/licenses/") to obtain the license text. This should be looking to the location passed into the project build so that if can be overriden by the local build 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1117) Request for feature to close connections on server side by ip address and by connection id

by Jay Howell (JIRA)

Request for feature to close connections on server side by ip address and by connection id ------------------------------------------------------------------------------------------ Key: JBMESSAGING-1117 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1117 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Affects Versions: 1.4.0.GA Reporter: Jay Howell Assigned To: Tim Fox Several customers have asked for a management method to drop client connections from the server by ip address and by client id. So there would be two cases. By ipaddress - this would stop the pinger and also close all connections associated with that client ip address. Only one pinger exists for an ip address, so this would require closging of the pinger connection also. By clientid - this would close the pinger thread only if there are no other connections present. In each of the cases, clients should get an asynchronous onException call. The person writing the client will have to have this in mind. If a client has 1000 connections and the connection logic on the client reconnects. When the server drops the ip address, then that machine will try to reconnect all 1000 clients. I really depends on how the connection pooling on the client works. -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1022) Implement expired message reaper

by Tim Fox (JIRA)

Implement expired message reaper -------------------------------- Key: JBMESSAGING-1022 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1022 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 We should implement an expired message reaper which traverse the queues to see if messages are expired and sends them to the expiry queue. Currently we only expire messages on delivery. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3997) getManagedConnection retries

by Adrian Brock (JIRA)

getManagedConnection retries ---------------------------- Key: JBAS-3997 URL: http://jira.jboss.com/jira/browse/JBAS-3997 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Assigned To: Weston Price We should add the ability to retry getManagedConnection() when there is a resource exception from the pool. This will allow the ConnectionManagers to be more tolerant of transient failures. I'd suggest two new attributes on the connection manager, with the suggested defaults: <allocate-retry>1</allocate-retry> <allocate-retry-wait-millis>5000</allocate-retry-wait-millis> I also think the connection manager needs a "shutdown" boolean (maintained by start/stop) i.e. so don't wait 5 seconds if we get a resource exception caused by the CM/Pool getting undeployed, e.g. at JBoss shutdown. This would turn into the following *untested* code in BaseConnectionManager2: protected ConnectionListener getManagedConnection(Transaction transaction, Subject subject, ConnectionRequestInfo cri) throws ResourceException { ResourceException failure = null; if (shutdown.get()) throw new ResourceException("The connection manager is shutdown " + jndiName); // First attempt try { return poolingStrategy.getConnection(transaction, subject, cri); } catch (ResourceException e) { failure = e; // Retry? for (int i = 0; i < allocationRetries; ++i) { if (shutdown.get()) throw new ResourceException("The connection manager is shutdown " + jndiName); try { if (allocationWait != 0) wait(allocationWait); return poolingStrategy.getConnection(transaction, subject, cri); } catch (ResourceException e1) { failure = e1; } catch (InterruptedException e1) { JBossResourceException.rethrowAsResourceException("getManagedConnection retry wait was interrupted " + jndiName, e1); } } } // If we get here all retries failed, throw the lastest failure throw failure; } -- 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, 10 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007