Opened 9 years ago
#1431 new defect
DRMAA can "reconnect" with a bogus session key
Reported by: | dlove | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 8.1.1 |
Severity: | minor | Keywords: | |
Cc: |
Description
Am 15.08.2012 um 15:11 schrieb Dave Love:
Reuti <reuti@…> writes:
PS: Interesting, that you can specify also a session_id with a random
number (i.e. reconnect to a never existing session), and you can use
it for further submissions (behaves like illegal session id = create a
new one with this number). And even two programs can connect to the
same session.
That sounds wrong. Do you have an example to hand to paste into the
tracker?
I used a variation of the demos which are included with SGE (see attached). You can change (at least the last number) to anything you like.
There are no jobs left for this session to be deleted, but this is already after the (successful) reconnect.
I was just wondering: how long can you reconnect? I didn't find any answer in DRMAA documents.
-- Reuti
Added by email2trac