----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
jon * wrote:
>
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> on 11/19/99 4:16 PM, Kevin L McWhirter <[EMAIL PROTECTED]> wrote:
>
> > You really aren't having much fun -- are you jon? Sheesh!
>
> I would be having more fun if you would listen to me.
>
> > My point about servletrunner (albeit was not clear) is that it is using the
> > identical JVM and identical LD_LIBRARY_PATH settings. In my mind that
> > eliminates
> > the JVM and LD_LIBRARY_PATH as variables in this problem -- they simply are
> > NOT the
> > problem!
>
> I repeat, you are wrong.
>
> > You mention that the java.library.path property is possibly the issue. If
> > that
> > were true then servletrunner would fail to load the library also -- would it
> > not?
> > If I am wrong here please correct me!
>
> I repeat, you are wrong.
>
> > I have been using Linux since the 0.91 kernel. My first distribution was from
> > SLS
> > (Soft Landing Software) out of Canada. It came on 30 5-1/4" diskettes. I am
> > VERY
> > familiar with LD_LIBRARY_PATH issues! I also have fairly extensive experience
> > with
> > HP/UX, SCO UNIX, AIX and Solaris.
>
> I watched my mom use punch cards. Big deal.
>
> > In my mind the issue is somewhere inside Apache-Jserv. Probably my
> > misunderstanding of how it works and how it should be properly configured to
> > run
> > JNI code. I think that is probably the case since I was able to get it
> > working
> > (with brute force) by setting up 2 jar files instead of just one and putting
> > them
> > both in the wrapper.classpath statements in the jserv.properties files.
>
> It is a difference between the way that Apache JServ is running in the JVM
> vs. the way that servletrunner is running in the JVM. That is why it isn't
> working.
>
> > Now you seem to be suggesting that I should put the library in the directory
> > (one
> > of the directories?) pointed to by the java.library.path property. However,
> > I
> > have some problems with this:
> > (1) the property is null in my system -- and yet servletrunner runs the
> > servlet
> > just fine with it set to null
>
> Are you 100% sure that java.library.path is actually set to null in
> servletrunner?
>
> Here is a servlet for you to test with:
>
> doGet(HttpServletRequest req, HttpServletResponse res )
> {
> getoutputstream
> out.println ( System.getProperties() );
> }
>
> What is java.library.path set as? Run that in both Apache JServ as well as
> servlet running. I BET you get a different response for each.
>
> > (2) I have read nothing in the documentation that suggests that there be one
> > single
> > repository for shared libraries.
> > (3) I see nothing in the configuration files (aside from wrapper.env=) to
> > setup
> > such a repository.
> > (4) I want to group all the code for a single zone in one place -- all
> > together.
> > Otherwise, installation is less straight forward.
>
> The repo is the setting for java.library.path. There can be multiple paths
> here. You need to put your shared library code in one of those paths.
>
> > So I hope I have dispelled any notion in your mind that I am ignoring what you
> > have
> > said. I have taken it to heart! I do not understand how it makes a
> > difference.
> > And this was the nature of my previous question. Why do you believe that the
> > java.library.path property setting is the answer? As confident as you are
> > of
> > your answer, you must possess some knowledge about Apache-Jserv internals
> > that I
> > do not. Consider me your student -- teach me.
>
> Read my previous postings. I already explained to you that your shared
> library code MUST be in this path. You would not get the exception that you
> are getting unless you didn't have the shared library in that path. Period.
> End of story.
>
> For some reason, your java.library.path is getting screwed up for Apache
> JServ via your configuration.
>
> > Thanks again for your response, but relax. We are all family here.
> > Kevin
>
> I'm frustrated because you are not listening to me. I will relax when you
> decide to listen. At that point, your problem will be solved.
>
> Here is another way to look at it. People use Native JDBC drivers with
> Apache JServ all the time. It works fine. Your drivers should work as well.
> You just need to properly define your java.library.path. Period.
>
> -jon
>
Dear Jon, dear Kevin
Your discussions are very interesting but i didn't find a solution to my
problem :
I've tried all the solutions given by Kevin in the previous posts (a
single JNI.jar in the wrapper.classpath, autoreload.class=false,
autoreload.files=false). Thanks Kevin, if it works for you, please
email me your .properties or explain me how I must do because it doesn't
work for me.
I also try to use Jon's servlet. On my first try, java.library.path
didn't exist in the default properties. So, I tried this :
Properties prop=new Properties();
prop=System.getProperties();
prop.put("java.library.path","/usr/lib/");
System.setProperties(prop);
in my servlet. My dynamic library is in /usr/lib.
In fact, on my second try of Jon's servlet, I saw
"java.library.path=/usr/lib/" but I still have an UnsatisfiedLinkError
when I call my native method.
I don't understand anything...
Thanks for your response
Jerome
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
