Bug 346658

Comment 1 Wim Jongman 2011-05-20 08:13:35 EDT

What to do in this situation? It would already be a lot better for my case if there was some kind of delay when an exception occurred other then an IOException like this:



try {                                                      
	Socket socket = server.accept();                       
	if (socket == null)                                    
		throw new IOException("No socket available.  Probab ...
	FrameworkConsoleSession session = new FrameworkConsoleS ...
	framework.getSystemBundleContext().registerService(Cons ...
} catch (IOException e) {                                  
	if (!shutdown)                                         
		e.printStackTrace();                               
	try {                                                  
		Thread.sleep(500);        WAIT HALF A SECOND                         
	} catch (Exception e2) {                               
	}                                                      
} catch (Exception e) {                                    
	if (!shutdown)                                         
		e.printStackTrace();                               
	try {                                                  
		Thread.sleep(60000);      WAIT ONE MINUTE                         
	} catch (Exception e2) {                               
	}                                                      
}

Comment 2 Thomas Watson 2011-05-20 08:34:21 EDT

(In reply to comment #0)
> Hi,
> 
> We have an equinox server running with a console on a certain port. When we
> shut down the TCP/IP subsystem (this happens just before a backup) we get an
> exception loop that eventually brings equinox down.
> 
"eventually brings equinox down."  Does the equinox framework eventually shutdown?  Is it in the middle of shutting down but the this thread is taking up all the CPU causing it to take a long time to shutdown?

(In reply to comment #1)
> What to do in this situation? It would already be a lot better for my case if
> there was some kind of delay when an exception occurred other then an
> IOException like this:
> 

A delay may help if the issue is this thread running wild with the CPU while the rest of the framework is shutting down.  I wonder if we could detect that many rapid failures have occurred and we should either start delaying or completely shut the console socket thread down.

Comment 3 Wim Jongman 2011-05-20 11:32:53 EDT

(In reply to comment #2)

> "eventually brings equinox down."  Does the equinox framework eventually
> shutdown?  Is it in the middle of shutting down but the this thread is taking
> up all the CPU causing it to take a long time to shutdown?

The log files are filling up and the job is killed after it reaches a certain amount of storage. In Windows or Unix it would just crunch away CPU and fill the log files until disk space is full? All depending on the log settings of course.

> 
> A delay may help if the issue is this thread running wild with the CPU while
> the rest of the framework is shutting down.  I wonder if we could detect that

The framework is not shutting down in my case. It just needs to run without networking for a certain period of time. 

> many rapid failures have occurred and we should either start delaying or
> completely shut the console socket thread down.

It would be nice if the socket could be activated soon after the network stack is back online.

Comment 4 Eclipse Genie 2019-09-15 19:08:02 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.