• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Copied Tomcat 6 webapp working fine on one server but not another

 
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am running tomcat 6, 64 bit on a Windows 7 64 bit platform. I copied my web application (entire folder - it is called cuba4remedy) to a tomcat 6 64 bit installation on a different machine. this one running Windows 2008 standard 64 bit.

The servlet was working fine on my Windows 7 development machine but when I run on the new machine I see this error in the Catalinaxxx.log :-

SEVERE: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/cuba4remedy,J2EEApplication=none,J2EEServer=none

I don't really understand why I am getting this error. Any ideas anyone?

One more point might be relevant. I compiled on my dev machine using Javac version 1.7. On the machine I copied to only the Java runtime is installed - that is Java version 1.6.
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would certainly try recompiling with the command line option -target 6

See the javac options.

Bill
 
Angus Comber
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

William Brogden wrote:I would certainly try recompiling with the command line option -target 6

See the javac options.

Bill



I did try -target 1.6 but it errored. It was quite simple for me to download the v1.6 sdk so I did that and recompiled and it fixed the problem. I was a bit surprised though because I was not using any v1.7 features as far as I was aware.
 
William Brogden
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Compiled classes get labeled with the Java version they are compiled for. Java 6 won't run a class compiled for 7 due to this label, not the features.

Bill
 
Angus Comber
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

William Brogden wrote:Compiled classes get labeled with the Java version they are compiled for. Java 6 won't run a class compiled for 7 due to this label, not the features.

Bill



The trouble is customers are likely to have java jvm 1.4, 1.5, 1.6 and possibly 1.7. So for maximum compatibility and least deployment headaches I guess best to restrict yourself to only say 1.4 or 1.5 features?
 
William Brogden
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
See the Java version history at Wikipedia.

Versions 1.4 and 1.5 are no longer supported and 1.6 reaches end of life soon. As a consultant you should be letting customers know the dangers of out of date java and helping them update.

Bill
reply
    Bookmark Topic Watch Topic
  • New Topic