Opened 16 months ago

Closed 16 months ago

Last modified 13 months ago

#1458 closed defect (fixed)

The timeout when executing a command seems to not work

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone: Job scheduler extension v1.9
Component: net.sf.basedb.opengrid Keywords:


The AbstractSession.execute() method has a timeout parameter which is the longest time we want to wait for the command to timeout. It seems like this is not working as expected. If a timeout occurs the method will throw a TimeoutException, but will then go into the finally part that is closing the session. It seems like the close() method will wait until the command finishes.

Change History (2)

comment:1 by Nicklas Nordborg, 16 months ago

Owner: set to Nicklas Nordborg
Resolution: fixed
Status: newclosed

In 7028:

Fixes #1458: The timeout when executing a command seems to not work

It turned out that there is a timeout on the Connection implementation that is different from the other timeouts. Decreasing this timeout will make the close() method return faster.

But before we close the connection we can send a TERM signal to the remote process and hopefully it should terminate gracefully.

With both options in place I think the timout now should be close to what is expected.

comment:2 by Nicklas Nordborg, 13 months ago

Milestone: Job Scheduler extension v1.9Job scheduler extension v1.9

Milestone renamed

Note: See TracTickets for help on using tickets.