?As far as I know this fix should have been in 1.9.0, so I'm surprised it's not.
________________________________ From: Forrest Townsend <forrest.tow...@gmail.com> Sent: Wednesday, May 6, 2015 6:32 PM To: user@jclouds.apache.org Subject: COMMERCIAL:Re: Openstack keystone swift token expiration I have already voted for this bug report haha :) Thank you for your comments! Unfortunately I am not in a situation right not to run with 2.0.0, but if I have some down time I will try and comment back on https://issues.apache.org/jira/browse/JCLOUDS-615. Thanks, Forrest T. On Wed, May 6, 2015 at 3:32 PM Ignasi Barrera <n...@apache.org<mailto:n...@apache.org>> wrote: Hi Forrest, If I'm not wrong you're hitting https://issues.apache.org/jira/browse/JCLOUDS-615. If that is the case, there is a comment indicating that is fixed in 2.0.0-SNAPSHOT. Could you confirm that? Let's help us test this and add you feedback (and vote) to the issue. HTH! I. On 6 May 2015 at 23:41, Forrest Townsend <forrest.tow...@gmail.com<mailto:forrest.tow...@gmail.com>> wrote: > Hi > > I am running with jclouds version 1.8 and was curious if any other people > have been hitting the default 60 minute token expiration. If someone has > experienced this, what is a known work around? I know this isn't an > openstack email list but but if you [1] issue a new connection to openstack > through jclouds, will this recreate a new token? Or [2] would it be better > to close the current connection and then connect again? > > [1] CloudWrite( ... ) > { > .. > .. > putBlob( ... ); > > rc = handle an exception from put; > > if rc equals any kind of fail > connect( ... ) > retry putBlob( ... ) > > } //end CloudWrite > > or > > [2] CloudWrite( ... ) > { > .. > .. > putBlob( ... ); > > rc = handle an exception from put; > > if rc equals any kind of fail > close cloud connection > connect > retry putBlob( ... ) > > } //end CloudWrite > > > > Thanks, > Forrest T. > >
