nstead of manually implementing the
locking, or why the "Suppliers.memoizeWithExpiration" isn't used
instead, which is thread-safe too.
HTH!
I.
[1]
https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/suppliers/LocationIdToURIFromA
Hi,
I've been seeing this warning pop out of my code for awhile and have
finally gotten around to investigating it:
org.jclouds.location.suppliers.implicit.GetRegionIdMatchingProviderURIOrNull|_ThreadID=10;_ThreadName=Thread-2;|failed
to find key for value http://keystone.domainname.com:5000/
ueprint [1]; I don't know the state of
the art of Openstack and if that field is still returned or not).
* AND you use the "ContextBuilder.apiVersion" method to force the
version you want.
HTH,
I.
On 5 January 2017 at 20:33, Ryan Shoemaker
wrote:
Hi,
I'm hoping to get a bett
Hi,
I'm hoping to get a better understanding of how jclouds discovers and
decides which identity endpoint to use. Feel free to redirect me to
docs if this is already written up somewhere.
In my case, we have a community Mitaka installation running and an app
that uses jclouds v2.0.0. Initi
ra wrote:
Hi Ryan,
Apologies for the late reply.
Unfortunately there is no such helper. The current jclouds portable
model does not have those minimum requirements represented in the
Image entity (which would be a nice to have, btw) so there is no
portable filter yet.
I.
El 7 jun. 2016 9:33 p.
Hi,
Is there a built-in helper method that returns only those flavors
meeting the minimum requirements specified by a given image?
Thanks,
--Ryan
Hi,
Is there a reliable way to determine when a node has finished rebooting?
I started off writing my own reboot method that execs an "init 6" on the
node and then polls port 22 using a retry predicate to figure out when
the network service goes away and then comes back. I'm not a crazy
abou
On May11 11:30 AM, Andrew Phillips wrote:
Thanks Ignasi and Andrew.
I spent some time on Friday changing the code to work as you suggested
and the app is behaving much better.
Glad to hear! Could you have a quick look at the updated advice in:
http://jclouds.apache.org/start/concepts/#context
On May6 8:15 PM, Andrew Phillips wrote:
context-scoped) etc, so in general, I'd say you try to create a
context just once and reuse it when possible, and configure the thread
pool size to fit your app needs.
See also this old thread:
https://groups.google.com/forum/#!topic/jclouds/pF9ZqXPdLTk
operty in order to have more control on the
size of the thread pool.
HTH!
I.
[1]
https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/Constants.java#L26-L31
[2]
http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Executors.html#newCachedThreadPool()
On 6 Ma
, Ryan Shoemaker wrote:
Hi Ignasi,
I've attached the test code, including the quick&dirty thread set
comparisons. You can strip that out and just watch the threads via
jconsole or some other monitoring app if you prefer.
Thanks,
--Ryan
On May6 3:44 AM, Ignasi Barrera wrote:
Hi R
complete test code, including how you create the
jclouds context and the loop you're using, so I can run it to
reproduce the issue?
Thanks!
I.
El 05/05/2015 21:11, "Ryan Shoemaker" <mailto:ryan.shoema...@enterprisedb.com>> escribió:
Hi,
I'm running
Hi,
I'm running jclouds 1.8.0 with Guava 17.0 and I'm seeing threads
allocated every time I create an SshClient, but they are never released
and eventually pile up until the JVM can't allocate any additional
threads (java.lang.OutOfMemoryError: unable to create new native thread).
I hacked j
13 matches
Mail list logo
