[Design the new POJO MicroContainer] - Re: docbook build error
by alesj
This is what I currently get ...
anonymous wrote :
| C:\Java\jdk1.5.0_11\bin\java.exe -classpath C:\java_lib\maven-2.0.7\boot\classworlds-1.1.jar -Dclassworlds.conf=C:\java_lib\maven-2.0.7\bin\m2.conf -Dmaven.home=C:\java_lib\maven-2.0.7 org.codehaus.classworlds.Launcher -f C:/projects/microcontainer/docs/pom.xml generate-sources
|
|
| [INFO] Scanning for projects...
| [INFO] Reactor build order:
| [INFO] JBossMC Getting Started Guide (en_US)
| [INFO] JBossMC Getting Started Guide (aggregator)
| [INFO] JBossMC Reference Guide (en_US)
| [INFO] JBossMC Reference Guide (aggregator)
| [INFO] JBoss Microcontainer Docs
| Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plug...
| Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plug...
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] Failed to resolve artifact.
|
| GroupId: org.jboss.maven.plugins
| ArtifactId: maven-jdocbook-plugin
| Version: 2.0.0
|
| Reason: Unable to download the artifact from any repository
|
| org.jboss.maven.plugins:maven-jdocbook-plugin:pom:2.0.0
|
| from the specified remote repositories:
| central (http://repo1.maven.org/maven2)
|
|
| [INFO] ------------------------------------------------------------------------
| [INFO] For more information, run Maven with the -e switch
| [INFO] ------------------------------------------------------------------------
| [INFO] Total time: 1 second
| [INFO] Finished at: Thu Sep 13 21:40:33 CEST 2007
| [INFO] Final Memory: 1M/2M
| [INFO] ------------------------------------------------------------------------
|
| Process terminated abnormally! Exit code 1
|
What am I missing (or how to get this plugin)?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084208#4084208
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4084208
17 years, 1 month
[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Handling cluster state when network partitions occur
by manik.surtani@jboss.com
I think the primary partition approach is best. Caches not in the primary partition purging their in memory state is probably the wrong path though, since as a generic solution, not all installations will be backed by shared databases.
Caches shutting down would be my preferred option. Perhaps block for a short period, hoping the network would heal, and then throw an exception after a timeout. Perhaps a specific exception - SplitBrainException or something - so that cache users such as HTTP Replication can react by forcing an HTTP response like 410 (don't know if this is possible - Brian?) such that the load balancer will treat the node as unavailable. Once the partition heals the cache is made available to requests again after performing a state transfer to come up to speed with the primary partition.
Even the impact of incorrectly identifying a primary partition is low, since at worst case, the larger partition is unresponsive while the smaller one is. I guess the real problem is more than one partition thinking it is primary. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084139#4084139
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4084139
17 years, 1 month