- This topic has 26 replies, 8 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
Henry… Tomcat 3 and Tomcat 5 are massively different from eachother and even Tomcat 4 and Tomcat 5 are different enough to be of a concern, are you sure that the version of Tomcat on the Solaris machine was also Tomcat 5? Do you load any native resources in your web app? Do you rely on any DLLs? (for database drivers). Do you rely on a JNDI context for setting up DB connections? Did you check the Tomcat log for exceptions when it was trying to deploy your app? Did it explode your WAR file correctly when you dropped it in the webapps dir? When you said it found “the HTML files” does that mean you could access it via a URL? If that is the case, then the webapp was started. Did you try clearing out the webapps and work directory on your Solaris server and then redeploying the WAR file?
These questions should help us get to the bottom of this.
I installed the Tomcat 5 to my virtual server. Here is the install set: Apache Tomcat/5.0.27, Java 1.3.1_04-b02, Sun Microsystems Inc. SunOS 5.8 sparc. I have no local resources.
The error message I get is:
HTTP Status 404 – /empress/servlet/Impart——————————————————————————–
type Status report
message /empress/servlet/Impart
description The requested resource (/empress/servlet/Impart) is not available.
I have looked at the logs and see no errors.
Henry.
What compatibility level do you have the Eclipse compiler set to for your project in Eclipse? I noticed that you are deploying using JDK 1.3, so make sure you are compiling with JDK 1.3 compatability.
It turned out to be a combination of several things. First, I tried to run both Tomcat 3 and 5 on my server because I didn’t want to port all my other apps at once. Turned out not to be a workable configuration based on assumptions my hosting company makes. So I uninstalled Tomcat 3. That still did not fix everything. Tomcat 5 was running under another port and I had to kill that process manually before it would relinquish control to the scripts. Then I upgraded to Java 1.4.1 on the server. That was part of the problem and I am grateful for the compatibility reminder. Finally, and I think this is a bug of some sort, the web.xml file was not present in the deployment on the server, even though it was present on the local machine when I did deployments. I manually copied the web.xml file over to complete the solution. Thanks again for your help. A bit cumbersome. I spent 10 hours just deploying this one small servlet. I have been working with them for some 3 years now.
Henry.
Henry… this does sound like situation that was complicated by so many factors. I’m glad you figured it out.
I have been using MyEclipse for updates of a year in a similar situation and before I deploy, I’ll change my lcoal deployment to packaged deployment, let ME create the WAR file, then upload the WAR file to the hosting provider and its always worked.
On of the big things I did to make sure it would work is to duplicate the production server on my local machine, app server, JDK version, etc. After I got everything set up ‘identically’ the deployment became a breeze. It sounds like you did that today by removing all possibly variables, I hope future deployments work smoother.
[btw: I’ve looked a little at java portal solutions, whilst solving step by step the problems with my HelloWorld deployment.]
–
You can savely ignore the complicated remarks about the problem with the Tomcat/Solaris deployment. Things are finally very easy!
–
(use _un_packaged deployment, thus a folder is generated)
– deploy to your local tomcat, test & debug the application
– copy (e.g. via ftp) the deployed folder (<local tomcat>/webapps/HelloWorld) to the folder <remote tomcat>/webapps/ HelloWorld directory.– for copying you can use e.g. ftp [should be possible within eclipse, if not, use your standard tools]
– Launch the demo with <remote tomcat>/HelloWorld/ (no restart needed)
– you can synchronize the remote folder whenever you have deployed a new stable version locally. [should be possible within eclipse, possibly one knows about the “synchronization view”.]
requirements:
– ideally, the remote tomcat / JVM installation should have the same version with your local one.–
Some details:
The main problem with HelloWorld deployment was: The Java-Hosting-Provider’s Tomcat.
– Take care that your java-hosting-service provides you with a unaltered tomcat (the out-of-the-box (or archive) behaviour), and that modifications to configuration files precisely described. This is a general requirement, for each remote software-package.
– You need to get somehow contact to the default tomcat page, like the one in an local installation “http://localhost:8080”. Don’t assume that you got your private instance on “http://yourDomain.com:8080” [i did not, i got the shared tomcat there, but how should i know this…].
– After getting contact at e.g. “http://yourDomain.com”, you can use the /manager application to upload your *.war file via your webbrowser. but!
– The tomcat’s “manager” and “admin” applications need passwords. If your hosting-provider did not setup your basic hosting-account (user/pwd) as default, ask him to do so. Alternatively you can modify the file /conf/server.xml manually (e.g. via ftp), but then you have to restart your tomcat.
– Starting and stopping Tomcat depends onf Hosting-Providers functionality (e.g. webinterface). You have to use e.g. an SSH shell to launch the /bin/startup.sh and /bin/shutdown.sh.
–
Essentially, deployment of an webapplication to a tomcat is done by simply copying the webapplication folder to the /webapps directory. This should run fine, even without a restart, if the tomcat installation is a default one (as unpackaged from the installation archive).
comments are of course welcome.
thanks.
–
somer errors:
You can savely ignore the complicated remarks about the problem with the Tomcat/Solaris deployment.
=> Tomcat/SunOS 5.8 sparc deployment
–
Alternatively you can modify the file /conf/server.xml manually
=> /conf/tomcat-users.xml
–
It would be horriby handy if MyEclipse had a plug in to generate a default Maven script (http://maven.apache.org) . At the moment I am copying some of the files back and forth between directory structures which works well enough but having it in there would be VERY slick.
Deployments are a lot easier using Maven than Ant IMHO; written by the same crew Maven is sort of an Ant+
Wow this thread is turning into a catch-all 😉
Maven support is getting increasing more attention on our radar and will be addressed in a future release, no ETA though.
Indeed Maven is increasingly of interest. In the meantime, checkout:
This is a full-fledged maven IDE support software, with flavors supporting Eclipse as well as NetBeans and JBuilder. Yours truly has contributed to the Eclipse plugins.
You can try Prokmu jsp hosting!
