----------------------------------------------------------------
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:
>
> on 11/19/99 3:28 PM, Kevin L McWhirter <[EMAIL PROTECTED]> wrote:
>
> >
> > I would agree with you except that servletrunner runs the servlet just fine!
> > Loads
> > the library and links the JNI calls. As a sidebar, I was REALLY surprised
> > how
> > fast this stuff is!
>
> Excuse me, but servletrunner is not JServ.
>
> > But I cannot believe it is the JVM. An application I wrote that does exactly
> > what
> > the servlet does also runs fine. I'm afraid that I have to conclude that
> > LD_LIBRARY_PATH is NOT the issue! Like I said, I can see the LD_LIBRARY_PATH
> > setting in /proc/<JVM proc id>/environ.
> >
> > Hmmm. What a puzzle.
> > Kevin
>
> It isn't a puzzle. You simply don't have the shared library in the
> java.library.path. I can repeat this until I'm blue in the face, I wish you
> would please wake up and listen to me.
>
> -jon
You really aren't having much fun -- are you jon? Sheesh!
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!
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 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.
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.
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
(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.
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.
Thanks again for your response, but relax. We are all family here.
Kevin
--
--------------------------------------------------------------
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]
