Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365162

Summary: Blank Page on startup
Product: [ECD] Orion Reporter: MadTom1999 <madtom1999>
Component: ServerAssignee: Project Inbox <orion.server-inbox>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3    
Version: 0.3   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description MadTom1999 CLA 2011-11-30 02:20:17 EST
Install Downloaded eclipse-orion-0.3RC2-linux.gtk.x86_64.zip (or ..0.3-lin...)
run orion on port 8081 - crashes
---------------------------------------------------------------------------
JVM terminated. Exit code=15
/usr/bin/java
-Dorg.eclipse.equinox.http.jetty.http.port=8081
-Dorg.eclipse.equinox.http.jetty.autostart=false
-Xms40m
-Xmx384m
-jar /home/tom/Projects/eclipse//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-os linux
-ws gtk
-arch x86_64
-launcher /home/tom/Projects/eclipse/orion
-name Orion
--launcher.library /home/tom/Projects/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so
-startup /home/tom/Projects/eclipse//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata 369002f
-consoleLog
-console
-data serverworkspace
-vm /usr/bin/java
-vmargs
-Dorg.eclipse.equinox.http.jetty.http.port=8081
-Dorg.eclipse.equinox.http.jetty.autostart=false
-Xms40m
-Xmx384m
-jar /home/tom/Projects/eclipse//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
----------------------------------------------------------------------------
modify orion.ini to port 8085 it runs - with a few messages
call localhost:8085 and get a blank page titled 'Welcome to Orion'
the page has content but not shown - firefox Error Console complains about defaults.pref being badly formed.
Comment 1 MadTom1999 CLA 2011-11-30 02:49:08 EST
It seems that the error is due to something still running or a port locked after the first IP conflict crash. 
On running on a new machine and changing the port in orion.ini before starting the app seems to run as expected.
On the original machine logging out the user and restarting on a clear port seems to produce the desired result also.
This may require a different bug report...