| Summary: | reams of NPEs logged by SimpleUserCredentialsService on startup | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Rafael Chaves <eclipse> |
| Component: | Server | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ken_walker |
| Version: | 4.0 | ||
| Target Milestone: | 4.0 RC3 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Rafael Chaves
(In reply to Rafael Chaves from comment #0) > Trying to open with 4.0RC1 an workspace that was started with 1.0RC2 leads > to dozens (hundreds?) of exceptions like the one below. The server stays up > though. Orion 3.0 doesn't complain about the same workspace at all. SimpleUserCredentialsService should not be starting at all unless you turn it on. This is fixed with Bug 418621. At some point we will want to migrate your Orion storage to the Orion 4.0 format. You are saying you created an Orion storage using 1.0 and have been updated over time using the same storage with 2.0, 3.0 and now 4.0? I should be able to download these builds and test. I dug further trying to reproduce this with a new workspace and turns out it is not triggered by old metadata, but by this setting in orion.conf: #uncomment this line to use hierarchical user content layout based on user id orion.file.layout=userTree I can reproduce this issue with a brand new workspace by having this setting enabled in orion.conf. Once triggered, I can shutdown and comment out the setting again, and the issue will happen in again in following startups. This problem has been resolved by the fixes in: Bug 419232 [server] MetaStore migration does not handle Orion 0.2 metadata Bug 419176 [server] Runtime exception thrown with orphan files in the Orion repository |