• 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

why eclipse is still running older tomcat version

 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Today I have downloaded Eclipse kepler release and added tomcat 7.0.42 to it. My older Eclipse IDE had tomcat 6.0.37.

Now I have imported my same old WORKSPACE to Eclipse kepler. But when I am starting my tomcat 7
it getting started correctly but with the following error



Its true that my older tomcat 6 version was for 64-bit system type but somehow it worked with my eclipse IDE. All my projects are working fine.
But as can be seen in console why both tomcat 6 and tomcat 7 servers are getting started even when my 'server perspective'
showing only tomcat 7 as added. I know its something because of same workspace I am using or may be both the tomcat versions
are added with same port number 8080. I tried everything from my side but couldnt able to stop tomcat 6 from getting started or to
remove java.lang.UnsatisfiedLinkError. Please advice me on that.
Thanks in advance.

-Jayant
 
Jayant Joshi
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The full console content is here after server gets started

 
Jayant Joshi
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Okay when I remove tomcat 6 from D:\Software\Apache software\apache-tomcat-6.0.37-windows-x64 then this error is not coming. Still don't know how it generated.
 
Jayant Joshi
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I removed the classpath too for tomcat 6 and replaced it with tomcat 7. This could be the reason why I am not getting that error any more. But I am not sure. No one here to reply to this thread ?
 
author
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you loaded the old workspace, it still has Tomcat 6 registered. And all of the projects you had earlier deployed to Tomcat 6 will still use 6. To use Tomcat 7, you'll have to first configure it and then switch all of your projects to use 7.
 
Jayant Joshi
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Currently I am not getting any error but I undo everything to regenerate it. Like changing classpath, copied tomcat 6 where it was before etc but still couldn't regenerate the error. Anyways thanks for your reply Peter. I will keep it in mind.

-Jayant
 
Jayant Joshi
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Finally I could able to regenerate the same error again. But deploying my project with tomcat 7 doesnt help. What I did was, I opened my old eclipse IDE and removed tomcat 6 as a server which was added previously. This removed all configurations of tomcat 6 from my workspace. When I opened it again with new eclipse kepler IDE with tomcat 7 added, this error was gone. For me this thread is resolved.

-Jayant
 
You have to be odd to be #1 - Seuss. An odd little ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic