Re: [equinox-dev] Thousands of exceptions during boot, yet application i

["Thomas Watson" <tjwatson@xxxxxxxxxx>]

Moving discussion over to forum:  
https://www.eclipse.org/forums/index.php?t=rview&goto=1744897#msg_1744897

Tom





From:      
 Michal Siemaszko <michal.siemaszko@xxxxxxxxxx>
To:      
 Equinox development
mailing list <equinox-dev@xxxxxxxxxxx>
Date:      
 10/03/2016 09:09 AM
Subject:    
   Re: [equinox-dev]
Thousands of exceptions during boot, yet application is running - harmless
or symptom of issues which should be solved?
Sent by:    
   equinox-dev-bounces@xxxxxxxxxxx

---

Hi Tom, 

Thank you for your reply. 

I really was not trying hard to find problems,
the only reason I hit these is because I need to debug remaining issues
which prevent upgraded version of said application from running. The only
tools (that I know of) at my disposal are breakpoints and osgi.debug; my
reasoning was (and still is) that the underlying cause of these can be
caught by looking at these, since by the time logging layer is initialized,
only symptoms are visible. I did start with setting breakpoints in 'org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader'
(in catch blocks of #loadClass and #getResource methods), but then started
hitting those existing exceptions by the thousands, then when osgi.debug
was enabled all these stack traces were dumped to text file and are being
analyzed. 

I see many of the stack traces (visible
only in osgi.debug, or when hitting bps in DefaultClassLoader) then manifest
as actual failures visible once logging layer kicks in (same classes, etc.)

Since file generated from osgi.debug is
over 60 MB and there are over 3300 exceptions, sharing these is not really
possible at this point. 

Are there any other settings in osgi.debug
or config.ini that could be turned on (many of these are not documented/hard
to come across) that could help in properly diagnosing these issues? 

Regards, 
Michal

---

From: equinox-dev-bounces@xxxxxxxxxxx
<equinox-dev-bounces@xxxxxxxxxxx> on behalf of Thomas Watson <tjwatson@xxxxxxxxxx>
Sent: Monday, October 3, 2016 2:58:25 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Thousands of exceptions during boot, yet
application is running - harmless or symptom of issues which should be
solved? 
 
It is hard to tell if the exceptions
are issues to be concerned about without having one as an example.  It
is possible that enabling debug is just printing out some benign exception
that is otherwise ignored by the system and not logged.

Yes Equinox should easily handle 1000s of bundles being installed.  There
are many Eclipse based products that do just that.

Tom





From:        Michal
Siemaszko <michal.siemaszko@xxxxxxxxxx>
To:        "equinox-dev@xxxxxxxxxxx"
<equinox-dev@xxxxxxxxxxx>
Date:        10/01/2016
06:15 PM
Subject:        [equinox-dev]
Thousands of exceptions during boot, yet application is running - harmless
or symptom of issues which should be solved?
Sent by:        equinox-dev-bounces@xxxxxxxxxxx

---

Hi, 

I'm working on upgrading a legacy application which uses Equinox as its
OSGi runtime. When booted and running, there are close to a thousand bundles
loaded in the container. 

Since I'm working on upgrading significant parts of the application, and
debugging issues still present during boot, I discovered thousands of exceptions
present in the existing (trunk/production version, not the upgraded one)
of the application after enabling osgi.debug. 

Is seeing so many exceptions - e.g. ClassNotFound exceptions - during boot
in an application which does boot however and runs, is normal? Or is it
a symptom of issues which should be addressed and might come out when -
e.g. now - parts of the application are being upgraded and many new bundles
added and a critical point is reached where application simply will not
start until underlying reason for this is solved? 

Is Equinox OSGi well suited for running applications consisting of close
to a thousand bundles? Are there any potential resource bottleneck related
issues which should be considered in such large OSGI applications? 

I will greatly appreciate your input, since I have not found much - or
nothing at all - regarding issues which could cause such.

Regards,
Michal
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev