Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

UnsatisfiedLinkError after Tomcat restart

 
Jay Grant
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Receiving java.lang.UnsatisfiedLinkError: ICEJ1 (Library is already loaded in another ClassLoader) on my ICEJ1 DLL. This occurs after a Tomcat restart on the first invocation of a servlet which loads the DLL, so it's not a case of having updated the servlet while Tomcat is running and attempting to reinvoke it (which as I and innumerable other victims have discovered, itself necessitates a Tomcat restart). libICEJ1.x and libICEJ1.so exist only in .../lib, there are no other copies. Could Tomcat have squirreled something somewhere else that precipitates this condition?
 
Sachin Pachari
Ranch Hand
Posts: 56
Eclipse IDE Netbeans IDE Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Could you post some more detailed information in the matter, its very hard to tell where its going wrong.
 
Jay Grant
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not really much I can add. If the DLL-related "lib..." files exist only in the .../lib directory as far as I can tell (where they should exist), then how can they be already loaded elsewhere in a different ClassLoader? A recursive search of the directory hierarchy only shows them in /lib.
 
Sachin Pachari
Ranch Hand
Posts: 56
Eclipse IDE Netbeans IDE Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Try Posting the Error Stack Trace, it might give more clarity, just the type of error cant help in any possible way, so could you give more information on this matter ?
 
Jay Grant
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually think I found it...there was an overlooked class file of the same name in the ROOT structure which referenced the mystery DLL...deleted it and the message disappeared.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic