Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346818 - Cannot log in to OrionHub (Chrome and Firefox)
Summary: Cannot log in to OrionHub (Chrome and Firefox)
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-22 20:52 EDT by Adrian Aichner CLA
Modified: 2011-09-01 11:42 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Aichner CLA 2011-05-22 20:52:49 EDT 
I see this problem with
Google Chrome 12.0.742.60 beta-m
FireFox 4.0
FireFox 4.0.1

Here's the beginning of one stacktrace.

I can provide full stacktrace on request.

Regards,
Adrian

HTTP ERROR 500

Problem accessing /. Reason:

    Plug-in org.eclipse.orion.server.configurator was unable to load class org.eclipse.orion.internal.server.servlets.file.EditSupportFilter.

Caused by:

org.eclipse.core.runtime.CoreException: Plug-in org.eclipse.orion.server.configurator was unable to load class org.eclipse.orion.internal.server.servlets.file.EditSupportFilter.
	at org.eclipse.core.runtime.CoreException.<init>(CoreException.java:43)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
	at org.eclipse.equinox.http.registry.internal.FilterManager$FilterWrapper.initializeDelegate(FilterManager.java:183)
	at org.eclipse.equinox.http.registry.internal.FilterManager$FilterWrapper.doFilter(FilterManager.java:172)
	at org.eclipse.equinox.http.servlet.internal.FilterRegistration.doFilter(FilterRegistration.java:67)
	at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:25)
	at org.eclipse.orion.server.configurator.servlet.WelcomeFileFilter.doFilter(WelcomeFileFilter.java:39)
	at org.eclipse.equinox.http.registry.internal.FilterManager$FilterWrapper.doFilter(FilterManager.java:173)
	at org.eclipse.equinox.http.servlet.internal.FilterRegistration.doFilter(FilterRegistration.java:71)
	at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:25)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:130)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:318)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
Comment 1 Boris Bokowski CLA 2011-05-23 01:04:22 EDT 
Thanks for reporting this. The root cause of the stack trace said something like "the workspace path is read-only". Not sure why, but it went away after a restart of the server.