[JBoss JIRA] Created: (JBMICROCONT-175) Move incomplete deployment checking into MainDeployer
by Scott M Stark (JIRA)
Move incomplete deployment checking into MainDeployer
-----------------------------------------------------
Key: JBMICROCONT-175
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-175
Project: JBoss MicroContainer
Issue Type: Feature Request
Affects Versions: JBossMC_2_0_0 Beta3
Reporter: Scott M Stark
Fix For: JBossMC_2_0_0_CR1
Currently all users of the MainDeployer.process have to externally code something like:
protected void checkIncomplete() throws DeploymentException
{
IncompleteDeployments incomplete = IncompleteDeploymentsBuilder.build(mainDeployer, controller);
if (incomplete.isIncomplete())
throw new IncompleteDeploymentException(incomplete);
}
to see if the last process has any deployments in an incomplete state. It would be better if this logic was passed in as a listener with helper implementations for the typical check to avoid this duplication and need to inject kernel controller.
--
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
17 years, 6 months
[JBoss JIRA] Closed: (JGRP-170) upTbl should be cleared in _upViewChange()
by Bela Ban (JIRA)
[ http://jira.jboss.com/jira/browse/JGRP-170?page=all ]
Bela Ban closed JGRP-170.
-------------------------
Resolution: Out of Date
TOTAL was canned in 2.5
> upTbl should be cleared in _upViewChange()
> ------------------------------------------
>
> Key: JGRP-170
> URL: http://jira.jboss.com/jira/browse/JGRP-170
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.2.9, 2.2.9.1, 2.2.8
> Reporter: Bela Ban
> Assigned To: Bela Ban
> Fix For: 2.x
>
>
> upTbl should be cleared in _upViewChange().
> Say there are three nodes A,B,C. Suppose there are 10
> outstanding TOTAL sequences say 1-10 (1-5 from A and
> 6-10 from B). Say seq#1 is missing so we have 2-10 in
> every upTbl.
> Now assume the view changes and A and B replayBcast
> (). This time A gets 6-10 and B gets 1-5.
> A lot can go wrong now, say if A's sequences reach in
> reverse order. We have duplicate transmissions from A.
> Its also possible that B's transmission is totally lost.
> I haven't verified all possible scenarios here, but I think
> the above two are quite possible.
--
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
17 years, 6 months