Tomcat installation help please!!!!!

[kriti sharma]

I have my jdk at c:\jdk1.3 and tomcat at c:\jakarta-tomcat-5.0.19.i have set Java_HOME=c:\jdk1.3 in the autoexec.bat.When I run startup in c:\jakarta-tomcat-5.0.19\bin the dos prompt appears hanged up.nothing happens.when i open http://localhost:8080 it shows "cannot find server". how do i run tomcat. Please help urgently..

[nash avin]

Hi,
If the startup console hangs then you havent set up the tomcat correctly,there is no point in using the http://localhost:8080 url.Whats the operating system you are using.
let me know
nash

[William Brogden]

This kind of question comes up all the time - browse in the last 2 weeks of posts, you may find the answer. If not, be sure to include your operating system in your next post.
Bill

[kriti sharma]

windows 98

[kriti sharma]

I changed call "%EXECUTABLE%" start %CMD_LINE_ARGS% to call "%EXECUTABLE%" run %CMD_LINE_ARGS% and started getting the output on the same DOS screen. I am getting a big bunch of errors.i do not know how to copy the complete trace from MS DOS screen,so that i can post it here,can someone tell me?
Also , I did change the port in server.xml from 8080 to others but nothing works.

[William Brogden]

Windows 98 does not provide enough "environment" memory space in a DOS console window by default. You have to modify the setting. This post discusses the problem.
Bill

[Anjanesh Lekshminarayanan]

Similar problem.
I have WinMe. I recently downloaded Tomcat 5. It was written that it would run as a WinNT/Win2K/WinXP service whatever may be the installation.
I ran tomcat.exe but nothing happened. The DOS window just opened & closed. I ran in DOS mode it gave no error. It wasn't running in the background(I checked ctrl+alt+del).
Anyone know how to get jsp scripts to work on Me ?
Thanks

[William Brogden]

Before trying to get Tomcat to run as a service, you should get it running as an application. What happens if you open a DOS command prompt window, change to the TOMCAT_HOME\bin directory and execute startup.bat?
Bill

[kriti sharma]

i do not have the environment space problem, i did set it to 4096. when i run startup.bat a long list of errors appear.i cannot scroll down the dos window. can you tell me how to capture the entire trace and copy it so that i can post it here.sorry but i am not very well-versed with DOS commands as well.

[N Nanda]

Hi kriti,
you have not mentioned how did you install Tomcat. For windows there are 2 ways to work with Tomcat.
1. Download the

.exe

file and install it. :: For this I don't think you need to set the environment virables (like java_home etc.).
2. Download the

.zip

file. :: For this kind of download, unzip it in a location like C:\Apache\Tomcat5 ( No need to name it like jakarta-tomcat-5.0.19 ). Now open autoexec.bat in a text editor and add followings lines...

JAVA_HOME=C:\jdk1.3
CATALINA_HOME=C:\Apache\Tomcat5

Note :: All should be in capitals.
I assume you have configured your Java environment. If not go through following lines.
Now go to the line containing the line PATH. Add the following...
;C:\jdk1.3\bin
Thats all. Save the file autoexec.bat and restart your machine. Open the folder where you have unzipped the tomcat (here C:\Apache\TOmcat5) and browse bin folder. Double click on startup.bat. After successful startup, open a browser and give http://localhost:8080
Hopefuuly it'll work. For more tomcat configurations, you can visit my site
http://sit.iitkgp.ernet.in/~nnanda/config.html

[kriti sharma]

i cannot get the complete trace of errors as the dos window does not allow scrolling,the initial errors are lost,only last screen is available.
when i run startup.bat,this is what i get.....
--------------------

