February 2009 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: The DeploymentManager and ProfileService

by emuckenhuber

"scott.stark(a)jboss.org" wrote : | 1. The JBossEmbeddedAS needs to accept richer input to allow metadata such as the inmemory deployment information. | https://jira.jboss.org/jira/browse/EMB-19 | Hmm inmemory deployment - so that you don't need to create a physical jar? Wouldn't that then be just another Profile implementation which actually creates the deployments? I guess @Profile would be similar to the sub-profile in xml then - where you basically just choose a required profile for the unit test? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207444#4207444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207444

15 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Deployment cleanup & modifications

by alesj

"alesj" wrote : | Does this look legit enough? | This needs more work, as sub-deployments don't have Deployment instance. I'll dig further. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207438#4207438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207438

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: UUIDGenerator broken on Windows...

by clebert.suconic＠jboss.com

This fake adapter will have the same MAC on every Windows installed out there: Just found a post on Technet, with the same MAC listed. So it is definetely not unique. As Jeff said, we will need to blacklist that MAC: http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thre... MAC Addresses were supposed to be unique.. right? So.. why M$ did it this way? But oh well.. that's an issue for sure. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207392#4207392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207392

15 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Deployment cleanup & modifications

by alesj

"alesj" wrote : | We need to move "Deployment::hasBeenModified" off the VFSDeploymentContext. | I guess some combination of VFSDeployment and VFSDeploymentContext's metadata locations. | | I'll see what can be done ... | | Does this look legit enough? | Index: src/main/org/jboss/system/server/profileservice/repository/MutableDeploymentRepository.java | =================================================================== | --- src/main/org/jboss/system/server/profileservice/repository/MutableDeploymentRepository.java (revision 83887) | +++ src/main/org/jboss/system/server/profileservice/repository/MutableDeploymentRepository.java (working copy) | @@ -37,8 +37,10 @@ | import java.util.concurrent.locks.ReentrantReadWriteLock; | import java.util.zip.ZipInputStream; | | +import org.jboss.deployers.client.spi.Deployment; | import org.jboss.deployers.structure.spi.DeploymentContext; | import org.jboss.deployers.structure.spi.main.MainDeployerStructure; | +import org.jboss.deployers.vfs.spi.client.VFSDeployment; | import org.jboss.deployers.vfs.spi.structure.VFSDeploymentContext; | import org.jboss.profileservice.spi.DeploymentContentFlags; | import org.jboss.profileservice.spi.ModificationInfo; | @@ -320,9 +322,19 @@ | */ | protected boolean hasBeenModified(VFSDeploymentContext deploymentContext, boolean checkRoot) throws IOException | { | + Deployment clientDeployment = deploymentContext.getDeployment(); | + if (clientDeployment instanceof VFSDeployment == false) | + { | + if (log.isTraceEnabled()) | + log.trace("Deployment is not VFS based: " + clientDeployment); | + return false; | + } | + | + VFSDeployment deployment = VFSDeployment.class.cast(clientDeployment); | + VirtualFile root = deployment.getRoot(); | + | if (checkRoot) | { | - VirtualFile root = deploymentContext.getRoot(); | // no need to check metadata locations if archive or root | if (root.isArchive() || root.isLeaf()) | return root.hasBeenModified(); | @@ -338,15 +350,20 @@ | { | for(VirtualFile child : children) | { | - String pathName = child.getPathName(); | - Long timestamp = lastModifiedCache.get(pathName); | - long lastModified = child.getLastModified(); | - lastModifiedCache.put(pathName, lastModified); | - if (timestamp != null && timestamp < lastModified) | + // get client side metadata - if exists | + VirtualFile clientChild = getClientChild(root, child); | + if (clientChild != null) | { | - if (log.isTraceEnabled()) | - log.trace("Metadata location modified: " + child); | - return true; | + String pathName = child.getPathName(); | + Long timestamp = lastModifiedCache.get(pathName); | + long lastModified = clientChild.getLastModified(); | + lastModifiedCache.put(pathName, lastModified); | + if (timestamp != null && timestamp < lastModified) | + { | + if (log.isTraceEnabled()) | + log.trace("Metadata location modified: " + clientChild); | + return true; | + } | } | } | } | @@ -368,6 +385,21 @@ | } | | /** | + * Get client side child. | + * | + * @param root the client root | + * @param child the server child | + * @return matching client child if exists | + * @throws IOException for any error | + */ | + protected VirtualFile getClientChild(VirtualFile root, VirtualFile child) throws IOException | + { | + String rootPathName = root.getPathName(); | + String childPathName = child.getPathName(); | + return root.getChild(childPathName.substring(rootPathName.length())); | + } | + | + /** | * Cleanup last modified cache for path name. | * | * @param pathName the path name | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207385#4207385 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207385

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: split-brain between live and backup node

by timfox

Yes, we know that split brain can occur, that's why the task exists in the first place! The task is to prevent duplicate deliveries in a split brain situation, not try and convince me that it can occur, I already know that...;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207379#4207379 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207379

15 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Too strict pattern matching in PackageClassFilter

by scott.stark＠jboss.org

That looks to be by design. We should have a RecursivePackageClassFilter or allow package wildcards like javax.servlet.* to indicate the javax.servlet package or any of its subpackages. I think the single package interpretation is consistent with the osgi bundle class loader behavior, so we would have to have an extension to that. I'll have to look at how the filteredPackages information is incorporated into the class loader model because it could simply be that is where the behavior could be extended. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207378#4207378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207378

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: split-brain between live and backup node

by jmesnil

that's not the use case I described: the backup server never goes down. My use case is that the live node server is temporarily offline and a client fails over to the backup server. What happens when the live node is online again and clients connect to it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207377#4207377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207377

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: split-brain between live and backup node

by timfox

If the backup server really has gone down, and is brought back up, it can no longer be the backup server, since it's state is no longer synchronized with the live. If it's a transitory failure of short enough duration, then we can just add reconnection attempts like any other connection. However while the server is down any replications will be blocked which might cause clients to block and timeout. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207375#4207375 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207375

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: split-brain between live and backup node

by jmesnil

"timfox" wrote : "jmesnil" wrote : | | In the code, I've not seen any heartbeat between the live node and the backup node. L1 will never be informed when it can reach B1 again. | | B1 as the original backup never checks connectivity to the original live node L1 | | | | | | There is a heartbeat, like any normal connection yes, bad wording of mine. I meant that once L1 has been informed that it is no longer connected to B1, it will not be informed when the connection is up again. I'll write a test case to illustrate this case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207374#4207374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207374

15 years, 4 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Struts integration withjBPM

by mark.little＠jboss.com

wrong forum. take it to the jBPM forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207373#4207373 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207373

15 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2009