You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/04/29 18:45:32 UTC

[GitHub] [accumulo-examples] Manno15 commented on issue #45: reservations example fails

Manno15 commented on issue #45: reservations example fails
URL: https://github.com/apache/accumulo-examples/issues/45#issuecomment-487697448
 
 
   I took a look at this and it appears the reason why the client is closing is because the try-block around the client initialization closes right after connecting. 
   
   What would be the best solution? I have tried some reformatting of ARS.Java but with the way it is structured currently to take in user arguments makes that a bit more complicated of a solution. I could also separate the connect feature to a function on its own so the other functions (like reserve) can check on connection status and then reconnect if need be. That seems more like a workaround than a clean solution so I am hesitant on doing that. Since this is an example, we could remove the try-block for the client connection and then call client.close() somewhere else if required. Any other ideas?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services