aspose file tools*
The moose likes Tomcat and the fly likes JNI + Tomcat? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "JNI + Tomcat?" Watch "JNI + Tomcat?" New topic
Author

JNI + Tomcat?

Scott Lynch
Greenhorn

Joined: Dec 12, 2001
Posts: 19
I'm currently running Tomcat 4.0 and have a servlet that uses JNI that's giving me some issues. If I use the /manager/reload command on my application, this particular servlet doesn't come up because it's unable to link to the JNI library that I have compiled. Is there something I need to tell Tomcat in order for it to find the library? I'm able to restart the server from the command line and it will pick up the library from my LD_LIBRARY_PATH. I've got a feeling that Tomcat is using the default library path when a reload is issued.


"It is not a good idea generally to annoy a computer cracker, but it is a very bad idea to annoy a group of computer crackers bent on impressing each other."<br />- Robert X. Cringely
Mike Curwen
Ranch Hand

Joined: Feb 20, 2001
Posts: 3695

the manager app (in my limited experience with it) was a bit hinky.

I eventually stopped using it, as it didn't always seem to work as advertised. This was on a Solaris staging box at work, I haven't tried it too much with Win2000.
Scott Lynch
Greenhorn

Joined: Dec 12, 2001
Posts: 19
Originally posted by Mike Curwen:
the manager app (in my limited experience with it) was a bit hinky.

I eventually stopped using it, as it didn't always seem to work as advertised. This was on a Solaris staging box at work, I haven't tried it too much with Win2000.

I knew there was something I forgot to mention.. but yeah, this is on Solaris as well. It's not really such a big deal since any time I have to add a new servlet I have to bring it down and back up again (web.xml is not parsed when manager/reload is called), but it would be nice if there were a way to bring down a single application without taking down Tomcat.
Mike Curwen
Ranch Hand

Joined: Feb 20, 2001
Posts: 3695

that is what /manager is *supposed* to do, and in fact, it brought things down for me alright. It was getting back up that was a problem.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JNI + Tomcat?
 
Similar Threads
Neat trick for Unix shell users..
JNI UnsatisfiedLinkError
Having Classpath trouble on my new iMac
Infinite Loop of action processing
Servlet reload