Task #3191 (closed)
Opened 14 years ago
Closed 12 years ago
Bug: DeleteCallbackI "hangs" on connection refused
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-4.4 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | cneves, cxallan, jburel, atarkowska, wmoore |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | 2012-01-17 (6) |
Description
This is a loop until it's closed:
WARNING:omero.api.DeleteCallback:Error calling DeleteHandlePrx.close: 2abb98a2-fe12-4bba-a0b8-093ccb30caa2/DeleteHandled80699c1-2194-4953-80b7-06e60fa2bddf -t:tcp -h 134.36.65.228 -p 34577
Traceback (most recent call last):
File "/home/omero/OMERO.server-4.2.1-DEV-r8401-trunk1147/lib/python/omero/callbacks.py", line 170, in close
self.handle.close() # ticket:2978
File "/home/omero/OMERO.server-4.2.1-DEV-r8401-trunk1147/lib/python/omero_api_IDelete_ice.py", line 234, in close
return _M_omero.api.delete.DeleteHandle._op_close.invoke(self, ((), _ctx))
UnknownLocalException: exception ::Ice::UnknownLocalException
{
unknown = Network.cpp:1220: Ice::ConnectionRefusedException:
connection refused: Connection refused
}
Change History (6)
comment:1 Changed 14 years ago by jmoore
- Owner set to jmoore
comment:2 Changed 14 years ago by jmoore
- Remaining Time set to 0.25
comment:3 Changed 14 years ago by jburel
- Sprint changed from 2010-10-28 (18) to 2010-11-11 (19)
comment:4 Changed 13 years ago by jmoore
- Milestone changed from OMERO-Beta4.2.1 to Unscheduled
- Sprint 2010-11-11 (19) deleted
I'm not sure of the best thing to do in the case of a "connection refused" exception. It most likely means that the server is down, but it could just be a temporary network issue. Most likely we need to introduce an error handling strategy which checks the server, etc. etc. Pushing.
comment:5 Changed 12 years ago by jmoore
- Cc cneves-x cxallan wmoore added
Anyone have any thoughts on whether we handle this now and how?
comment:6 Changed 12 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Remaining Time changed from 0.25 to 0
- Resolution set to invalid
- Sprint set to 2012-01-17 (6)
- Status changed from new to closed
In discussion with Jean-Marie and Chris, we haven't seen this recently (original issue was with 4.2.1). If anyone can reproduce, please re-open. In order to more generally fix this issue, I've marked #2485 as a bug.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moved from sprint 2010-10-28 (18)