at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at org.apache.catalina.util.CatalinaDigester.startElement(CatalinaDigest
er.java:112)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
ce)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unkn
own Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElemen
t(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at org.apache.catalina.startup.Catalina.load(Catalina.java:566)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap

---------------------
please help!!!

[William Brogden]

See my other post about configuring the DOS window to hold more lines.
That error may indicate a problem with one of the xml configuration files, because Digester is what Tomcat uses to read them - but you should capture more of the error messages.
Bill

[Kaustubh Patil]

Kirti,
You might get all the stack trace in the logs of the tomcat. See the log files. You might paste the relevent part in the post.
-Kaustubh.

[Kaustubh Patil]

Kriti,
If you haven't yet resolved the problem. Do this. Modify the startup.bat in the \bin directory. To make the catalina start in the same window modify the line

call "%EXECUTABLE%" start %CMD_LINE_ARGS%

to

call "%EXECUTABLE%" run %CMD_LINE_ARGS%"

The "run" makes it start it in the same window. This will give you the full stack trace of the exception. Have a look at that.
Usually the problem is conflict in the port. If its the same in your case modify the xml file \conf\server.xml. Modify the catalina service entry. The catalina service entry has an entry <connector> set the port of the first connector entry to some unused port. To make it easy search on the "8080" number, which is the default port entry. Change it to some other number , say 9000.
Save the xml and run the startup again..
See what happens. Hope this helps.
[ April 15, 2004: Message edited by: Kaustubh Patil ]

[kriti sharma]

to Kaustubh :i did as you said and got the following errors.cant even give the full trace of erros as i can copy only the last screen of errors on DOS.
--------
or: sun.misc.InvalidJarIndexException: Invalid index!
at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:594)
at sun.misc.URLClassPath.getResource(URLClassPath.java:134)
at java.net.URLClassLoader$2.run(URLClassLoader.java:349)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:346)
at org.apache.catalina.loader.StandardClassLoader.findResource(StandardC
lassLoader.java:562)
at org.apache.catalina.loader.StandardClassLoader.getResource(StandardCl
assLoader.java:638)
at org.apache.commons.modeler.Registry.loadDescriptors(Registry.java:895
)
at org.apache.catalina.mbeans.MBeanUtils.createRegistry(MBeanUtils.java:
1649)
at org.apache.catalina.mbeans.MBeanUtils.<clinit>(MBeanUtils.java:154)
at org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.<clinit>(
GlobalResourcesLifecycleListener.java:112)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.j
ava:253)
at org.apache.commons.digester.Rule.begin(Rule.java:200)
at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at org.apache.catalina.util.CatalinaDigester.startElement(CatalinaDigest
er.java:112)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
ce)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unkn
own Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElemen
t(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at org.apache.catalina.startup.Catalina.load(Catalina.java:566)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:397)

[Kaustubh Patil]

Ohhh..seems that your logs are really big..
do one thing.. a simple one.. redirect the output to some other file , log file.
run the commad as "startup > tom.log"
you will get all the log in the tom.log file.. it will be easier to solve the problem once you get the whole log..i hv tried this. This does create a log. But remember to start the catalina in the same window as mentioned earlier.
I m getting too much intrested this problem now.. lets solve this..once and for all...
[ April 16, 2004: Message edited by: Kaustubh Patil ]

[William Brogden]

It is not clear from the Tomcat site whether or not version 5 requires SDK 1.4 - I know that some versions of Tomcat 4 required SDK 1.4.
I have only run Tomcat 5 under sdk 1.4
Bill

[Kaustubh Patil]

Actually.. i did install Tomacat 5 yesterday. I hv JDK 1.3 on my machine..and my JAVA_HOME is set to "C:\jdk1.3.1_03"

[kriti sharma]

my startup has
call "%EXECUTABLE%" run %CMD_LINE_ARGS%
that means catalina runs in the same window as startup.
i did type startup > error.log
no content found in the error.log file.
the bin folder has a logs folder which is empty.

[Kaustubh Patil]

"that means catalina runs in the same window as startup."
- Did it start in the same window or r u still getting the pop up ?
"no content found in the error.log file."
-This cannot happen.. if u say there was some o/p on the screen and still the error.log is empty .cannot happen.. error.log will be in the same folder from where u ren the startup.
"the bin folder has a logs folder which is empty."
-forget these logs..

[kriti sharma]

when i run startup only a single window runs.
how to convince you that the error.log file is EMPTY!!!
bad luck running strong on my side!

[Kaustubh Patil]

Well !! Its strange..U say that some error stack does come on your o/p. But when u redirect the o/p to a file , the file is empty... !!! really strange.. never seen this before..
This thing probably has nothing to do with tomcat then..

[Kaustubh Patil]

I googled the exception that u put in the post. Seems that some times JDK 1.3 does not have the jar that tomcat needs.. say some of the posts on the web...
strange !! strange !! as I am myself using JDK 1.3.1..
WHATEVER ...!! Its driving me nuts..
Do one thing, try using JDK 1.4. If it works.. or the problem is because of something else..then I can see what exactly jar it misses..and how it works on my machine..

[kriti sharma]

kaustubh,u wont believe it, my life is such that,i very frequently hear people say to me "really strange.. never seen this before.."
am born on a 3rd and am born unlucky....
will try to get hold of jdk1.4 and then tell you.
thanks a lot for your time.

[Kaustubh Patil]

I think I found the answer. This is the bug listed on Java site. In JRE1.3 this exception is thrown when an attempt is made to create a jar index file for the classes loaded through reflection. This happens only with JDK 1.3 Not even with JDK 1.2 It was fixed in 1.3.0_03. For more details.. see
Java Bug list . Bug # 4358512
So dont worry its not your fault. And nither its ur b'date .
And speaking abt b'date I should be thrice as unlucky as you are 'cause mine is 9th.
But instead I was fortunately running JVM 1.4.1 though my JAVA_HOME was pointing to JDK 1.3.1_03. Now this is something I need to figure out.
Prob. this was because the JRE 1.4 automatically starts on startup of OS.
huh!! :roll: Now I am the one who needs an answer. :roll:
[ April 20, 2004: Message edited by: Kaustubh Patil ]

[Kaustubh Patil]

Did this problem got solved ? or was it something else ?