It seems that, after running jetty once, a jetty.xml file is created in etc/. This file is not present in the distribution, and it creates a JAAS security context for "default" realm and not the "karaf" realm. Removing etc/jetty.xml once seems to fix the problem permanently.
The etc/jetty.xml is copyed when http feature first time get installed, you can find it from karaf features.xml
and after that it you can edit the etc/jetty.xml as you want.
The "default" realm name is obvious incorrect and should be addressed anyway, though somehow I can't reproduce the behavior you encounter.
I can't reproduce it anymore either. After changing one time it always works, even if I change the realm back to default. Perhaps it is an issue higher up with Jetty or JAAS?
But, I have seen this problem on chrome and firefox, on my 32bit workstation and my 64bit laptop (i.e. servicemix is installed and running locally on the workstation and the laptop, not just my browser hitting one servicemix installation), all running Sun's (I mean Oracle's) jdk-1.6.0_u26.
In today's release (4.4.1 01-06) I have a little problem with web console....It run for few minutes and after a while it shutdown (404 http error for any request).
I can see the jetty.xml file with 2 realm defined: karaf and default (default for applications that look for it as Achim said in https://issues.apache.org/jira/browse/KARAF-939)
Someone else can reproduce it?
I dont know if exactly the same problem that you had, Markk.
Thanks at all.
Edited by: soasoa on Oct 25, 2011 10:03 PM
You mean you can connect to webconsole previously, but for a while the webconsole doesn't work? Did you change any configuration of this FUSE ESB? Did you use "Gogo" tab from webconsole and occasionally shutdown the FUSE ESB?
Could you elaborate the steps how we can reproduce it?
I tried it but the webconsole works well for me.
Hello Freeman, thanks for response.
I couldnt authenticate in web console in 4.4.1 00-08 so I downloaded 01-06 and installed it.
Yes, I used Gogo tab and executed some instructions as osgi:list or osgi:refresh. I remember I did a shutdown but after webconsole failed and always from console windows (not from Gogo tab).
I can say my steps but I dont know if you can reproduce it:
1.- Removed jbi container support from etc/org.apache.karaf.features.cfg file.
2.- Changed some logging properties in etc/org.ops4j.pax.logging.cfg file
3.- Started servicemix.
4.- From console window, I installed webconsole feature.
5.- Authenticated with smx user and deployed a bundle.
6.- Executed some instructions in gogo as osgi:list and navigated over the webconsole tabs.
I remember the first fail was in OSGi repository tab (while searching by A, B, C... links).
Sorry can not give you more information. I'm going to install it again and write here if it occurs again with all the steps.
UPDATE: I've installed the product in mi work and started it. Web Console is running ok since 2 hours. I havent used gogo tab. I'll try it now.
UPDATE: I've executed instructions as list or refresh from gogo and everything works fine. Now, I shutdown from servicemix console, remove cache data and log file, start again......and I can reproduce it again: in 2 or 3 minutes console fail whith 404 http error !!
Edited by: soasoa on Oct 26, 2011 8:47 AM