Hello again,
I encountered problems trying to implement email service in my webapp. I'd prototyped
in a standalone Java program and things ran ok. When I implemented the email service
in my servlet, I got many errors, mostly of the noclassdeffound variety.
The folks on this list indicated the
List,
I thought I'd try a few things, to try and get my application to make use of
javax.mail.*
I'm running IBM java131 and Tomcat 3.3.1
I've got a fairly extensive webapp written and running. Moved it to a RedHat 9 Linux
server without any changes (cool!).
I'm now trying to add some new fu
OK, I'm going a little (more) crazy here.
I *think* that the problem might be that the mail stuff is the very first use I've
made of a J2EE component. The code is compiled with a CLASSPATH which includes
x:\usr\local\j2ee\j2ee.jar. The standalone code runs fine, and presumably at runtime
it f
Well, I'm back again for some help. I'm running Java 1.3.1, Tomcat 3.3.1
I have a small proof of concept java program which uses javax.mail and which
successfully sends off a note.
When I incorporate the proof of concept code into a servlet, I get:
java.lang.NoClassDefFoundError: javax/activat
Thanks! You were right. I had two CLASSPATH statements, and one was pointing at only
the jre. I can't really understand how that happened, I really have been running very
well for the past six months, compiling JSPs, running servlets, and generally very
happy. Why this should have happened ri
Everything was working fine this afternoon. This evening nothing works. I'm now
getting the dreaded java.lang.NoClassDefFoundError: sun/tools/javac/Main.
Just before this, I was getting an abstract error method, failing to find TLD
information. There weren't any library tags in the page bei
Ok, thanks. Changing TOMCAT_USER in tomcat3.conf to 'root' did the trick, eventually.
I had errors in several chown commands during the setup for start. I just commented
them out, since there shouldn't be any need for a root user to access files, right?
Anyway, it's running now, on port 80 an
Ok, thanks. I'm starting Tomcat with a script (now I know that, didn't before). It
has a configuration file which defines the startup user as 'tomcat3' (I'm still using
Tomcat 3.3.1). Should I change the TOMCAT_USER config variable to root?
Or is there a Better Way? P'haps some permission I c
I don't think that Apache is running, status of httpd is stopped. Is there another
way to ensure this?
The tomcat failure message is quite specific about permission:
Exception: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: org.apache.tomcat.core.Tomcat
Actually, I'm such a newbie that I'm perfectly willing to give Tomcat exclusive access
to port 80 -- at the moment, I rather not incur the additional learning curve required
to get Apache running, still less getting Apache to frontend for Tomcat.
I grant you that I'll probably want to use Apache
What do I have to do to get Tomcat 3.3.1 to run with port 80? I modified server.xml
to alter the port number, and it now fails with lack of permission on port 80. The
Redhad doc for Apache says it must be started by root for this to work, but I start it
as root and it still fails.
A command l
Hello,
I'm new to both Tomcat and Linux. I installed 3.3.1 via RPM on my Redhat 9 system.
The file structure doesn't seem to be what is documented in the Tomcat docs. Is there
a list of where all the Tomcat bits go when installed via RPM?
Thanks in advance!
Regards,
Terry Fuller
[EMAIL PRO
12 matches
Mail list logo
