[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
16 years, 1 month
[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
16 years, 1 month