1 of 1 people found this helpful
You have to use gatein.bat.
Can you please point me on where it says to use startup.bat as we need to fix this documentation. Using startup.bat will not work.
Try deleting gatein/data and start again with gatein.bat
I unzipped the file and looked in the root of the resulting directory GateIn-3.0.0-GA. In there is a file called "RUNNING.txt" I think I may be forgiven for opening that. It talked about running GateIn on TomCat and said to start tomcat using startup.bat. I know the TomCat instance was provided with GateIn, but seeing the startup.bat I tried that first.
There was no gatein\data directory (there were a conf and logs subdir).
I Removed the entire distribution and re-unzipped it, now carefully starting it through gatein.bat.
The startup logs were considerably different and it now works as advertised. I would suggest to add a RUNNING-GATEIN.txt to draw away the attention from the other one or rename the text files to correctly reflect their intent/traget audience.
Ok, RUNNING.txt comes from plain Tomcat, we should remove that file, I also wanted to remove startup.* all along.
There should be a GATEIN-README.txt file in your distribution though. (noticed that command for production and development is stated as the same it should be gatein-dev.sh for dev)
Created a JIRA: https://jira.jboss.org/jira/browse/GTNPORTAL-1181
Thanks for the feedback
Do we still need the startup.bat to be included? Or can it be merged into gatein.bat or renamed to something else.
Its confusing having multiple start scripts, especially since people used to Tomcat will instinctively try and run the server with the wrong one.
Nope we can remove the startup.* files from my POV.