Railo 3 hung, was: Re: What's a site like this one worth?

Larry Lyons wrote: > there are now two free and open source versions of the CF engine, OpenBlueDragon and Railo 3.1 (to be released very shortly). I installed and tried to run Railo 3 tonite. I ran the program using the string "sh start.bat" ... it listed a few hundred lines in Terminal, then seemed to get hung up. Err ... lost? These may be a good alternative for you. > > since you've a bit of experience with CF you may want to get John Farrar's book The ColdFusion 8 Developer's Tutorial. Its very good for getting up to speed with CF 8. > http://www.amazon.com/ColdFusion-Developer-Tutorial-John-Farrar/dp/1847194125/ref=pd_bbs_sr_4?ie=UTF8&s=books&qid=1232113937&sr=8-4 I'll look into it ... add it to my collection of CF books. ;-) Thank you! * JB *

> I installed and tried to run Railo 3 tonite. I ran the program using the > string "sh start.bat" ... it listed a few hundred lines in Terminal, > then seemed to get hung up. > > Err ... lost? I guess you're not used to running ColdFusion from the Terminal then? :) When it is "hung up" it has started and it's ready for you to hit the server with a browser. If you close the Terminal, you'll quit the Railo process and shut down the server. ColdFusion, Railo and OpenBD all behave the same in that respect. Running the servers from the console is good practice for development since you can see all messages logged there without having to root around in log files and you can also see any debugging output you have that uses console (such as <cfdump output="console"...> or <cflog log="console"...>). Hope that helps... -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood

This was my issue with resin, I just couldn't keep it running ----- Excess quoted text cut - see Original Post for more -----

Here is a tip if you are running any process from the terminal: Say you started Railo by doing: >sudo ./httpd.sh You will then get loads of output and the debugging, if you close that window it will stop the process, i.e. kill it. so you dont want that window hanging about do you? so hit Ctrl + z then type "bg" and it will background the process, which  means you can close the window. Maybe that was what was happening? Mark Drew - Adobe Community Expert - Reactor ORM Project Manager - CFEclipse Project Lead Developer Blog: http://www.markdrew.co.uk/blog/ LinkedIn: http://www.linkedin.com/in/mdrew ----- Excess quoted text cut - see Original Post for more -----

----- Excess quoted text cut - see Original Post for more ----- Or: sudo nohup ./httpd.sh & This will start the process in the background and capture all output to nohup.out - and when you close Terminal it will not kill the process. You can then watch the log by doing this: tail -f nohup.out As lines are written to the log, they will show up in your Terminal. You can stop tailing by ctrl+C and safely close Terminal. You can later navigate back to that directory and start tailing the log again any time you want. HTH, -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood