-
Committer:
Scott Moser
-
Date:
2011-11-22 04:26:44 UTC
-
Revision ID:
smoser@ubuntu.com-20111122042644-mgdxrrkpuibowcc6
remove 'seed-cache' for all regions
it seems that 'seed-cache ${regions[@]}' was to much for the build
system. This actually doesn't change anything, significant. It just means
that we don't generate the cache in parallel, but rather serially on first
access.
More than once I saw failures like:
Unexpected error:
org.codehaus.xfire.fault.XFireFault: Can't overwrite cause
at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
at org.codehaus.xfire.client.Client.onReceive(Client.java:410)
at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
...
at org.codehaus.xfire.service.binding.DocumentBinding.readMessage(DocumentBinding.java:35)
at org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Client.onReceive(Client.java:406)
... 14 more