Bugzilla – Full Text Bug Listing
| Summary: | Port Conflict Crash doesnt self clean properly | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | MadTom1999 <madtom1999> |
| Component: | Server | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
MadTom1999
What browser were you using? I am definitely seeing problems on Chrome doing the following: 1) Start orion 0.3 on port 8080 2) Open Chrome and point to localhost:8080. Leave it open. 3) Stop the server 4) Start another server, such as self-hosting latest orion server 5) Back in Chrome, hit F5 to refresh. -> Chrome insists on using its cached copy not matter what kind of refreshing you do. You need to aggressively clear your chrome cache before it will load properly. I don't think this is a problem of the server not cleaning up properly ,but the combination of browser client caching and switching to a different server at the same address. I was using firefox 3.6... I don't think it can be the browser: The problem arose thus: orion is started on a used port and then crashes in desktop space - no browser connection was attempted so no caching. a new port is chosen and then orion re-run and the browser connected to a blank page. If the bash session was closed and restarted then the orion Welcome page comes up. I've just tried to replicate but cant - I cant even get it to crash on a used port! But I do have a working orion so it may have passed some initiation point? If I get time I'll try later on a different machine Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |