Hi Bertrand,
While I have not taken thread dumps, I do not believe that my system is
stuck in a loop as I can access the normal karaf instance with a remote
client and see that all bundles are resolved and working. Problem
appears to only affect the webconsole at the 'home' url to felix.
A little more background as to what I am doing, may highlight the
problem better.
My karaf host system is a Debian live running on a headless compact
flash based intel (like) processor. The Debian OS live boots to a
memory based disk, so each boot of the system is to a pristine OS
state. The karaf framework 1.2.0 is configured to start as a service.
The system sole purpose is to host felix-karaf and the main interaction
with the system is via the webconsole (ssh if this fails).
The only variable that I see for the working attempts versus the not
working attempts is the time lag between when the system boots up to
when I browse to the console. (I am not counting the seconds so
perhaps I am requesting a page at a particularly bad time which causes
the failure? Although I have waited at varying lengths and I still do
not discern a pattern based on length of duration.)
Should mention that even when I do get a blank page at the
http://hostname:8080/system/console/bundles url I can go to a parent
path of that url and get a jetty error telling me the page is not
accessible. From that I also see that Jetty is working.
I am running Firefox as my browser - wonder if there is a browser /
webconsole issue here someplace?
thanks for your help,
John
Bertrand Delacretaz wrote:
Hi,
On Fri, Feb 26, 2010 at 2:25 AM, John E. Conlon <[email protected]> wrote:
Have been experiencing an intermittent hanging problem when I try to connect
to a felix web console. By hanging I mean - connecting to the url produces a
blank webpage - no errors just a blank page. Sometimes it works and other
times not (its around a 50% failure rate.) When I make a connection to a
newly started framework's webconsole and I get a hang the only thing I can
do is to restart the framework. (I am using Karaf with felix)...
Could it be that your system is stuck in a loop like FELIX-1967 ?
I've seen similar symptoms when experiencing that problem, the console
appears to be stuck because it's waiting on locks that are held for a
very long time due to Resolver.findConsistentClassSpace running in
circles.
If that's the case, thread dumps every few seconds would show that
method active at various stages, and CPU usage would be high.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
