Thanks for the responses! > It does take a little while before ACE is fully running, even after all bundles > have been started. If you wait a while, you will see some additional messages > appear. When ACE has fully started, the web UI should be visible on the > mentioned address. If this takes more than a minute (on current hardware) > something is wrong, and maybe, as Jean Baptiste said, something else is running >on port 8080?
I have edited platform.properties and set -Dorg.osgi.service.http.port=8111 and restarted the server. I get the same results. Netstat -a does not show anything listening on port 8111 (or 8080) until I issue a command in Gogo. (I just use 'help') even after waiting 10 minutes. Within 5 seconds of issuing the Gogo command, the port becomes Listened to. I then waited 15 minutes for the server get fully warmed up. Still 404 response on http://loalhost:8111/ace > "stop 0" will stop the system bundle and therefore the OSGi framework. I never > did understand why Gogo does not add an alias like "quit" or "exit" to make > that easier for the user. I issued a stop 0 command in Gogo, but nothing happens When I issue a second stop 0 command, it reports Bundle org.apache.felix.framework [0] cannot be stopped since it is already stopping. After 30 minutes, I used a <cntrl-C> to stop it. Any recommendations on how to proceed? Seems pretty strange to me, the build and tests all appeared to be fine. I am running on Windows XP SP3 on an Lenovo ThinkPad T410 (quad core 2.6Ghz with 3Gb RAM) java version "1.6.0_23" Java(TM) SE Runtime Environment (build 1.6.0_23-b05) Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing) Thanks Wayne Irwin I.S.P. <http://www.cips.ca/isp> ITCP <http://www.cips.ca/itcp> Senior Infrastructure Specialist Application Integration Solution Centre (AISC) Great-West Life Assurance Company 60 Osborne Street North Winnipeg, MB Canada R3C 1V3 Tel (204) 946-7999 www.GreatWestLife.com <http://www.greatwestlife.com/> The contents of this communication, including any attachment(s), are confidential and may be privileged. If you are not the intended recipient (or are not receiving this communication on behalf of the intended recipient), please notify the sender immediately and delete or destroy this communication without reading it, and without making, forwarding, or retaining any copy or record of it or its contents. Thank you. Note: We have taken precautions against viruses, but take no responsibility for loss or damage caused by any virus present.
