That is normal and expected. You should also have seen a line like this:
10:07:26,241 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBos
s_4_2_1_GA date=200707131605)] Started in 2m:40s:173ms
At this point, open a browser and point it at http://localhost:8080/portal and you should be all set to go.
Thanks for your help.
I did not realize that I had to keep the install window (for Run.bat) open to keep the jboss server running.
Yes, when you close the command prompt window, all applications started in the window are also closed. Its the way Windows works (actually, Linux does the same, though there are ways around it).
You can set up the app server to run as a service (that way there is no command window hanging around), see http://wiki.jboss.org/wiki/Wiki.jsp?page=RunJBossAsAServiceOnWindows. I recommend using JBoss native.
I am having the same issue except that when I try to access the portal at http://localhost:8080/portal I am not getting a page. I have not yet found any obvious errors - any ideas? Netstat does not show anything using port 8080 (this is on linux).
the process appears to be running:
java -Dprogram.name=run.sh -server -Xms128m -Xmx512m -D ....
and the open process window shows:
12:49:17,530 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 48s:469ms
12:49:18,825 INFO [RegistrationInfo] The producer didn't require any specific registration properties
12:49:18,826 INFO [RegistrationInfo] Using default registration data for producer 'self'
12:49:18,832 INFO [ProducerInfo] Refreshed registration information for consumer with id 'self'
12:54:19,006 INFO [ProducerInfo] Refreshed registration information for consumer with id 'self'
but no page for me.
Does anyone have any ideas?
thanks in advance!
jamesmrush, you should have started a new topic, not appended to an existing one, especially since your problem is not related to the original problem posted.
Are you able to access the home page or the jmx console? Try http://localhost:8080 and http://localhost:8080/jmx-console.
Are you starting the app server with a -b option (such as run -b 0.0.0.0)?
Which version of the Portal are you running? Are you running the app server + portal bundle, or did you install the app server and portal separately? If you are not using the bundle, what database are you using?
Are there any stack traces in the terminal window? (You might have to increase the history/buffer size to scroll all the way back to where you started the app server.)
mfb said his "install" was hangind on:
[ProducerInfo] Refreshed registration information for consumer with id 'self'
I am seeing the same thing. Main (only) difference appears to be that when he tried to access localhost:8080 he actually got something.
I am running the jboss-portal-2.6.2.GA bundle (AS plus portal).
I cannot access http://:8080 or /portal or /jmx-console
I am just running the run.sh as-is, have made no modifications.
No stack traces visible, it actually looks pretty clean.
Should I re-submit as a fresh forum note?
It is not "hanging", that is simply the last message logged at the time. As you access various applications, there might or might not be further logging output (Seam and Hibernate generate lots of logging, so does JSF, but other things don't generate any logging output).
mfb's issue was that he closed the console, thus bringing down the app server, and the portal. I assume that you did not close the terminal you used to start the app server.
Right before the "Started in 99s" message, there should be another message that looks like this:
13:34:27,879 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
Post the "Starting Coyote HTTP" message that you have.
When you replied to my post, you used URL "http://:8080". Did you actual enter the exact text "http://localhost:8080" or did you enter something else?
Let's just continue the discussion here, that is better than breaking off into another thread at this point.
I have figured it out, it was staring just fine, I was trying to access the page at http://machinename/portal instead of (literally) localhost. I fixed this by using ./run.sh -b 0.0.0.0 to start the process.
thanks for the help!